@ELT,IQD UUSIG*1091-001-001.INSTALL/DOC,,SENT,,DOC LOOKPRINT$ Installation and Maintenance Manual Peter G. Madsen MAPPER Coordinator FREDERICK and NELSON (206) 235-8844 10/18/91 10/18/91 Page 2 Rev. 16 LOOKPRINT$ Installation and Maintenance ______________________________________________________________________________ TABLE OF CONTENTS 1. SYSTEM SUMMARY..................................................... 3 1.1. PURPOSE........................................................ 3 1.2. NOMENCLATURE................................................... 3 1.3. TASKS AND PROCEDURES........................................... 3 1.4. DATA BASE DESCRIPTION.......................................... 3 1.5. SYSTEM ACCESS.................................................. 4 1.5.1. WHO USES THE SYSTEM........................................ 4 1.5.2. SECURITY RESTRICTIONS...................................... 4 2. INSTALLATION OF THE SYSTEM......................................... 5 2.1. GENERATION OF A DRAWER......................................... 5 2.2. COPY THE DISKETTE FILES........................................ 5 2.2.1. DISKETTE CONTENTS.............................................. 6 2.3. TRANSLATING THE RUNS AND TABLES................................ 6 2.4. RUN REGISTRATION............................................... 7 2.4.1. SENDPRINT$ REGISTRATION........................................ 7 2.4.2. LOOKPRINT$ REGISTRATION........................................ 7 2.4.3. FORMPRINT$..................................................... 8 2.4.4. MREGPRINT$ REGISTRATION........................................ 8 2.4.5. REGPRINT$ REGISTRATION......................................... 8 2.4.6. CALLED SUBROUTINE 7B........................................... 8 2.4.7. CALLED SUBROUTINE 10B.......................................... 9 2.4.8. CALLED SUBROUTINE 13B.......................................... 9 2.4.9. SCREEN 5B...................................................... 9 2.4.10. SCREEN 11B..................................................... 9 2.4.11. SCREEN 14B..................................................... 9 2.5. TABLES......................................................... 9 2.5.1. INDEX REPORT................................................... 9 3. OPERATION OF THE SYSTEM............................................ 10 3.1. EXECUTING REGPRINT$............................................ 10 3.2. EXECUTING MREGPRINT$........................................... 10 3.3. MISCELLANEOUS NOTE............................................. 10 10/18/91 Page 3 Rev. 16 LOOKPRINT$ Installation and Maintenance ______________________________________________________________________________ 1. SYSTEM SUMMARY 1.1. PURPOSE This document provides the some of the knowledge required to install, register, and maintain the LOOKPRINT$ system. The target audience is MAPPER Coordinators. A separate document, called LOOKPRINT$ User Manual, describes the operation of the LOOKPRINT$ system. The LOOKPRINT$ system is named after the principal run used to access the PRINT$ listings. 1.2. NOMENCLATURE First we should make note of the terms used in this document. All OS-1100 runs are called "jobs" to distinguish them from MAPPER runs. In practice, we also use the term "job" to refer to the name given to a PRINT$ when it is registered. We use the term "register a job" to describe the process by which we identify a job and the parameters for its storage. Jobs are registered. 1.3. TASKS AND PROCEDURES Two categories of tasks are described below - 1) the installation and 2) the registration of jobs once the system is in place. Several steps are involved in the installation of this system. The process is not automated but neither is it complicated. First a cabinet must be assigned and a drawer generated for the runs. Next, the runs must be loaded and registered. Last, some sample PRINT$s must be registered and tested. The "daily maintenance" procedures consists of registering new PRINT$s. The registration process may include selection of a drawer for storage. The registration request procedure performed by the end user (programmer or analyst) is described in the user manual. 1.4. DATA BASE DESCRIPTION The data base requirements are extremely simple. The system requires a minimum of one 132 character wide FCS drawer. Additional drawers (also 132 chars, FCS) will be required when the system is accepted by your users; plan ahead. We suggest you assign a full cabinet (or set of cabinets) and reserve a few files. Factors that will determine the number of drawers required at your site are: the number of batch jobs, their execution frequency, and how many copies are retained. Initial response at Frederick and Nelson was low key, followed by exponential growth as the concept was accepted. We are now back to modest linear growth. 10/18/91 Page 4 Rev. 16 LOOKPRINT$ Installation and Maintenance ______________________________________________________________________________ 1.5. SYSTEM ACCESS 1.5.1. WHO USES THE SYSTEM The principal users of the LOOKPRINT$ system at Frederick and Nelson are data center personnel. The heavy users are our programming staff and those responsible for monitoring production jobs. 1.5.2. SECURITY RESTRICTIONS The MAPPER coordination staff controls the LOOKPRINT$ system at our site. We do not anticipate that this will change since the the system can have a large impact on disk use. You may consider assigning the job registration function to another DP organization such as Production Control or Data Control. The Operations staff and the Production Control staff have access to all PRINT$s. All other users are restricted to jobs registered under their MAPPER department number. The end user is never allowed update access to the PRINT$s. 10/18/91 Page 5 Rev. 16 LOOKPRINT$ Installation and Maintenance ______________________________________________________________________________ 2. INSTALLATION OF THE SYSTEM Installation of the system can be separated into four steps. You will first create a drawer for the runs and the initial data. Next you will copy the diskette files to your MAPPER system. Third, you store and register the runs. Fourth, you store the tables. You will also be required to provide a name for your system. At Frederick and Nelson, we have two copies installed. The first is called the LOOKPRINT$ system and is primarily for PRINT$ listings. The second copy is called the LOOKREPORT system and is used for storing user reports. After installation you will create some test jobs and register them. Last, you declare victory and let a couple of your best users pilot the new system. 2.1. GENERATION OF A DRAWER The runs will execute, without modification, anywhere in the system. Choose a cabinet and generate a drawer for the runs. Generate it 132 characters wide, with a an FCS character set, and no edits (line 32 of RID 0 must be blank). If you limit the drawer to less than 2000 RIDs, then you must revise the called routine 7B. Data storage drawers can also be generated to these specifications. The first drawer may serve as your first PRINT$ storage drawer. Be careful to generate the drawer in a file that can accept a lot of RIDs - a new file should be considered. Note: If you choose to use the run drawer for data storage also, you must change the value of the variable in the called routine (7B). See the run description section for 7B for further details. 2.2. COPY THE DISKETTE FILES This you must do with the tools available at your site and your own wits. The software resides in MS-DOS diskette ASCII files. Copy the files into your MAPPER system by any means available to you. The names of the file indicate the original RID. Place them into the equivalent RID in the drawer you created above. You can change the drawer without modifying the runs. If you change the RID NUMBER, then you will need to make changes to variables (these required changes are noted in the runs). The TXT files are manuals. Copy them into a word processor file for revision and publication. 10/18/91 Page 6 Rev. 16 LOOKPRINT$ Installation and Maintenance ______________________________________________________________________________ 2.2.1. DISKETTE CONTENTS The files which reside on the diskette are: FILE TYPE FUNCTION ------ ------ ------------------------------- 1B Run SENDPRINT$ 2B Table Index of PRINT$ locations 3B Run LOOKPRINT$ 4B Table Description of fields in 2B. 5B Screen Help for FORMPRINT$. 6B Run FORMPRINT$. 7B Run called subroutine. 8B Run MREGPRINT$. 9B Run REGPRINT$. 10B Run called subroutine. 11B Screen for called subroutine in 10B. 13B Run called subroutine. 14B Screen for called subroutine in 13B. INSTALL.TXT is the file that contains this document. It describes installation and maintenance of the system. USERMAN.TXT is a text file that contains the User Manual for SENDPRINT$ and LOOKPRINT$ runs. To assist in diagnosing possible data transfer problems, here is how the files were created. First each report was processed by a run that performed the @LCH command to change tabs to a right brace (}) character. The result was printed with an AUX command on an OFIS Link PC which captured all the reports in a text file. The text file was split into separate files (and page eject characters removed) with a word processor called PC Write. The manuals where written in OFIS Link and printed to an ASCII file. The output was cleaned up with PC Write to eliminate printer specific control characters. 2.3. TRANSLATING THE RUNS AND TABLES When you retrieve each file into MAPPER, you must process it with two CHG commands. Change all right braces (}) to tab characters. Remember that the CHG command does not change characters in the headers. Before replacing the RID, remove the ".DATE" and "..... END REPORT ....." lines. These lines were left in the the ASCII files for identification. A wise person would perform a BLT function before storing the RID. When you copy the files to the your run drawer, each file should be placed in the RID corresponding to the number in the file name. 10/18/91 Page 7 Rev. 16 LOOKPRINT$ Installation and Maintenance ______________________________________________________________________________ 2.4. RUN REGISTRATION 2.4.1. SENDPRINT$ REGISTRATION This is the batch port run that processes the PRINT$ as it comes into MAPPER. Register the SENDPRINT$ run (1B) in department 104, executable by a user called BPORT-104. Provide access to all cabinets that may contain PRINT$s. At our site, we gave access to all cabinets. Limits on IOs and LLPs is a matter for your review - when one of these limits is exceeded, the PRINT$ is tossed in the bit bucket. At what size PRINT$ do you wish this to happen? The run is restricted from storing RIDs in in cabinets 200-310. You may wish to change that code. You must also register user BPORT-104 with a password of BPORT. You may elect something else, in which case you must update the user manual to reflect the proper user-id and password. At the end of the run is a documentation result which displays when the user executes the run as follows: SENDPRINT$,HELP. You should rewrite this result to meet your site's standards and procedures. At label 002 is a subroutine that contains the RID numbers of all non- registered subroutines and screens. With the exception of the FORMPRINT$ help screens (5B) this is the only place you must make changes if you plan to move RIDs around. 2.4.2. LOOKPRINT$ REGISTRATION This run provides on-line access to the PRINT$s. Register the LOOKPRINT$ run (3B) in your master run registration department. Provide access to all cabinets where PRINT$s may be registered. At the end of this run is a documentation result that is displayed when the user executes the run as follows: LOOKPRINT$,HELP. You should rewrite this result to meet your site's standards and procedures. 10/18/91 Page 8 Rev. 16 LOOKPRINT$ Installation and Maintenance ______________________________________________________________________________ 2.4.3. FORMPRINT$ This run creates a PRINT$ registration form and sends it to the user in charge of the PRINT$ system. FORMPRINT$ CALLs the 10B RID which in turn uses 11B. Register the FORMPRINT$ run (6B) in the master run registration department. Provide access to the cabinet it is registered in. Update the "duty roster" with the user(s) in charge of registration at your site. The delivered run shows two people who alternate "on call" duties based on the day of the month. 2.4.4. MREGPRINT$ REGISTRATION This run registers PRINT$s listed in a registration request form created by FORMPRINT$. MREGPRINT$ CALLs the 7B RID. Originally the "MREG" stood for multiple registration but at our site it become known as "mega-reg" during the time when we converted the bulk of our jobs. Register the MREGPRINT$ run (8B) in the department of, and restricted to, the person assigned to control the job registration process. MREGPRINT$ CALLs 7B so the actual registration code is common with REGPRINT$. 2.4.5. REGPRINT$ REGISTRATION This run provides a method of registering PRINT$s one at a time. The run CALLs the 7B RID. Register the REGPRINT$ run (9B) in the department of, and restricted to, the person assigned to control the job registration process. REGPRINT$ CALLs 7B so the actual registration code is common with MREGPRINT$. 2.4.6. CALLED SUBROUTINE 7B This routine the the code that performs the actual registration for the two runs which call it (REGPRINT$ and MREGPRINT$). This RID is not registered; its location is defined at label 002 in SENDPRINT$ (1B). This routine is called by REGPRINT$ and MREGPRINT$. SPECIAL NOTICE: A mechanism was created to avoid registering a PRINT$ that will be stored in RIDs reserved for runs or tables (RIDs 1-20). The variable is used to establish the minimum allowed RID. The run contains a commented line that should be activated (take the period off) when you register the first PRINT$ in the drawer where the runs reside. Once registration is complete for the first PRINT$, the line can be commented out again to allow complete use of other data storage drawers. 10/18/91 Page 9 Rev. 16 LOOKPRINT$ Installation and Maintenance ______________________________________________________________________________ 2.4.7. CALLED SUBROUTINE 10B This is the job menu routine for the LOOKPRINT$ run. This RID is not registered; its location is defined at label 002 in SENDPRINT$ (1B). 2.4.8. CALLED SUBROUTINE 13B This is the date and time window routine for the LOOKPRINT$ run. This RID is not registered; its location is defined at label 002 in SENDPRINT$ (1B). 2.4.9. SCREEN 5B The HELP screens for FORMPRINT$ reside here. The location of this report is defined at label two in SENDPRINT$ (1b). There are also internal references, to this rid, on the DSPFORM commands in 5B. 2.4.10. SCREEN 11B This is the job menu screen for the jobs menu routine in 10B. Its location is defined at label 002 in SENDPRINT$ (1B). 2.4.11. SCREEN 14B This is the date and timewindow screen for the date and time routine in 13B. Its location is defined at label 002 in SENDPRINT$ (1B). 2.5. TABLES 2.5.1. INDEX REPORT The PRINT$ index (2B) is where the locations of the PRINT$ reports are recorded. It is where PRINT$s are registered by MREGPRINT$ and REGPRINT$ and where SENDPRINT$ looks to determine where to place an incoming PRINT$. SENDPRINT$ increments the "current" RID through the circular list defined by the LOW and HIGH fields. The time stamp of the most recently received item is recorded in the table; it is only used for displaying the latest activity on the job menu (in LOOKPRINT$). Documentation for this report is found in 4B. 10/18/91 Page 10 Rev. 16 LOOKPRINT$ Installation and Maintenance ______________________________________________________________________________ 3. OPERATION OF THE SYSTEM Only the instructions for the registration functions are described here. Instructions for using the system (from the programmer's perspective) are in a separate document (USERMAN.TXT). 3.1. EXECUTING REGPRINT$ This run adds one line at the top of the PRINT$ index (2B). It uses MAPPER 35 screen commands to build the input screen. The input screen includes a help function (F8) to describe each input field. Before executing this run, you should read the "REGISTERING JOBS" section of the user manual. To operate it, start the run, fill in the form and transmit. The screen will be erased when the job is registered. You may then register another PRINT$ or press function key 10 to stop the run. 3.2. EXECUTING MREGPRINT$ When you receive the registration request from FORMPRINT$, mode switch to 0 and duplicate the message. Check the report for completeness and ensure that the "ERR FLD" and "ERROR" fields are blank. If the requestor left the mode and type fields blank, you will have to fill in these values. If you wish to review the highest registered RIDs in production, enter "LOOKPRINT$,TYPES". Display the request form and execute the MREGPRINT$ run. Each line will be read and the PRINT$ registered. When the request form is re-displayed, check the "ERR FLD" and "ERROR" fields. "ERR FLD" will display the field number if an error occurs and "ERROR" will hint at the problem. 3.3. MISCELLANEOUS NOTE When registering a PRINT$, you have the option of having SENDPRINT$ initiate a run each time that PRINT$ is received. The optional run must be registered for use by BPORT-104. You should review this matter for compliance with your own security policy. @END SENT @ELT,IQD UUSIG*1091-001-001.USERMAN/DOC,,SENT,,DOC LOOKPRINT$ User Manual Peter G. Madsen MAPPER Coordinator FREDERICK and NELSON 08/21/91 08/21/91 Page 2 Rev. 48 LOOKPRINT$ _________________________________________________________________________________ TABLE OF CONTENTS 1. OVERVIEW OF THE SYSTEM................................................... 3 1.1. WHO CAN USE THE SYSTEM.............................................. 4 1.2. REGISTERING JOBS.................................................... 4 1.2.1. REGISTRATION FORM................................................... 4 2. OPERATION OF SENDPRINT$ AND LOOKPRINT$................................... 5 2.1. SENDING THE PRINT$ FILE TO MAPPER................................... 5 2.1.1. BUILDING YOUR ECL.............................................. 5 2.1.2. SAMPLE ECL..................................................... 5 2.1.3. BUILDING YOUR ECL IN MAPPER.................................... 6 2.1.4. EXAMPLE MAPPER CODE............................................ 6 3. VIEWING STORED PRINT$ LISTINGS........................................... 7 08/21/91 Page 3 Rev. 48 LOOKPRINT$ _________________________________________________________________________________ 1. OVERVIEW OF THE SYSTEM This system, called LOOKPRINT$ (or SENDPRINT$) makes it possible to easily send job listings to MAPPER terminals or to the MAPPER data base. People who use this system can reduce printing expenses and paper storage. They also have on-line access to their PRINT$s via a menu. By including a simple ECL addition, a PRINT$ is sent to MAPPER rather than the printer. With proper placement of the @SYM statement, you can choose to have aborted jobs produce printed listings. You may also print the PRINT$ through standard MAPPER functions. A MAPPER run called SENDPRINT$ handles the incoming PRINT$ and sends it to a station or stores it in a registered location. When registering a job in the SENDPRINT$ list, you may specify the number of retained cycles and retention days. The number of retained PRINT$s should reflect the frequency of inquiry. You may also instruct SENDPRINT$ to initiate a MAPPER run which will process the PRINT$ or perform a given task each time the batch job is run. A MAPPER run called LOOKPRINT$ provides access to the stored PRINT$ reports. Each job is registered to a specific MAPPER department and access is restricted to users in that department. To assist in selecting a PRINT$, LOOKPRINT$ provides a menu of job names and job descriptions. 08/21/91 Page 4 Rev. 48 LOOKPRINT$ _________________________________________________________________________________ 1.1. WHO CAN USE THE SYSTEM One of our goals for this system was to have few restrictions. Any person with authority to create and execute batch jobs can send their ECL listings to MAPPER. You can send a PRINT$ to your MAPPER station without registering it. If you wish to automatically save the PRINT$, you must have the MAPPER Coordinator register the job (see "REGISTERING JOBS"). All MAPPER users can run LOOKPRINT$ but people only have access to PRINT$s registered in their current department. This reduces the size of job menus and provides a measure of security. 1.2. REGISTERING JOBS The MAPPER staff will register jobs for you. Both production and test (personal) jobs can be registered. To make this task simple for both you and the MAPPER support people, we created a run for entering the information required to register a job. 1.2.1. REGISTRATION FORM To display the registration form (report), enter FORMPRINT$ and transmit. The report contains the following fields: DEPT: MAPPER department of users who will use LOOKPRINT$ JOB NAME: Unique job identifier MOD: Mode (cabinet) where data is to be placed (optional) T: Type (drawer) where data is to be placed (optional) RIDS: Number of Reports to keep (number of cycles) RUN: Name of MAPPER run which will process the PRINT$ (optional) SAV DAY: Number of days that the PRINT$ is safe from deletion (the default is seven days at our site) COMMENTS: Description of job for LOOKPRINT$ menu When you are finished entering the required information, press function key 1 (F1) to send it to the MAPPER staff. The run will send the request to the person on duty for registering PRINT$s. He or she will notify you when the registration is complete. 08/21/91 Page 5 Rev. 48 LOOKPRINT$ _________________________________________________________________________________ 2. OPERATION OF SENDPRINT$ AND LOOKPRINT$ 2.1. SENDING THE PRINT$ FILE TO MAPPER This section describes ECL requirements and how to direct your PRINT$ to a MAPPER terminal and/or save it. 2.1.1. BUILDING YOUR ECL Examine the sample ECL below. It contains two parameters for which you may provide values. The parameters are called and . The parameter may be up to four (4) characters long and must be numeric. If a valid station number (also called UNIT or PID) is entered, the PRINT$ file will be sent to the station. If the station number is not valid, the file will be sent to the MAPPER Coordinator's station. If the station number is not to be used, then just enter the comma to terminate the parameter (spaces are not allowed). The parameter is used to identify a storage location to receive the PRINT$ listing. Before this parameter can be used, the job name must be registered by the MAPPER Coordinator. The job name must be unique and we advise you to make it the same as, or similar to, the batch run id. The parameter takes precedence over the parameter. The second @MSG,N command and the ENDRD$ line terminate the scan of the batch port queue by the batch port process. If the @MSG,N/ENDRD$ sequence is not included, extra lines may occasionally be appended to the end of your PRINT$. The extra lines are the lines preceding the BPRUN$ in the next file queued to MAPPER's batch port. The lines are harmless but occasionally raise a question about their origin. 2.1.2. SAMPLE ECL ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³@RUN <===== Your run card goes here ³ ³@MSG,N ; ³ ³BPRUN$ SENDPRINT$,, BPORT-104,104,BPORT 000,OPEN,F ³ ³@SYM PRINT$.,,MAPPER ³ ³ . ³ ³ . <===== Put ECL for your job here ³ ³ . ³ ³@MSG,N ; ³ ³ENDRD$ ³ ³ . <===== Move the SYM statement down here if you want the ³ ³ PRINT$ printed in case the job aborts ³ ³@FIN ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ 2-1 Sample ECL 08/21/91 Page 6 Rev. 48 LOOKPRINT$ _________________________________________________________________________________ 2.1.3. BUILDING YOUR ECL IN MAPPER With the SENDPRINT$ run, it is convenient to start batch jobs from MAPPER and have the listing returned to the station that initiated the job. To accomplish this, your MAPPER run must capture the station number and insert it into the ECL. Refer to the example below which illustrates the following four steps: First, compose and store your ECL in a MAPPER report. Use the the sample ECL, shown above, as a guide. In the BPRUN$ statement, substitute the character string "#unit" for the parameter and leave the parameter blank. The RID with the ECL must have proper MAPPER headers for the LCH command to work. Second, in the MAPPER run which starts the batch job, insert code similar to the example MAPPER code shown below. Third, execute the MAPPER run. The ECL will be executed and the PRINT$ will be routed back to MAPPER. Fourth, press the Message Waiting key when the terminal beeps. 2.1.4. EXAMPLE MAPPER CODE In this sample, replace the "m,t,r" in the LCH command with the location of the report containing your ECL. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³@ Ldv,w i4=STNUM$ . Capture the station number ³ ³@ Ldv,p = . Remove any spaces ³ ³@ Lch,m,t,r AF 2-79 '#unit'/ . Insert station number ³ ³@ Ln-,-0,2,4 . Remove headers ³ ³@ Str,-0 . Initiate the batch job ³ ³@ Brk,0,a . Display a start message and ³ ³ ³ ³ The job has been started. ³ ³ You will receive a message when it is complete. ³ ³ ³ ³@ Gto End . Terminate the run ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ 2-2 Example MAPPER code 08/21/91 Page 7 Rev. 48 LOOKPRINT$ _________________________________________________________________________________ 3. VIEWING STORED PRINT$ LISTINGS A. Sign on to MAPPER. B. On the top line, enter "LOOKPRINT$" and transmit. A menu of all jobs registered in your MAPPER department will appear. To bypass the menu, you may enter "LOOKPRINT$,job". C. If the job you want is shown, tab to it and transmit. The most recently stored PRINT$ will be displayed. If more than one PRINT$ is retained in MAPPER, the function keys can be used to display earlier or later listings. Since the PRINT$s are in a circular list, the RollFw and RollBk functions will wrap around when they reach the end of the list. For example, with the most recent PRINT$ in display, you go direct to the oldest PRINT$ by selecting the RollFw function key. When you are done, press function key 10, then sign off of MAPPER. D. To limit the jobs appearing on the menu, you may tab to the LOCATE field and enter a string of characters which appear in the menu lines desired. You may enter a portion of the job name, a word in the description, or a portion of the time stamp (Last run). Press transmit after entering your locate parameter. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ ³ ³ ___________________________________ PRINT$ ___________________________________ ³ ³|Locate: Last run |³ ³| PETER Personal test job for Madsen 910729 120502 |³ ³| SALLY Personal test job for Coates 910811 120601 |³ ³| JOHN Personal test job for Ahlers 910315 120523 |³ ³| |³ ³| |³ ³|______________________________________________________________________________|³ ³ 1 2RollFw 3RollBk 4Menu 5 6 7 8Help 9 10Quit ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ 3-1 Sample LOOKPRINT$ menu Functions: (F2) RollFw - Advances the PRINT$ menu to the next screen of jobs. (F3) RollBk - Returns the PRINT$ menu to the previous screen of jobs. (F4) Menu - Returns to entire list of PRINT$s if a subset was selected. (F8) Help - Displays message to select a job by pressing transmit. (F10) QUIT - Terminates the run. @END SENT @ELT,IQD UUSIG*1091-001-001.1B,,SENT,,ELT .DATE 18 OCT 91 17:07:40 RID 1B 18 OCT 91 MADSEN .@991231 RUN: SENDPRINT$ Author: Madsen *PURPOSE: Send the PRINT$ to a terminal *VERSION: 2.100 Added selection by time stamp window. *=============================================================================== :L1=11,2=18,3=26,90=80,120=87,130=88,140=89,150=90,161=95,162=98,163=101,164=104,165=107,169=110,170=117,180=123 @ Rnm -1 . }Save result while setting up @ Rsr 001 . }Application wide variables @ Gto 003 . }Skip over subroutine @. *** Application wide variables } @001 Rsr 002 . }Application RID variables @ Dvs,ETYPE$, \ } 'DEPT','JOB','MOD','T','RID','LOW','HIGH','RUN','SAV',\ 'COMMENTS','DATE','TIME' \ i,a,i,a,i,i,i,h,i,\ s,a,