JHS Operator s Guide

Transcription

1 JHS Operator s Guide

2 COPYRIGHT Licensed Materials - Property of Systemware, Inc. Copyright Systemware, Inc., All rights reserved. Use, duplication, or disclosure restricted by contract with Systemware, Inc. DISCLAIMER Systemware, Inc. reserves the right to revise this publication and to make changes from time to time in the content hereof without the obligation of Systemware, Inc. to notify any person of such revision or changes. Systemware cannot be responsible for product problems caused by unsupported versions of operating system software or other vendor software such as application-server or Web software packages. TRADEMARKS Systemware, the Systemware logo, and all Systemware product components and logos are either registered trademarks or trademarks of Systemware, Inc. All other trademarks are the properties of their individual owners. DOCUMENTATION AND TECHNICAL SUPPORT The following documentation comprises the Systemware package for Xptr and related software: JHS Administrator's Guide SD JHS User's Guide SD JHS Operator's Guide SD Implementation Guide SD System Manual SD Message Manual SD JCL Utilities SD Installation Manual SD For information regarding this documentation or to inquire about receiving additional documentation, contact: documentation@systemware.com Systemware, Inc., Dallas Parkway, Suite 1100, Addison, Texas For product or technical support and other information, contact Systemware: Phone (972) Fax Web site Customer information portal SD (March 2007) AUDIENCE This manual is intended for persons involved in operating and maintaining Systemware JHS software. The procedures discussed in this manual assume a knowledge of z/os utilities, JCL, VSAM, and CICS. For detailed information on implementing and administering JHS, refer to your company JHS administrator or the JHS Administrator s Guide.

3 Contents Introduction 5 Manual audience 5 Chapter descriptions 5 Summary of z/os console commands 6 Chapter 1 z/os console procedures 7 Introduction 7 Starting JHS 8 Quiescing JHS 8 Stopping JHS 8 Stopping JHS on another CPU 8 Starting and stopping drivers 10 Starting and stopping collectors 10 Archiving SYSOUT 11 Archive command syntax 11 Clearing SYSOUT from the data base 16 Displaying tape writer status 16 Resetting the tape writer 17 Starting a trace 18 Stopping the trace 21 Restarting the trace 21 Updating system parameters 21 Updating SYSOUT selection criteria 21 Invoking a system dump 22 Security exit message 22 Chapter 2 JHS console procedures 23 Access from screen 23 O01: Operations screen 24 JHS output control 25 O30: Output Processing (-O.OUT) 26 Selecting the list to display (BND, RPT, OWE, DVR, JOB) 26 Managing requests to restore from archive 43 JHS Operator s Guide R4.2 (March 2007) 3

4 Index 61 O80: Archive Status (-O.ARC) 44 User management 53 System control 55 Display virtual storage usage 56 System commands 56 4 Systemware, Inc.

5 Introduction This manual describes procedures used at MVS and JHS consoles to monitor and control JHS. Numbered JHS messages are listed here since most numbered messages are issued only to MVS consoles. Manual audience This manual is intended for computer operations and technical support personnel. Chapter descriptions Chapter 1 - describes MVS console procedures. Chapter 2 - describes JHS console procedures. JHS Operator s Guide R4.2 (March 2007) 5

6 Summary of z/os console commands Summary of z/os console commands Start JHS Quiesce JHS Stop JHS Stop JHS on another CPU Archive SYSOUT to tape Clear SYSOUT from JHS Data Base S JHSMAIN F JHSMAIN,Q P JHSMAIN F JHSMAIN,STOP CPUB or F JHSMAIN,STOP ALL F JHSMAIN,ARCHIVE F JHSMAIN,CLEAR Display tape writer status Reset tape writer Display tape volume status Indicate tape volume not available Indicate tape volume available Start trace Stop trace Restart trace Update system parameters Update SYSOUT selection criteria System dump (continue) System dump (terminate) Close JHSLOG F JHSMAIN,D W F JHSMAIN,RESET jname jnum or F JHSMAIN,RESET F JHSMAIN D VOL volume F JHSMAIN,R VOL volume F JHSMAIN,A VOL volume F JHSMAIN,TRACE Reply to SW#0251 w/ "PAUSE" or "STOP" Reply to SW#0251 w/ "GO" F JHSMAIN,SETPARM name value or F JHSMAIN,SP name value F JHSMAIN,SP SELECTMBR member F JHSMAIN,DUMP C JHSMAIN,DUMP F JHSMAIN,WL 6 Systemware, Inc.

7 1 z/os console procedures Introduction This chapter contains procedures for controlling JHS from an OS console. Most of the procedures can also be done from a terminal logged on to JHS with operator authority. The phrase "JHSMAIN started task" refers to the JHS data base system on the MAIN CPU. The MAIN CPU is the CPU on which JHS accumulates SYSOUT, creates archive files, and retrieves SYSOUT from archive files. Only a single CPU can be designated the MAIN CPU for a JHS data base system. The phrase "JHSCOMM started task" refers to the JHS data base system on any COMM CPU. All other CPUs that access the JHS data base on the MAIN CPU must run the JHSCOMM started task. The phrase "JHS started task" refers to a JHS data base system on any CPU, either MAIN or COMM. The actual started task names may differ from the names used here. Note: jhsstartedtaskname" and "JHSMAIN" both refer to the started task name which is used to invoke execution of JHS on the MAIN CPU. They are used here interchangeably. JHS Operator s Guide R4.2 (March 2007) 7

8 Starting JHS Starting JHS Only a single JHS started task may execute on a CPU at a time. Only one JHSMAIN started task may be executing in a CPU complex at a time. The JHSMAIN and JHSCOMM started tasks may be started in any sequence. Step Action 1 Verify that no other JHS started task is running on this CPU. 2 If the JHSMAIN system is to be started, verify that JHSMAIN is not running on any other CPU in the CPU complex. 3 To start the JHSMAIN started task enter: STOP ALL S JHSMAIN S JHSCOM To start the JHSCOMM started task enter: 4 When message SW#0001I is displayed, JHS is operational.when message SW#0236I is displayed, JHS can be accessed from terminals in native VTAM mode. JHS native VTAM mode is an optional facility. Quiescing JHS The Q or QUIESCE command prepares JHS for an orderly shutdown. It prevents new work from being started, but allows work in process to proceed to an orderly conclusion. Users at terminals are allowed to continue but no new users are allowed access. The accumulation of SYSOUT from SPOOL is stopped at the end of the current job. The shutdown process started by the QUIESCE command cannot be reversed; JHS must be stopped and restarted. To quiesce JHS enter: F JHSMAIN,Q Stopping JHS The P or STOP command interrupts most work in process. Stop JHS with the OS STOP (P) command. If the JHS started task name is JHSMAIN enter: P JHSMAIN Stopping JHS on another CPU If the JHSMAIN started task is running, the stop command may be directed to a CPU other than the CPU the command is entered on. To specify another CPU use the SMF identifier for the other CPU on the stop command. For example, to stop CPUB from CPUA enter: F JHSMAIN,STOP CPUB 8 Systemware, Inc.

9 Chapter 1 OS Console Procedures 1 z/os console procedures JHSMAIN running on the MAIN CPU can be stopped by a command running on a COMM CPU; however, very little productive can ensue since all commands must go through JHSMAIN on the MAIN CPU. To stop JHS on all CPUs, use ALL for the SMF identifier. F JHSMAIN,STOP ALL JHS Operator s Guide R4.2 (March 2007) 9

10 Starting and stopping drivers Starting and stopping drivers To start an Xptr driver, enter: F JHSMAIN,START DRIVER name number where name is the name of the collector and number is the number assigned by the system. It is displayed on panel O32 (O.OUT.DVR) as three digits following the fourcharacter driver name. The driver number may change when your administrator installs a new INSTLIB output driver member.. To stop an Xptr driver at the end of the current job, enter: F JHSMAIN,STOP DRIVER name number Starting and stopping collectors To start a collector, enter: F JHSMAIN,STARTCOL name where name is the name of the collector. To stop a collector at the end of the current job, enter: F JHSMAIN,STOPCOL name To stop a collector at the end of the dataset currently being collected, enter: F JHSMAIN,STOPCOL name EOD To stop a collector immediately, enter: F JHSMAIN,STOPCOL name INT 10 Systemware, Inc.

11 Chapter 1 OS Console Procedures 1 z/os console procedures Archiving SYSOUT The ARCHIVE command copies SYSOUT from the online disk JHS data base to tape. The actual transfer is done by a job submitted by JHS as a result of this command. The archive process does not interrupt any JHS processing. The ARCHIVE command is usually issued automatically based on time of day and day of week as described in the JHS Administrator's Guide. To archive all SYSOUT use: F JHSMAIN,ARCHIVE To archive all jobs (if Xptr is also installed) use: F JHSMAIN,ARCHIVE JCL Jobs that need to be kept on the JHS data base for similar time periods can be managed in Archive groups. These groups are defined and maintained by the JHS system administrator. The primary use of archive groups is to cause jobs that are to be retained for similar time periods to be archived together. For more information on Archive groups, see the JHS Administrator's GuideTo archive all jobs belonging to a specific archive group, include the archive group number after JCL. For example, to archive all jobs in group two use: F JHSMAIN,ARCHIVE JCL 2 Archive command syntax JHS can archive jobs to different devices, e.g. tape, disk, etc. Archiving can be to any of 99 groups, each having its own archiving configuration. Each group can contain up to 99 levels, one of which is the initial or primary archive, another the secondary or backup archive, and each of the rest configured to archive data from the initial archive to a specific device. Typically, archiving times and devices are preset and automatically performed. You can manually control the archiving by: Interrupting the archiving process for selected archive groups Suspending the archiving of scheduled jobs Controlling the migration of archive files between levels within an archive group Deleting unwanted archive files Interrupting archiving Use the ARCHIVE INT and ARCHIVE CANCEL commands to stop archiving before normal archive job completion. The INT option terminates the archive process in a normal start after the next job. The CANCEL option disconnects any active archive process and leaves the process in an error state that will repeat the creation of the archive at a later time. Both commands suspend future archiving until you issue an ARCHIVE command or restart the data base. Specify a group or range of groups using nn or nn-nn., where nn is a decimal number. From an OS command line, enter: F JHSMAIN,ARCHIVE [JCL grouprange] INT F JHSMAIN,ARCHIVE [JCL grouprange] CANCEL JHS Operator s Guide R4.2 (March 2007) 11

12 Archiving SYSOUT grouprange, levelrange, and archiverange can be a single number or a range of consecutive numbers between 1 and 15, i.e. nn-nn, where nn is a decimal number. You must supply the JCL REPORT argument if you specify a group range. Suspending archiving To prevent the archiving of currently SCHEDuled jobs,, enter either of the following commands:. F JHSMAIN,ARCHIVE [JCL grouprange] INT F JHSMAIN,SP MAXARCHIVES 0 For archiving to occur, the MAXARCHIVES parameter must have a value other than zero. To reset the MAXARCHIVES parameter to its default value, enter: F JHSMAIN,SP MAXARCHIVES Closing an archive tape To close an archive tape, enter from an OS command line: F JHSMAIN,CLOSEARC [JCL REPORT] [grouprange] [L levelrange] [# archiverange] Specify a group, level, or archive, or a range of any of these using nn or nn-nn., where nn is a decimal number. You must specify JCL (or REPORT) if you specify a group range. Migrating archives to other storage areas After jobs are copied to an initial archive file, additional copies of the archive file can be made for backup or for better utilization of archive media. Archive migration is the process of making these copies under the control of the data base system. The status of each migrated archive file is: SCHEDULED The source of the migration has been created. The process is waiting for a time or command. READY The file is ready for migration. The process is waiting for resources. COMPLETE The file has been successfully created. HELD An operator HOLD command has been entered for this file. ERROR An error was encountered while attempting to create this copy. No further attempts will be made while the archive file is in this state. The status of each migrated archive file is retained across data base stops and starts. The ARCMIG command controls the archive migration process. The general format of the ARCMIG command is: F JHSMAIN,ARCMIG [JCL grouprange] [L levelrange] [# archiverange] [SCHED /HOLD/RELEASE/INT/CANCEL] Archive files are organized by groups, levels, and archive number. All archive files with the same archive number within a group are copies of the same data. A level must be specified if an archive number is specified. A group must be specified if a level is specified. JCL (or REPORT) must be specified if a group is specified. Groups, levels, and archive numbers may be specified as a range of values, i.e. nn-nn. 12 Systemware, Inc.

13 Chapter 1 OS Console Procedures 1 z/os console procedures Creating scheduled archive migration files This command causes all SCHEDULED archive files to become READY. Issue this command to start the archive migration process for levels that require a start command. F JHSMAIN,ARCMIG [JCL grouprange] [L levelrange] Do not specify an archive number. For example, to initiate migration for job groups 3 and 4, level 2, use: F JHSMAIN,ARCMIG JCL 3-4 L 2 To initiate migration for all SCHEDULED files, use: F JHSMAIN,ARCMIG Suspending archive migration To prevent the creation of currently SCHEDULED archive migration files, enter either of the following commands:. F JHSMAIN,ARCMIG [JCL grouprange] [L levelrange] [# archiverange] HOLD F JHSMAIN,SP MAXMIGRATES 0 Restarting archive migration To restart archive migration of files in HELD and ERROR status, enter: F JHSMAIN,ARCMIG RELEASE Archive migration can be suspended due to either an ARCMIG HOLD command or an error during prior archive migration for an archive file. To restart only HELD archive files, enter: F JHSMAIN,ARCMIG [JCL grouprange] [L levelrange] RELEASE To return files in both HELD and ERROR status to SCHEDULED status, enter: F JHSMAIN,ARCMIG [JCL grouprange] [L levelrange] [# archiverange] RELEASE For archive migration to occur, the MAXMIGRATES parameter must have a value other than zero. To reset the MAXMIGRATES parameter to its default value, enter: F JHSMAIN,SP MAXMIGRATES Scheduling archive migration for old archives Migration is managed by archive levels. When you add an archive level to the system, the archive files created before the date that the new level level is added are not automatically subject to migration. You must explicitly request these files by group, level, and archive number. The command format is: F JHSMAIN,ARCMIG [JCL grouprange] [L levelrange] [# archiverange] SCHED If the source files were created prior to the level definition, allow the archive migration to complete before terminating the system. You may need to issue an additional ARCMIG command may to initiate migration. JHS Operator s Guide R4.2 (March 2007) 13

14 Archiving SYSOUT Stopping archive migration You may use the ARCMIG INT and ARCMIG CANCEL command to stop an active migration process. These commands prevent any future migration processing for the groups/levels. A system restart or an ARCMIG RELEASE re-enables migration processing. Migration is performed on an archive file basis. The ARCMIG INT command suspends the migration process between archive files. Use one of the following commands to prevent further migration before terminating the system. Current migration process will complete normally. F JHSMAIN,QUIESCE F JHSMAIN,SP MAXMIGRATES 0 F JHSMAIN,ARCMIG [JCL grouprange] [L levelrange] INT The ARCMIG CANCEL command disconnects any active migration process. The job producing the archive file may end with errors. The archive file may be placed in the ERROR state. Syntax is: F JHSMAIN,ARCMIG [JCL grouprange] [L levelrange] CANCEL Deleting archives Archive files are deleted after their contents (job output) have been deleted, either because they have expired or because someone has manually deleted the output. This process includes removing records from the data base and deleting the actual archive file. You may delete specific copies (levels) before this time. Normally this process is automated.. The ARCDEL command can override normal archive deletion processing. The status of each archive file with respect to deletion processing is: SCHEDULED The archive has been created.. The process is waiting for the contents to expire, a time or a command. READY The file is ready for deletion. The process is waiting for resources. COMPLETE The file has been successfully deleted. HELD An operator HOLD command has been entered for this file. ERROR An error was encountered while attempting to delete this copy. No further attempts will be made while the archive file is in this state. The status of each archive file is retained across data base stops and starts. The ARCDEL command controls the archive deletion process. The general format of the ARCDEL command is: F JHSMAIN,ARCDEL J grouprange L levelrange # archiverange [HOLD/RELEASE/INT/CANCEL/FORCE] Archive files are organized by groups, levels, and archive number. All these arguments are mandatory for the ARCDEL command. All archive files with the same archive number within a group are copies of the same data. A level must be specified if an archive number is specified. A group must be specified if a level is specified. Groups, levels, and archive numbers may be specified as a range of values. 14 Systemware, Inc.

15 Chapter 1 OS Console Procedures 1 z/os console procedures Deleting specific archive files This command causes deletes archive files from the system. CAUTION: After all copies of an archive file are deleted, the jobs cannot be restored or printed from the archive. F JHSMAIN,ARCDEL J grouprange L levelrange # archiverange [FORCE] If FORCE is not specified, the system verifies that at least 1 copy (level) of the archive file will exist after the ARCDEL command is processed. Suspending archive deletion This command prevents the deletion processing of currently SCHEDULED archive files. F JHSMAIN,ARCDEL J grouprange L levelrange # archiverange HOLD Restarting archive deletion Archive deletion can be suspended due to either an ARCDEL HOLD command or an error during prior deletion for an archive file. To restart archive deletion, use: F JHSMAIN,ARCDEL J grouprange L levelrange # archiverange RELEASE Changing archive file unit You can change the unit names used to allocate tape drives when SAMEUNIT YES is specified, to re-allocate a named group of tape drives. Syntax is: F JHSMAIN,ARCCMD J group L level # [archiverange] NEWUNIT=name No response message appears in the JHSLOG if the device for the level does not support the command. Marking archive file as onsite or offsite You can mark an archive file as being unavailable because it has been removed to offsite storage. Syntax is: F JHSMAIN,ARCSTAT [J group L level # archive] ONSITE OFFSITE CAUTION: ARCSTAT OFFSITE ONSITE issued without other argument causes ALL archives on the system to be set to the specified status. ARCSTAT OFFSITE flags the specified archive file(s) as not available for retrieval. Use the ARCSTAT ONSITE command to mark archive file(s) as available for use. For example, to indicate that archive files 100 to 110 in JCL group 5, level 3 have been moved to offsite storage, use: F JHSMAIN,ARCSTAT J 5 L 3 # OFFSITE JHS Operator s Guide R4.2 (March 2007) 15

16 Clearing SYSOUT from the data base Clearing SYSOUT from the data base The CLEAR command causes all SYSOUT to be written to tape and JHS to terminate automatically. This command is used prior to reformatting the JHS data base for SYSOUT storage. It is not required during the normal operation of JHS. This command should only be used as requested by the persons responsible for the JHS system. To start archiving and stop JHS enter F JHSMAIN,CLEAR If JHS does not submit a job within a few minutes, use the Display Tape Writer Status procedure and the Reset Tape Writer procedure described below as required. Verify that message SW#0107: CLEAR PROCESSING COMPLETE is issued just prior to JHS system termination. Displaying tape writer status JHS produces the archive tape with a job called the tape writer job. This job must be submitted by JHS. JHS submits only one such job at a time. The tape writer job identifies itself to JHS when it starts. If JHS does not know the correct status of the tape writer job (not submitted, waiting for execution, executing) then the archive tape creation process cannot proceed. If tape writer processing has been suspended due to tape or disk I/O errors, the errors are ignored and the tape writer process is restarted. A similar job is used to restore SYSOUT from archive. Step Action 1 To display tape writer status enter: F JHSMAIN,D W JHS responds with message SW#1215I if no tape writer jobs are pending, or a SW#0206 message listing a tape writer name. 16 Systemware, Inc.

17 Chapter 1 OS Console Procedures 1 z/os console procedures Resetting the tape writer The RESET command informs JHS that the tape writer process should be restarted. It should be used in the following situations: The tape writer status listed in SW#0206 is incorrect. An error such as a permanent tape error occurred suspending archive tape creation. Step Action 1 Display tape writer status with: F JHSMAIN,D W JHS will respond with message SW#1215I if no tape writer jobs are pending, or a SW#0206 message listing a tape writer name. 2 If SW#0206 lists a job name and job number, enter the job name and job number in a RESET command. For example, to reset job JHSTAPE, job number J487, enter: F JHSMAIN,RESET JHSTAPE J487 CAUTION: DO NOT USE THE RESET COMMAND IF THE JOB LISTED BY SW#0206 IS EXECUTING. UNPREDICTABLE RESULTS COULD OCCUR, INCLUDING A LOSS OF DATA. 3 If a SW#1215 message is displayed, or SW#0206 does not list a job name and job number, enter the RESET command as follows: F JHSMAIN,RESET JHS Operator s Guide R4.2 (March 2007) 17

18 Starting a trace Starting a trace The JHS trace facility records internal JHS activity. The trace should only be used under the direction of personnel responsible for JHS software maintenance. The trace may be started and stopped without interrupting normal JHS processing. Trace information is recorded by the JHS started task to a disk file and/or an internal memory resident trace table. In either case, when the table or file fills up with trace information, it will wrap and continue to record by overlaying the oldest data. The instructions for running the trace at a customer site should include a list of trace ID points and a dataset name or DD name or size. The available trace points in JHS are: ID 2: ID 3: ID 10: ID 29: ID 30: ID 31: ID 32: ID 33: ID 34: ID 35: ID 37: ID 38: ID 70: ID 73: ID 74: ID 75: ID 76: ID 77: ID 78: ID 80: ID 82: ID 83: ID 85: ID 96: ID 97: ID 98: ID 99: ID 103: Transaction received in JHS address space. Transaction completed in JHS address space. Console and automatic command entry Line Edit exit Security exit parameters upon return from exit. Initialization exit Job record build exit Dataset purge exit Overflow exit Rules exit Job group exit Archive deletion exit (data traced is ACRREC) Subsystem request for SYSOUT after return from JES (data is return code, SSOB, SMF job log number) SYSOUT characteristics exit Subsystem interface prior to call to JES Security exit parameters prior to calling exit User security exit to trace routine Line read from SPOOL Index variable stored by Line Edit Exit. Accept archive restore request Read DSIREC for SYSOUT to be restored Read JSDREC for SYSOUT to be restored Delete job archive reference after job not found on archive VSAM buffer pool statistics VSAM IO performance BDAM buffer pool statistics BDAM IO performance Data received from VTAM terminal 18 Systemware, Inc.

19 Chapter 1 OS Console Procedures 1 z/os console procedures ID 106: ID 152: Data sent to VTAM terminal Write index variable values to data base Please see the System Manual for a detailed description of the JHS internal trace facility. The trace facility can be started automatically during system initialization, by entering the reply options from the console, or by referencing a member containing these replies. To start the trace using a predefined member use: F JHSMAIN, SP TRACEMBR name where name is a member name in the system parameter library. If the parameters in the member are incomplete, you will be prompted to complete the parameters from the console in the same manner as if you started the trace from the console. Step Action 1 To start the trace enter: F JHSMAIN,TRACE The above command will cause message SW#0250: ENTER TRACE OPTIONS to be issued as a WTOR until all trace options have been specified. The replies are: DSN trace.dataset.name ID trace.points DSNPFX <dsname> UNIT <unitname> VOL <volser> CYL <number> SIZE <number> RESET <idlist> CANCEL END 2 To enter a trace dataset name, reply to SW#0250 with DSN name. For example, to specify dataset JHS.TRACE.DATA reply: DSN JHS,TRACE DATA JHS Operator s Guide R4.2 (March 2007) 19

20 Starting a trace JHS will respond with message SW#0250: ENTER TRACE OPTIONS 3 In addition to sending trace information to a disk file, it can be sent to a table in internal memory. Although this is rarely needed, it can provide additional information regarding the activity right before a dump is taken. The table is then retrieved from the dump listing. The trace table will wrap around if it fills up. To enter a trace table size, reply to SW#0250 with SIZE number. For example, to specify a 16K trace table reply: SIZE 16 JHS will respond with message SW#0250: ENTER TRACE OPTIONS 4 To enter trace ID points, reply to SW#0250 with ID list. For example, to specify ID points 23 to 29 reply: ID ID 31 For example, to specify ID point 31 reply: JHS will respond with message SW#0250: ENTER TRACE OPTIONS 5 DSNPFX <DSNAME> is a high level qualifier of a new dataset that will be used as the trace file. The trace program will append.ddyymmdd.thhmmss to generate a full dataset name. The unit response must be made prior to the PSNPFX response. The optional VPOL and CYL responses must be made prior to the DSNPFX response if they are to be used. 6 UNIT <UNITNAME> is the unit name for allocation of a new trace dataset by the DSNPFX response. This must be made prior to the DSNPFX response. 7 VOL <VOLSER> is the volume serial number for allocation of a new trace dataset by the DSNPFX response. If omitted then no explicit volume will be requested and only unit will be used. This response must be made prior to the DSNPFX response to be effective. 8 CYL <NUMBER> This is the new trace file size in cylinders, as used by the DSNPFX response. If omitted then any new trace file will be allocated as 1 cylinder. If the trace file becomes full then the oldest entries are overlaid with new data. This response must be made prior to the DSNPFX response to be effective. 9 After all trace options have been entered, reply to SW#0250 with END to start the trace, or CANCEL to prevent trace activation. Either END or CANCEL must be entered prior to stopping JHS. JHS will display SW#0251: TRACE ACTIVE when the trace has started. 20 Systemware, Inc.

21 Chapter 1 OS Console Procedures 1 z/os console procedures Stopping the trace The JHS trace facility records internal JHS activity. The trace may be started and stopped without interrupting normal JHS processing. The trace facility is also automatically stopped during JHS shutdown. To temporarily stop the trace without releasing the trace file, reply to SW#0251 with PAUSE. To stop the trace and release the trace file, reply to SW#0251 with STOP. Restarting the trace This procedure may be used to reverse the effect of the PAUSE command described above. To restart trace activity after a PAUSE reply to SW#0251, with GO. Trace options remain unchanged. Updating system parameters Some JHS system parameters can be modified while JHS is executing with the SETPARM command. Use the command SETPARM? (or SP?) to obtain a list of parameters that can be updated with the SETPARM command. A SW#1049 message will appear in the log for each parameter that can be updated with the SETPARM command. JHS system parameters are initially obtained from the partitioned dataset allocated to the PARMLIB DD statement. JHS synchronizes the update with its processing. This may cause a delay between the time that the command is entered and the time that change is effected. When the change is successfully completed, message SW#1050 will be issued. If there is an error in updating the system parameter, message SW#1051 will be issued. The general form of the SETPARM command is: F JHSMAIN,SETPARM name value where name and value are the system parameter name and new value. SETPARM may be abbreviated as SP. See the JHS Administrator's Guide for a comprehensive listing of all JHS system parameters. Updating SYSOUT selection criteria To change the SYSOUT classes and jobs processed by JHS, add or update the SYSOUT selection member in PARMLIB; then, issue the following command to cause the update to take effect. F JHSMAIN,SETPARM SELECTMBR member where member is the member name to be read. The change will take effect after the current job is processed. JHS Operator s Guide R4.2 (March 2007) 21

22 Invoking a system dump Invoking a system dump The Dump command dumps the system address space to a OS SYS1.DUMPnn dataset. This is a high speed dump that must be formatted with the OS service aid AMDPRDMP using the PRINT CURRENT control statement. The CPU may appear to stop for a few seconds while dumping common storage. To invoke a system dump and cause JHS to continue, enter the following OS console command: F JHSMAIN,DUMP To invoke a system dump and cause JHS to terminate, enter the following OS console command: C JHSMAIN,DUMP Security exit message The SEC command sends a message to the security exit. The use and format of this command is determined by your installation and implementation of the security exit. The form of this command is: SEC text For example, to send the message SEC REFRESH to your security exit, enter: F JHSMAIN, SEC REFRESH 22 Systemware, Inc.

23 2 JHS console procedures The Operations function has facilities for the control of JHS, including the management of: system shutdown logged on user(s) information archive restore request(s) and control tape writer status and control These facilities are usually restricted to computer operations personnel who are logged onto JHS with user name /SYSTEM/ADMIN or who are given operator authority. Some of these facilities may be available for general use, depending upon the installation options. Access from screen Access operational activity from the Main Activities Menu by entering O into the Command ==> field, or cursoring down to the Operations line, entering any key and pressing ENTER. J MAIN ACTIVITIES JHS Command ===> O Select Command from list below. Place any character next to command or enter command in Command ===> area. - Cmd Description J - Select jobs Press HELP key for further information V - View reports Press END key to exit JHS A - Administration O - Operations Xptr and JHS are software PRO - Profile of options products licensed by and property of L - Select data base Systemware, Inc., Dallas, Texas X - Next application Xptr, JHS, and Systemware are registered trademarks of Systemware. Last user: /SYSTEM/ADMIN JHS Operator s Guide R4.2 (March 2007) 23

24 O01: Operations screen O01: Operations screen The Operations menu is presented, from which any of the operations activities may be selected. J 1 O01: Operations JHS Command ===> arc Select Command from list below. Place any character next to command or enter command in Command ===> area. - Cmd Description IN - SYSOUT collection OUT - Output processing R - Restore archive ARC - Archive status RGN - Regions USR - User management SYS - System control USE - Database Usage Last user: /DEMO/OPS/JHS.OPERATOR The operations screen divides the control facilities into several functions: Command Action IN SYSOUT collection (see Screen O65:) OUT Output processing (see Screen O30: R Archive restore management (see Screen O20:) ARC Archive management (see Screen O10:) RGN Sysplex regions; applies only to Xplx option. USR User management (see Screen O25:) SYS System control (see Screen O05:) USE Database Usage (see Screen O60:) To select a function, enter its code (that is under the Cmd heading) into the Command ===> field, or enter any character to the left of the Cmd. To exit the Operations screen press END (PF3). 24 Systemware, Inc.

25 Chapter 2 JHS Console Procedures 2 JHS console procedures JHS output control JHS has a comprehensive and versatile output control facility that can send selected SYSOUT datasets to any, several, or all of a range of output devices. Several output screens are available for defining the type of output desired. These screens are accessible through the Output Processing screen, reachable through the -O.OUT command. The screens are also directly accessible through commands as follows: Bundle Status Report Status Output Work Element Status Output Driver Status Driver Job Status -O.OUT.BND -O.OUT.RPT -O.OUT.OWE -O.OUT.DVR -O.OUT.JOB JHS Operator s Guide R4.2 (March 2007) 25

26 O30: Output Processing (-O.OUT) O30: Output Processing (-O.OUT) The Output Processor writes SYSOUT to output devices based on predefined instructions or special requests. Screens provide display and control facilities for the processing of SYSOUT from the time it is received until the time distribution is complete. The Output Processor and its display and control facilities are only available on the MAIN CPU for a data base. The Output Processing screen can be selected by entering -O.OUT on the Command ==> line of any screen. J 1 O30: Output Processing Command ===> Select Command from list below. Place any character next to command or enter command in Command ===> area. - Cmd Description BND - List open bundles matching bundle and report name masks RPT - List reports matching report and bundle name masks OWE - List output ready for output drivers matching all masks DVR - List output drivers matching driver name mask JOB - List submitted jobs outstanding Selection criteria: Bundle name mask ==> Report name mask ==> Driver name mask ==> Demand print only ==> (yes/no) Source and User apply to RPT with Demand Print, and apply to all OWE. Source name mask ==> User name mask ==> Selecting the list to display (BND, RPT, OWE, DVR, JOB) The Output Processing display and control facility has these areas (Table 4): BND Bundles Potential combinations of one or more reports sent to one or more distribution in one or more ways. RPT Reports Units of SYSOUT received by the system. OWE Output work elements Actual combinations of one or more reports sent to one or more distribution points in one way. DVR Drivers Modules that write output to external devices. JOB Batch Jobs Jobs submitted from batch drivers On the Output Processing screen and on most lower level screens, the appropriate list can be displayed using commands BND, RPT, OWE, DVR, and JOB, respectively. 1 If you are on a lower level screen, such as Report Control, and enter: BND the Bundle Control list is displayed. In this case, any row select commands (Opt column) on the Report Control screen is ignored. 26 Systemware, Inc.

27 Chapter 2 JHS Console Procedures 2 JHS console procedures Bundles in output processing (-O.OUT.BND) The output processor distributes SYSOUT to bundles and then to output work elements. The Bundle Status screens list the bundles that are currently being handled by the output processor and indicate their current status. After the output processor has converted the bundle into output work elements (OWEs), the bundle control blocks are deleted and cannot be displayed. The Bundle Status screens can be accessed by selecting BND on the O30: Output Processing screen or entering -O.OUT.BND on the Command line of any screen. The Bundle Status display, screens O40:-O42: (Figure 17 through Figure 19), contain columns that can be viewed by scrolling RIGHT and LEFT. J 1 O40: Bundle Status Line 1 Command ===> Scroll ===> PAGE Commands: CLOSE - Close bundle DELETE - Delete U - Update TIME hhmm, PAGES nnn, LINES nnn, HOLD, RLS - Change closure rule Options: S-Select for command CLS-Close DEL-Delete RPT-List rpts Scroll RIGHT for more information Use HELP for additional commands. ---Reports---- Last Opt Bundle All Rcvd Indx Status Command *NO BUNDLES FOUND ******************************BOTTOM OF DATA ******************************* Scrolling RIGHT produces: J 1 O41: Bundle Status Line 1 Command ===> Scroll ===> PAGE Commands: CLOSE - Close bundle DELETE - Delete U - Update TIME hhmm, PAGES nnn, LINES nnn, HOLD, RLS - Change closure rule Options: S-Select for command CLS-Close DEL-Delete RPT-List rpts Scroll LEFT or RIGHT for more information Closure Closure Last Opt Bundle Opened Rule 1 Rule 2 Command **************************** BOTTOM OF DATA ******************************* Scrolling RIGHT again produces: J 1 O42: Bundle Status ROW 1 OF 1 Command ===> Scroll ===> PAGE Commands: CLOSE - Close bundle DELETE - Delete U - Update TIME hhmm, PAGES nnn, LINES nnn, HOLD, RLS - Change closure rule Options: S-Select for command CLS-Close DEL-Delete RPT-List rpts Scroll LEFT for more information Dist Output Last Opt Bundle Pages Lines Pts Modes Serial # Command ******************************** BOTTOM OF DATA **************************** JHS Operator s Guide R4.2 (March 2007) 27

28 O30: Output Processing (-O.OUT) Screens O40-O42: Displayed Bundle Information Last Command The last command issued against this bundle; this column contains ERROR if the command was not successfully completed. The column is cleared when the display is refreshed. Bundle Reports All Reports Rcvd Reports Indx Status ABEND Opened Name of bundle; the full 40 character name is displayed on screen O40. A shortened name consisting of the last 20 characters is displayed on other screens. Number of datasets available for inclusion. Number of datasets received by the output processor for this bundle. Number of datasets defined with indexing in the bundle contents list. Not applicable. Held due to job abend. Date and time the first dataset in the bundle was received by the output processor. Pages Number of pages in the bundle. If the number is followed by K, the value is in the thousands; if the number is followed by M, the value is in the millions. Lines Number of records (lines) in the bundle. If the number is followed by K, the value is in the thousands; if the number is followed by M, the value is in the millions. Dist Pts Not applicable. Output Modes Number of different combinations of output methods and parameters. Serial number An internal identifier for this bundle. Screens O40-O42: Commands/Options Closure Rules Commands Not applicable. CLOSE: DELETE: U: Options S: CLS: DEL: RPT: Close bundle. Delete bundle. Update bundle. Select bundle. Close bundle. Delete bundle. List reports in bundle. Scrolling bundles in output processing displays The Bundle Status screens are lists that can be scrolled using the standard UP and DOWN keys. Additional columns are available by scrolling LEFT or RIGHT. The Find command can be used to select a specific piece of information anywhere on the list. The columns used are based on an internal table that can have data in slightly different columns than on the displays. 28 Systemware, Inc.

29 Chapter 2 JHS Console Procedures 2 JHS console procedures Closing a bundle Closing a bundle causes it to be converted into output work elements and makes it ready for output. After this conversion, the bundle no longer appears on the bundle status list. If additional reports for the bundle arrive later, a new bundle is formed. To close a specific bundle, use: Opt Bundle CLS SP-ST01T2-JES2--JESMSGLG To close all bundles listed, use: CLOSE LIST A group of bundles can also be closed using the select for command feature: Command ===> CLOSE Opt Report S SP-ST01T2-JES2--JESMSGLG SP-ST01T2-JES2--JESJCL S SP-ST01T2-JES2--JESYSMSG To close all bundles in the system, whether listed or not, enter: CLOSE ALL Holding and releasing bundles The HOLD and RELEASE commands can be used to prevent or allow automatic closure. The commands can be used in either the list form or select for command form. To hold/release a specific bundle, use: H SP-ST01T2-JES2--JESMSGLG or RLS SP-ST01T2-JES2--JESMSGLG To hold/release all bundles listed, enter: HOLD LIST or RELEASE LIST To hold/release selected bundles, use: Command ===> HOLD Opt Bundle S SP-ST01T2-JES2--JESMSGLG SP-ST01T2-JES2--JESJCL S SP-ST01T2-JES2--JESYSMSG JHS Operator s Guide R4.2 (March 2007) 29

30 O30: Output Processing (-O.OUT) or use: \ Command ===> RELEASE Opt Bundle S SP-ST01T2-JES2--JESMSGLG SP-ST01T2-JES2--JESJCL S SP-ST01T2-JES2--JESYSMSG Datasets in a bundle Screen O43: Reports for Bundle lists all reports that have been received for the bundle. Screen O43 can be selected by using RPT next to the bundle on the Bundle Status screen. J 1 O43: Reports for Bundle SP-ST01T2-JES2--JESMSGLG ROW 1 OF 3 Command ===> Scroll ===> PAGE Opened: 09/07/88 14:05 Pages: 15 Lines: 561 Status: Closure rules: Reports defined: 3 Received: 2 Indexed: 3 Distribution points: 1 Output modes: 1 Screen O43 also lists the information for the Bundle from the Bundle Status screens (O40:- O42:). Reports in output processing (-O.OUT.RPT) The output processor distributes SYSOUT to bundles and then to output work elements. The Report Status screens lists the reports that are currently being handled by the output processor and indicates their current status. After the output processor has completed its work for the SYSOUT, the datasets are no longer listed on these screens but can still be seen in the data base. Selecting Report Status Accessing Report Status Screens Switching Screens Report Status Screens The Report Status screen can be selected by using RPT on the Output Processing screen or -O.OUT.RPT from any screen. Report Status screens (O35-O37) can be accessed by entering RPT on O30: Output Processing screen Once a Report Status screen is displayed, the other Report Status screens can be accessed by scrolling RIGHT or LEFT. The following figures are sample illustrations of Report Status screens. 30 Systemware, Inc.

31 Chapter 2 JHS Console Procedures 2 JHS console procedures J 1 O35: Report Status ROW 1 OF 2 Command ===> Scroll ===> PAGE Commands: HOLD - Suspend RELEASE - Remove suspend U - Update Options: S - Select for command B - Browse H - Hold RLS - Release Scroll RIGHT for more information. Use HELP for additional commands. H -Waiting For- Last Opt Report Ver R BND OWE JOB Command SP-ST01T2-JES2-JESMSGLG SP-ST01T2-JES2-JESJCL Scrolling RIGHT produces: J 1 O36: Report Status ROW 1 OF 2 Command ===> Scroll ===> PAGE Commands: HOLD - Suspend RELEASE - Remove suspend U - Update Options: S - Select for command B - Browse H - Hold RLS - Release Scroll RIGHT for more information. Use HELP for additional commands. Scroll LEFT or RIGHT for more information H Last Opt Report R Job Received Pages Lines Command 5MPSI-JES2-JESMSGLG ST05MPSI 09/18/95 14: T05MPSI-JES2-JESJCL ST05MPSI 09/18/95 14: ***************************** BOTTOM OF DATA ****************************** Scrolling RIGHT again produces: J 1 O37: Report Status ROW 1 OF 2 Command ===> Scroll ===> PAGE Commands: HOLD - Suspend RELEASE - Remove suspend U - Update Options: S - Select for command B - Browse H - Hold RLS - Release Scroll RIGHT for more information. Use HELP for additional commands. Scroll LEFT for more information For demand print only: Opt Report Source User name 5MPSI-JES2-JESMSGLG T05MPSI-JES2-JESJCL ************************* BOTTOM OF DATA **************************** JHS Operator s Guide R4.2 (March 2007) 31

32 O30: Output Processing (-O.OUT) The Report Status display, screens O35 - O37, contain the following columns. The columns displayed can be selected by scrolling RIGHT and LEFT: Last Command Report Ver H R Waiting for Bundles All Bundles Close OWEs All OWEs Done Jobs All Jobs Done Job Received Pages The last command issued against this report; this column contains ERROR if the command was not successfully completed. The column is cleared when the display is refreshed. Name of dataset; the full 40 character name is displayed on screen O35. A shortened name consisting of the last 20 characters is displayed on other screens. Report version. Hold reason. If non-blank, then the dataset is held in destribution. The codes appearing are: J held due to an error in the job O held by operation HOLD command Lists the elements of distribution that have not yet complete. The counters show the number of items for each element that are awaiting completion. The elements are: BND number of bundles waiting to close OWE number of output work elements waiting to process JOB number of driver-submitted jobs awaiting completion Number of bundles defined that contain this dataset. Number of bundles containing this dataset that have been closed; when a bundle is closed, it is converted to OWEs and can no longer be displayed as a bundle in output processing. Number of output work elements created from closed bundles. Number of output work elements that have been entirely sent to output devices. Number of driver jobs submitted from OWE processing. Number of driver submitted jobs that have completed. Name of the job that created the dataset. Date and time the system received the dataset. Number of pages in the dataset. If the number is followed by K, the value is in the thousands; if the number is followed by M, the value is in the millions. Lines Number of records (lines) in the dataset. If the number is followed by K, the value is in the thousands; if the number is followed by M, the value is in the millions. Source User Name The source name (TSO user id, security system identifier, VTAM terminal name, etc.) of the demand print request for this dataset. The user name of the demand print request for this dataset. Scrolling the datasets in output processing displays The Report Status screens are lists that can be scrolled using the standard UP and DOWN keys. Additional columns are available by scrolling LEFT or RIGHT. 32 Systemware, Inc.

33 Chapter 2 JHS Console Procedures 2 JHS console procedures FIND command The Find command can be used to select a specific piece of information anywhere on the list. The columns used are based on an internal table that can have data in slightly different columns than on the displays. FINDALL command The FINDALL command enables an end user to browse a dataset and eliminate all but those lines of interest from the display of the dataset with a single search operation. The resulting display includes the line containing the character string and optionally a user specified number of lines on the same page before and after the line containing the character string. The FINDALL command returns all occurrences of a search string in the section of the dataset currently being browsed. The display may include only a single page or lines from several pages, depending on the context. The full syntax for the FINDALL command is: FINDALL FA [searchstring] [P L] [startcol endcol] [-prior] [ +following] where FINDALL can be abbreviated as FA. Issuing FINDALL without any parameters resets the display to the browse piece in effect before the previous FINDALL was issued. Each FINDALL command resets the previous FINDALL condition. Only a single FINDALL can be in effect at any one time. searchstring is the character string to be searched for in the dataset (optional). P L indicates whether full pages or single lines are returned in the new browse section (default is LINE). Using P causes the entire page containing the search string to be displayed (optional). -prior is a number from 1 to 999 indicating the number of lines to be displayed preceding each line containing the string (optional). +following is a number from 1 to 999 indicating the number of lines to be displayed following each line containing the string (optional). The additional lines are must be on the same page as the designated string. Header lines defined in the report definition (but not view definition) are also included startcol and endcol parameters specify a range of columns to limit the search (optional). Examples: Display all lines containing PATTERN 017: FA 'PATTERN 017' L Display all lines containing PATTERN 017 between columns 10 and 35 including 1 line before and 2 lines after. FA 'PATTERN 017' L JHS Operator s Guide R4.2 (March 2007) 33

34 O30: Output Processing (-O.OUT) Display all pages that contain the string ACCT 0431: FA ACCT 0431 P Browsing a dataset To browse (view at the terminal) a dataset, use: Opt Report B SP-ST01T2-JES2--JESMSGLG Output work elements in output processing (O.OUT.OWE) The output processor distributes SYSOUT to bundles and then to output work elements. The OWE Status screens (O45:-O47) list the OWEs that are currently being handled by the output processor and indicates their current status. After the output processor has processed the OWEs, the distribution processing is complete and the OWEs are deleted. The OWE Status screens can be accessed by selecting OWE on the O30: Output Processing screen or entering -O.OUT.OWE in the Command ===> line of any screen. J 1 O30: Output Processing Command ===> owe Select Command from list below. Place any character next to command or enter command in Command ===> area. - Cmd Description BND - List open bundles matching bundle and report name masks RPT - List reports matching report and bundle name masks OWE - List output ready for output drivers matching all masks DVR - List output drivers matching driver name mask JOB - List submitted jobs outstanding Selection criteria: Bundle name mask ==> Report name mask ==> Driver name mask ==> Demand print only ==> NO (yes/no) Source and User apply to RPT with Demand Print, and apply to all OWE. Source name mask ==> User name mask ==> 34 Systemware, Inc.