CHAPTER 2

IBM S/390 2003/135 VM OPERATION

System Overview

The system hardware console is a PC running in a Windows environment which is located to the right of the tape drive. This is the console we will normally be using to ipl, or power up or down the hardware. This console is referred to as the Hardware Management Console (HMC) and will be called the HMC from this point forward.

The HMC user interface is designed to provide the functions you need through an object (icon) oriented design. By manipulating objects with the mouse we can manipulate the objects that are defined to the HMC and be aware of changes to the hardware status as they are detected.

The HMC communicates with each central processor complex (CPC) through the CPC’s support element (SE). When tasks are performed at the HMC, the commands are sent to one or more support elements, which then issue commands to their CPC. The tasks to be performed will be initiated with a mouse action.

Overview of Mouse Terms

The mouse action performed most frequently will be to drag an object with the right mouse button and drop the object on another object. An example will be to IPL, drag the IBMSSE object with the right mouse button and drop the object on the ACTIVATE task.

Icon A graphical representation of an object, consisting of an image, image background and a label.

 

To point with the mouse

Move the mouse until the mouse pointer rests on the desired spot.

 

To click the mouse button

Press and release the button once.

 

To double-click the mouse button

Click the button twice in quick succession.

 

To select an object

Click on an object’s icon with the left mouse button to select it for further action.

To swipe Press and hold down the left mouse button on the first object to be selected. Without releasing the left button, move the mouse’s pointer over the other objects to be selected.

 

To display a view

Double-click on a Views icon with the left mouse button to display the objects contained in the view. The objects will be displayed in the work area.

 

To open an object

Double-click on an object’s icon with the left mouse button to display another level of detailed information about the object.

 

To drag an object

Place the mouse pointer on the object’s icon. Press and hold down the right mouse button. Then, move the mouse (and the icon) to another location.

 

To drag several objects

After selecting several objects, place the mouse pointer on one of the selected object’s icon. Press and hold down the right mouse button. Then, move the mouse (and the icon) to another location.

 

To drop an object

Release the right mouse button to drop the dragged object in the new location.

 

Box selection

Place the mouse pointer above and to the left of the leftmost, top object to be selected. Move the mouse pointer down and to the right with the left mouse button held down.

 

Overview of HMC Workplace (Screen Display)

The HMC workplace panel consists of three areas: a Views area, a Tasks area and a Work area.

The Views area, in the upper left portion of the panel, contains icons that represent different collections or views of the objects that make up the processor complex.

The background color of this area also gives an indication of the status of the processor cluster.

 

The Tasks area, in the right portion of the panel, contains icons that represent the operations that you can perform on the objects.

 

The Work area, in the lower left portion of the panel, is the area of the panel that displays the objects of the processor cluster. Initially, the objects of the Groups view are displayed in the Groups Work area. The icon IBMSSE is the object for our system that we will be dragging to initiate tasks such as IPL, shutdown (deactivate task), power on (activate task).

Monitoring the Hardware

Good or acceptable status for all CPCs and CPC images in the processor cluster is indicated by a green background in the Views area of the HMC workplace panel, and by the absence of a red background around the Exceptions icon. Status changes from acceptable to unacceptable, referred to as Exceptions are indicated by a color change from green to red. Red indicates an exception, or that an object has an unacceptable status.

Messages that may require operator attention are indicated by the blue flashing Hardware Messages icon or by the cyan flashing Operating System Messages in the Tasks area under the Daily menu. In addition, to indicate which objects have hardware or operating system messages that require operator attention, the CPC or CPC image icon’s background color and its group icon background color will also be blue or cyan.

If an exception situation exists, open the Exceptions group from the Views area to see a subset of only those CPCs or images involved in an exception condition. Once you have displayed the Exceptions view, the background of the entire Views area changes back to green, and a red background only remains around the Exception icon, the object icon, and the group icon with the unacceptable status.

 

 

IBM S/390 2003/135 POWER PROCEDURES

IBM S/390 2003/135 POWER ON IPL PROCEDURES

  1. Double click on the GROUPS icon in the Views Area on the HMC. The Group’s work area will now be displayed in the Work area windows.
  2. Double click on the DEFINED CPC’s icon. You should now see the IBMSSE icon.
  3. Drag the IBMSSE icon over to and drop on the ACTIVATE icon in the Task area. If by some chance that task window does not have DAILY as the heading on the window, scroll with the circular arrow keys located in bottom right corner of the screen until you come to a menu heading of DAILY. The task ACTIVATE appears on this menu.
  4. An Activate Task Confirmation window will appear. Click the left mouse button on YES after reviewing the information on the confirmation window to verify the object you will activate is the CPC, and the activation profile is the one you want.
  5. An Activate Progress window will appear displaying the progress of the activation, and the outcome. Select OK to close the window when the activation completes successfully.
  6. Click OK with left mouse button.
  7. The VM IPL procedure will then continue from a VM window automatically displayed on the HMC console. The following messages are displayed on the VM window.

VM/ENTERPRISE SYSTEMS ARCHITECTURE SYSTEM PRODUCT

RELEASE 2 SERVICE LEVEL 0000;

SYSTEM NUCLEUS CREATED ON mm/dd/yy AT hh:mm:ss,

LOADED FROM ESARES

 

************************************************************

LICENSED MATERIALS – PROPERTY OF IBM

 

5684-112 © COPYRIGHT IBM CORP. 1983,

1992. ALL RIGHTS RESERVED

US GOVERNMENT USERS RESTRICTED RIGHTS -

USE, DUPLICATION OR DISCLOSURE

RESTRICTED BY GSA ADP SCHEDULE CONTRACT

WITH IBM CORP.

 

TRADEMARK OF INTERNATIONAL BUSINESS

MACHINES

***********************************************************

 

START ((WARM/FORCE/COLD)) (DRAIN) (DISABLE)

<NODIRECT> <NOAUTOLOG> OR <SHUTDOWN>

 

  1. Select the type of start to be performed. Normally a WARM start is done. A warm start recovers accounting data and retains the spooled output files. Type:

 

WARM

 

  1. The following messages will appear.
  2.  

    THE DIRECTORY ON VOLUME ESARES AT ADDRESS 0EB0

    HAS BEEN BROUGHT ONLINE

    HCPWRS2513I SPOOL FILES AVAILABLE nnnnn

    HCPWRS2512I SPOOLING INITIALIZATION IS COMPLETE.

     

  3. During this time the system is preallocating spool space for a system dump in case of a crash. Approximately 2 minutes will elapse and the following message is then displayed.
  4. DASD 0F52 DUMP UNIT CP IPL PAGES 0000

     

    Make sure a disk device is displayed for a dump and not a printer, or the entire dump will print on the printer before you can do another IPL if the system crashes. If a printer was selected as the dump device, you can change it to a disk device by typing:

     

    SET DUMP DASD

     

    If there is no space available on a dasd device, change the dump device to a tape drive, type:

     

    SET DUMP 79n

     

    Where n = 0, 1, 2, 3, 8, 9, A or B

     

    You can then check on what device the dump will select, by typing:

     

    Q DUMP

     

  5. After about 3 screens of info, a message to press ENTER or CLEAR will appear. Press ENTER and Operator will automatically be logged on. The number of spool files and the current logmsg will be displayed.
  6. Several virtual machines will automatically be logged on such as RECOVERY, VMSECURE, VMACCT, VMSCHED, VMTAPE etc.
  7. Update the status phone.

 

 

 

IBM S/390 2003/135 POWER OFF PROCEDURES

Note: Make sure to have followed the SHUTDOWN procedures for UBMVS, UBRF2, UBRF3 and VM before performing any of the following functions.

  1. Double click on the GROUPS icon in the Views Area on the HMC. The Group’s work area will now be displayed in the Work area windows.
  2. Double click on the DEFINED CPC’s icon. You should now see the IBMSSE icon.
  3. Drag the IBMSSE icon over to and drop on the DEACTIVATE icon in the Task area. If by some chance that task window does not have DAILY as the heading on the window, scroll with the circular arrow keys located in bottom right corner of the screen until you come to a menu heading of DAILY. The task DEACTIVATE appears on this menu.
  4. A Delete Confirmation window will appear. Click the left mouse button on YES if you really want to power down the system.
  5. A Deactivate Progress window will appear giving the approximate completion time. When complete the IBMSSE completed message will appear.
  6. Click OK with left mouse button.

 

 

IBM S/390 VM SHUTDOWN PROCEDURES

    1. Send out a warning to users. Allow users 5 minutes to log off if at all possible.
    2.  

      WARN ALL SYSTEM GOING DOWN IN 5 MIN., BACK AT uptime.

       

      Where uptime = time system is expected to be fully operational again

       

    3. Shutdown UBMVS, UBRF, UBRF2 and UBRF3. Follow the appropriate shutdown procedures for each system before continuing with the VM shutdown.
    4. At the scheduled shutdown time, send a message to users to log off immediately. Type:
    5.  

      WARN ALL SYSTEM DOWN, LOG OFF IMMEDIATELY

       

    6. To begin the shutdown procedure, execute the EXEC named "SHUTDOWN". Type:
    7.  

      SHUTDOWN

       

    8. The following messages will appear:
    9.  

      You are attempting to Shutdown the IBM !!!

       

      This procedure will first shutdown the SOFTWARE products,

      Then it will shutdown the 2003, UBVM, UBMVS and UBRF.

       

      *** NOTE UBMVS and UBRF should be shutdown before UB***

       

      DO YOU WANT TO SHUTDOWN THE IBM 2003? (YES OR NO)

      VMYEXE018R REPLY nn TO READ ISSUED BY SHUTDOWN.

       

    10. Type:
    11.  

      R nn YES

       

    12. The following messages will appear:
    13.  

      REPLY WAS YES . . . . SHUTDOWN OF PROGRAM PRODUCTS AND

      CPU IN PROGRESS . . .

      CPU SHUTDOWN OF xxxx . . .

      COMMENCED . . .

      SHUTDOWN OF PROGRAM RODUCTS IN PROGRESS . . .

      VMTST368I STAM SHUTDOWN COMPLETE

      VMYMPPI147E SERVICE VIRTUAL MACHINE VMTAPE NOT

      AVAILABLE

      VMTEND002I VMTAPE SYSTEM SHUTDOWN COMPLETE ON mm/dd/yy

      VMDEND029I VMSCHED SYSTEM END COMPLETE ON mm/dd/yy

      VMXEND029I VMSECURE SYSTEM TERMINATION COMPLETE ON mm/dd/yy

       

      The shutdown procedure should take about 1-2 minutes to complete from the time you enter the reply to the shutdown procedure until the alarm sounds.

       

    14. The following message will appear on the VM console.
    15.  

      SYSTEM SHUTDOWN COMPLETE

       

      CRITICAL INFORMATION

       

      It is important that you wait to see the SYSTEM SHUTDOWN COMPLETE message. If you do not see this message, you will not be able to do a WARM start when you IPL, but will probably then need to attempt a FORCE start.

       

    16. If powering down the sytem completely (for example, air-conditioning maintenance is scheduled), continue with the IBM S390 POWER OFF PROCEDURES.

 

IBM S/390 VM SYSTEM REPORTING PROCEDURES

GENERAL POLICY OVERVIEW

In order to isolate and correct software and/or hardware problems, the following general policy is to be strictly adhered to along with the extra steps necessary dependent on the type of malfunction (hard crash, crash with auto-IPL, loop or wait state). Make sure to perform the specific steps outlined in the next section titled VM CRASH/RECOVERY Procedures.

 

    1. Update the status phone and describe the problem as completely as possible by logging a report using REMEDY. The more information you can provide, the easier it will be to find the cause and solve the problem.
    2.  

    3. Notify a system’s analyst of the problem, any time day, night or weekends. Phone numbers are located in section ACADEMIC SYSTEMS PERSONNEL in chapter 1 of this book.
    4.  

    5. If unable to contact one of the above, you should attempt to IPL with a WARM start which, if successful, will recover accounting data and previously closed spool output files. If this fails, leave system as is and continue trying to make contact with one of the above for thirty (30) minutes. Once contact is made with any one of the above, it is that person’s responsibility to contact another analyst if he/she is unable to handle the problem or situation. It is also the analyst’s responsibility to keep the originator of the call properly informed as to course of action being taken or planned. As a general rule of thumb, this should be done within 15 minute intervals.
    6.  

    7. After attempting a WARM start and after having failed to make contact with an analyst in 30 minutes, attempt to IPL the system in the following order:

 

FORCE - operates like a recovery attempt to save as many spool files as possible. Any spool file that has unreadable or invalid data is dropped from the system.

 

COLD - all closed spool files and accounting records are lost.

 

Recap: Try a WARM start initially (see step 3). If that should fail, try a FORCE start. If that should also fail, try reaching a system’s analyst again before proceeding to the next start. If still unable to reach a system’s analyst, then do the COLD start. If you cannot do a cold start, call for IBM Service.

 

NOTE: We do not want to do any more COLD starts than necessary because of losing all of the spool files.

 

    1. If a COLD start was done, enter into the LOGMSG that a COLD start was done on mm/dd/yy at hh:mm:ss and all spool files were lost. Any other messages which were in the LOGMSG must be re-entered since the LOGMSG file was also lost.
    2.  

    3. Be sure to have REMEDY filled in completely as to the type of starts done, phone calls made etc.
    4.  

    5. Update the status phone.

 

VM CRASH/RECOVERY PROCEDURES

Following are the steps to be taken when the IBM crashes or enters a "wait state" or loop. Also, all actions, error messages, and PSW’s should be recorded in REMEDY.

 

    1. Hard Crash

Symptoms:

Actions:

 

    1. Crash with Auto-re-IPL

Symptoms:

Actions:

 

    1. Loop or Wait State

Symptoms:

Actions:

 

NOTE

 

IPL’s – always WARM start, if fails, do FORCE, if force fails, double check IPL address, COLD as last resort.

 

 

SUMMARY OF DISCONNECTED SERVICE VIRTUAL MACHINES

Following is a list of the Disconnected Service Virtual Machines currently supported by the University of Buffalo Systems Group. These machines show up in the QUERY NAMES display as running DISC, except for VSM, which is shown running VTAM and TCPIP. Also, these machines should be logged on during IBM Production hours. During System testing, any, or all of these machines may be brought down.

 

Example of QUERY NAMES display:

 

q n

 

XSTORAGE

- DSC ,

VMTAPE

- DSC ,

EREP

- DSC ,

ELENA

- DSC

NATHAN

- DSC ,

IO116

- 0305,

SMTP

- DSC ,

UBRF3

- DSC

NETVIEW

- DSC ,

UBMVS

- DSC ,

AUDITOR

- DSC ,

MVSPRTR2

- DSC

MVSPRTR1

- DSC ,

MVSPRTR

- DSC ,

MVSPRT2

- DSC ,

MVSPRT1

- DSC

MVSPRT

- DSC ,

PRTMONV2

- DSC ,

PRTMONV1

- DSC ,

PRTMONV

- DSC

PRTMONE

- DSC ,

PRTMONU2

- DSC ,

PRTMONU1

- DSC ,

PRTMONU

- DSC

PRTMON2

- DSC ,

PRTMON1

- DSC ,

PRTMON

- DSC ,

NVAS

- DSC

RSCS

- DSC ,

RSCSP

- DSC ,

VTAM

- DSC ,

TESTPRT

- DSC

MVSPRTRT

- DSC ,

MVSPRTT

- DSC ,

PRTMONET

- DSC ,

PRTMONUT

- DSC

PRTMONVT

- DSC ,

PRTMONT

- DSC ,

PRTCNTL

- DSC ,

PROPCOM

- DSC

MAILFWD

- DSC ,

MAILERL

- DSC ,

MAILERT

- DSC ,

MAILER

- DSC

ISPVM

- DSC ,

VMACCT

- DSC ,

VMARCH

- DSC ,

RESTORE

- DSC

VMBACKUP

- DSC ,

VMSCHED

- DSC ,

RECOVERY

- DSC ,

FINGERD

- DSC

HTTPD

- DSC ,

MSGD

- DSC ,

GOPHER

- DSC ,

POP

- DSC

VMNFS

- DSC ,

PORTMAP

- DSC ,

NAMESRV

- DSC ,

LPSERVE3

- DSC

LPSERVE2

- DSC ,

LPSERVE

- DSC ,

FTPSERV3

- DSC ,

FTPSERV2

- DSC

FTPSERVE

- DSC ,

SNMPD

- DSC ,

SNMPQE

- DSC ,

VCOLLECT

- DSC

SMART

- DSC ,

PRIVOP2

- DSC ,

PRIVOPT

- DSC ,

TCPIP

- DSC

STKSRP

- DSC ,

VMX$0002

- DSC ,

UBRF2

- DSC ,

UBRF

- DSC

FACSTAFF

- DSC ,

VMSERVU

- DSC ,

VMSERVS

- DSC ,

VMX$0001

- DSC

VMSERVR

- DSC ,

VMSECURE

- DSC ,

OPCON

- DSC ,

PRIVOP

- DSC

SYSSYMP

- DSC ,

VMJRTRVR

- DSC ,

OPERATOR

- DSC ,

 

- DSC

VSM

- TCPIP

           

VSM

- VTAM

         

OPNJUDY

- TERMAX01

         

 

Note that any user may put himself into a "disconnected state". The advantage to the user in doing this is that a terminal need not be "occupied" in order to do work on the machine. This frees up the terminal for others.

 

Following are the userids that are doing work FOR the users. The column marked Support Group designates who maintains that product. If TEST appears, in this column, Operations need not be concerned with that machine. Machines with "N.A." in this column are controlled by another disconnected machine. Operations need not concern themselves with the machines marked "N.A." except to know what their functions are.

USERID

FUNCTION

SUPPORT GROUP

UBMVS

MVS – The Administrative Operating System

Systems

UBMVS1

MVS Test System

TEST

UBMVS2

MVS Test System

TEST

VMLEVEL2

VM Test System

TEST

OPERATOR

This account is the Operator’s Tool. It is logged onto port 00E0. This account is used for starting dumps, EREP, dumping spool, shutdown the system, secondary tape operator, etc. It is running VMOPERATOR from Systems Center.

Systems

OPCON

Running Programmable Operator (PROP). It runs Dumps, Erep and Monitors system activity.

Systems

VMSECURE

VM System security and Disk Management

Systems

VMX$0001

VMSECURE servant facility

Systems

VMX$0002

VMSECURE servant facility

Systems

VMARCH

Archival Subsystem

Systems

VMBACKUP

Permanent file backup and restore

Systems

VMTAPE

Tape Management Subsystem. Request for tape mounts are processed by VMTAPE.

Systems

VMSCHED

Utility for automatic submission of system or user jobs. This id ensures that PRTMON is running.

Systems

PRTCNTL

Part of PRTMON. Transfers files from virtual readers to PRTMON, PRTMON1, and PRTMON2.

Systems

PRTMON

Appends header/trailer pages for small UBVM print

Systems

PRTMON1

Appends header/trailer pages for medium UBVM print

Systems

PRTMON2

Appends header/trailer pages for large UBVM print

Systems

PRTMONV

Appends header/trailer pages for small XPRINT jobs

Systems

PRTMONV1

Appends header/trailer pages for medium XPRINT jobs

Systems

PRTMONV2

Appends header/trailer pages for large XPRINT jobs

Systems

PRTMONU

Unix output

Systems

PRTMONU1

Unix output

Systems

PRTMONU2

Unix output

Systems

PRTMONVT

Test printing from the VAX

TEST

VCOLLECT

System Monitor

Systems

SMART

Real Time System performance monitor

Systems

ISPVM

Necessary for using ISPF/PDF

Systems

MAILER

The electronic mail system

Systems

SMTP

TCPIP mailer machine

Systems

FTPSERVE

FTP Server

Systems

FTPSERV2

FTP Server

Systems

FTPSERV3

FTP Server

Systems

TCPIP

TCPIP primary Service virtual machine

Systems

NAMESRV

TCPIP name service machine

Systems

LPSERVE

TCPIP print service machine

Systems

LPSERVE2

TCPIP print service machine

Systems

LPSERVE3

TCPIP print service machine

Systems

VSM

This is not actually a Userid. This is only displayed when VTAM is running. Prior to VTAM’s complete initialization, this will NOT appear. It shows up as: VSM – VTAM in the display.

Systems

VSM

This is not actually a Userid. This is only displayed when TCPIP is RUNNING. Prior to TCPIP’s complete initialization, this will NOT appear.

Systems

VTAM

The VTAM service machine.

Systems

RECOVERY

The VTAM recovery machine. This must be running before VTAM. If RECOVERY is forced off, VTAM will ABEND.

Systems

RSCSP

Remote Spooling Communications Subsystem handles remote printers.

Systems

RSCS

Links to other computers.

Systems

VMACCT

Collects accounting data

Systems

MVSPRT

Controls printing of all small UBMVS print files

Systems

MVSPRT1

Controls printing of all medium UBMVS print files

Systems

MVSPRT2

Controls printing of all large UBMVS print files

Systems

PROPCOM

Communications PROP machine monitors communications

Systems

NETVIEW

Controls and monitors the network resources

Systems

XSTORAGE

Expanded Storage Monitor

Systems

EREP

Hardware Error Recording

Systems

NATHAN

LSOFT Visiting People – CO - OP

LSOFT

ELENA

LSOFT Visiting People – CO – OP

LSOFT

ERIC

LSOFT Visiting People – CO – OP

LSOFT

IO116

02e Print Operator’s Console

Operations

UBRF

Research Foundation Production

Research Foundation

UBRF2

Research Foundation Development

Research Foundation

UBRF3

Research Foundation Test

Research Foundation

AUDITOR

Monitor SVM

Systems

MVSPRTR

RF Print Processor (header/trailer pages)

Systems

MVSPRTR1

RF Print Processor (header/trailer pages)

Systems

MVSPRTR2

RF Print Processor (header/trailer pages)

Systems

PRTMONE

Entire (COMXPS) Printing to 4635 Banner Pages

Systems

NVAS

Netview Access Services – terminal session manager

Systems

TESTPRT

Test machine for printing

Systems

MVSPRTRT

Printing Test

Systems

MVSPRTTT

Printing Test

Systems

PRTMONET

Printing Test

Systems

PRTMONUT

Printing Test

Systems

PRTMONT

Printing Test

Systems

MAILFWD

Mail Forwarding

Systems

MAILERL

Mailer for LSOFT International

Systems

MAILERT

Mailer testing

Systems

RESTORE

VMBACKUP for Restores only

Systems

FINGERD

Finger Server

Systems

HTTPD

WWW Server

Systems

MSGD

Message Server

Systems

GOPHER

Gopher Server

Systems

POP

Pop Server

Systems

VMNFS

NFS Server

Systems

PORTMAP

TCPIP Port Mapper

Systems

SNMPD

SNMP Server

Systems

SNMPQE

SNMP Query Server

Systems

PRIVOP

Privilege Command Processor

Systems

PRIVOP2

Privilege Command Processor

Systems

PRIVOPT

Test Priv Command Processor

Systems

STKSRP

RVA2 Support (Disk)

Systems

FACSTAFF

SFS File Server

Systems

VMSERVU

SFS File Server

Systems

VMSERVS

SFS File Server

Systems

VMSERVR

SFS Recovery Server

Systems

VMJRTRVR

Accounting

Systems

 

 

EREP HARDWARE ERROR REPORTING PROCEDURES

EREP (ENVIRONMENTAL RECORDING, EDITING AND PRINTING PROGRAM) is the facility that collects any reported hardware errors that occur on any device, channel, or processor. This procedure is started automatically by VMSCHEDULE on UBVM and CA7 on UBMVS. This procedure is to be run every morning no later than 8:00 am, so that if problems are occurring, the most current report will be available. Also, this may be run on request by either IBM or anyone in the System’s group.

 

CURRENT SCHEDULE: Sunday – Saturday – 8:00 pm

 

Note: If VMSCHEDULE fails to start these jobs at the designated times, start them manually and be sure to fill out a REMEDY report.

 

The procedure that has been set up contains two steps. Step 1 will extract the error report off of UBVM and clear the recording area. Step 2 consists of starting an MVS job using CA7 to report any hardware errors MVS has recorded, and merge the two into one report. This report is printed and is to be placed in the IBM CE’s office. This report is also directed to four-cycle generation datasets. These reports can then be reprinted at anytime on a request only basis. To print the most recent EREP report, the operator should type:

 

S EREPPRT

 

on the MVS console.

 

If the operator wishes to print all four cycles of the EREP output, the operator should type:

 

S EREPALL

 

on the MVS console.

 

The printed output will print on the IBM 4245 printer located in room 116.

 

MANUAL PROCEDURE: (if VMSCHEDULE fails to start runs)

 

    1. From the UBVM operator’s console, execute the procedure called EREPCLR. Type:
    2. The following messages will appear on the UBVM console. This process will take less than 5 minutes.

***** STARTING ACTION ROUTINE EREPCLR ON VM/XA *****

IBMCE AUTOLOGGED TO RUN EREP.

HCPCLS6056I XAUTOLOG INFORMATION FOR IBMCE. THE IPL

COMMAND IS VERIFIED BY THE IPL COMMAND PROCESSOR.

***** EREPCLR COMPLETED. *****

0 RECORDING FILE(S), 0 RECORDS, A DISK nn% FULL

RECORDING DATA RETRIEVAL STARTED, RECORDS EREP EREP

 

    1. At the CA7 console (normally the 3290), demand start the EREP job. This is a separate EREP run which will not start any of the other normal nighttime processing runs. Type:
    2. DEMAND,JOB=EREP2

    3. The following messages will appear:
    4. $HASP373 EREP STARTED – INIT n – CLASS O – SYS IP01

      IEF403I EREP – STARTED – TIME=hh:mm:ss

       

    5. The job will request a cartridge as input first. The following messages will appear:
    6. IEF233A M99n,nnnnnn,,EREP,HIST,TKSSYS.EREP.HISTORY.GnnnnV00

      Messages requiring a response or other operator action appear in white.

    7. Mount the requested cartridge.
    8. The following messages will appear.
    9. IECTMS9 99x,nnnn,EREP ,ACCDEC ,99000,001,.HISTORY.GnnnnV00

      IEC502E K 99n,nnnnn,SL,EREP,TRENDS,TKSSYS.EREP.HISTORY.GnnnnV00

      IEC501A M 99n,nnnnnn,SL,NOCOMP,EREP,TRENDS,TKSSYS.EREP.HISTORY.GnnnnV00

      IEF234E K 99n,nnnn,PVT,EREP,TRENDS

      IEF417E FOLLOWING VOLUMES NO LONGER NEEDED BY EREP nnnnnn

      $HASP395 EREP ENDED

      $HASP350 EREP ON L7.ST1 nnn RECORDS

      $HASP250 EREP IS PURGED

       

    10. Put the cartridges away.