Scribd
Upload
20 views7 pages

Sunday 4PM To 1230AM Mainframe Operations Schedule - Revised

Uploaded by

saddamshaikframe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
20 views7 pages

Sunday 4PM To 1230AM Mainframe Operations Schedule - Revised

Uploaded by

saddamshaikframe
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Sunday 4PM – 12AM

16:00 –

o Check clipboard for Schedules, Tech Change Sheets and Requests. Review
Turnover Log.

19:30 –
Run the CA7 Backups, after UCJW0001 is released and in TSO on hold.
o IN TSO1/SDSF enter pre ucjw0001;i This will display the job. Look to the
right side of the display under ‘Status’ it should say HOLD. Then proceed to
the next step
o Shut down CA7
o You must be logged into CA7 with ca7con/master to shutdown
CA7
o In CA7 type “/shutdown,z3”. Verify that CA7 is down by checking
TSO1; CA7ONL should not be displayed in the active jobs.
o Once CA7ONL has ended, type “i” into TSO1. This will bring up the
input queue. Scroll to the job UCJW0001 and place an “a” next to it
and press CTRL. This will run the CA7 backups. Once completed
check for error codes.

When UCJW0001 completes successfully, restart CA7


o IN SDSF on TSO1, enter pre ucjw0001;st
Check to ensure job completed successfully
o At the TS01 command line type “/s imsrdr,mbr=ca7warm” and press
CTRL. This can also be done from the MVS1 console by using the
same command, just omit the “/”.
o Ensure that CA7 is active by viewing CA7ONL from the TSO1 session.
o After the “restart complete message” scrolls across the MVS1
monitor a CA7 session can be re-established from a workstation.

21:00 – The following WTOR will appear on the IPO1 console


@========> *** OPS ***
@========> YOU NEED TO ISSUE THE FOLLOWING COMMAND TO
@========> SHUTDOWN ONDEMAND BEFORE THIS JOB CAN RUN.
@========> P ARSSOCKD
@========> ONCE DOWN RESPOND TO THIS MESSAGE.
@xx REPLY C TO CANCEL MESSAGE
At the MVS console for IPO1 in the command input field enter
p arssockd and press CTRL or from your desktop
enter /p arssockd. Then reply to the message with xx,c xx=reply
number. To verify that ARSSOCKD is down, in SDSF on IPO1,
enter ‘da’, making sure ARSSOCKD is no longer displayed
21:00 - Shut down CICS and IDMS on IPO2.
IMPORTANT: CICS must be brought down before IDMS
o At the MVS console for IPO2 in the command input field enter
“s cicsshut” and press CTRL. This will shut down all of the IPO2 CICS
regions and should take around 5 minutes.
o In SDSF, enter pre cics*;da. This will display all CICS regions that are
running
After Confirming all the CICS regions are down shut down the IPO2
IDMS
Shut down IDMS regions
o V3 -IDMSTEST
o V4 - IDMSPREV
o V16 - IDMSPRDC
To do this go IPO2 MVS console in the command input field:
o type “d r,l “ and press CTRL or from your desktop in
TSO2/SDSF enter “sr” this will display system requests
o Note the reply numbers for the regions.
o Type the reply number and shutdown for each region. EXAMPLE:
32,shutdown. Then press control.
o There will be 3 WTORs that need replied.
o @xx ENTER CV NUMBER (03) TO CONFIRM SHUTDOWN OF
IDMSTEST - xx,03  Reply
o @xx ENTER CV NUMBER (04) TO CONFIRM SHUTDOWN OF
IDMSPREV – xx,04  Reply
o @xx ENTER CV NUMBER (16) TO CONFIRM SHUTDOWN OF
IDMSPRDC – xx,16  Reply
o All 3 regions can be done consecutively.

o Once the CICS and IDMS regions are down on IPO2:


o Release TRG21IP2 in CA7
This will start up the IDMS regions
o Once the IDMS regions are up,
IDMSPRDC V16
IDMSPREV V4
IDMSTEST V3 –
Release CICST100
o Once CICSD500 is up release CICST1CN
o To verify that CICSD500 is up, go into SDSF on IPO2
Enter s;pre CICSD500, then enter da
Tab down and put an S next to CICSD500
On the command line enter -- f given
You should see CICSD500 CONTROL IS BEING GIVEN TO
CICS. This tells you that CICSD500 is up. If you don’t see the
above message, continue entering f given until you see the
message
22:00 –
Verify that all IP02 IDMS & CICS regions are up.

o Check print dates:


o Check the IPO1 MVS Consoles for a WTR message to check print dates
o Reply to WTR message with the displayed number and “C”, Ex: 32c
o In TSO1 type the command “ h prt* “.
o Tab down to the last listing of ‘ prtdates’ and type an ‘s’ next to it and
press enter.
o Verify that the date is the current one.
o Type an ‘m’ and hit the ‘F8’ key, then hit F’7’ once. This will show the
current date. If the date is not current contact the MVS support group.

00:00 –
Shut down CICS regions on IPO1
IMPORTANT: CICS must be brought down before IDMS
o From the MVS Master Console type “s shutcics”, or from your desktop
enter /s shutcics… this will bring down regions:
 CICSP500
 CICSP400
 CICSP300
 CICSP0IT
 CICSP200
 CICSP100
o Confirm all CICS regions are down before continuing!

o Verify CICS Regions are down, then enter “S DB2DOWN” and press
CTRL. This will shut down:
o DSN1MSTR
o DSN1DBM1
o DSN1DIST
o DSN1SPAS
o WTOR on IPO1
o @---> NOTICE ****** NOTICE
o @---> THIS WILL BRING DOWN DB2 AND DSN1ADMT!!!!!
o @---> ARE YOU SURE YOU WANT TO DO THIS?
o @---> PLEASE SHUTDOWN ARSSOCKD PRIOR TO REPLYING
o @---> TO THIS MESSAGE !!!!!
o @---> REPLY C TO CONTINUE OR
o @---> CANCEL THIS PROCEDURE BY ISSUING (C DB2DOWN)
o Reply C to Continue
o Confirm that all the DSN’s are down by displaying all active jobs in the
TSO1 sessions (use the command “DA”) and make sure that the DSN’s
listed above are longer displayed.
o Confirm all previous steps are complete before continuing!

Shutdown IDMSPROD V1
o From the MVS Master Console type “ d r,l” to view reply number or
from your desktop in TSO1/SDSF enter “sr” this will display system
requests
o IDMSPROD @xx REPLY TO @@@$$$>>>>> IDMSPROD <<<<<$$
$@@@: xx= reply number
o Type the reply number and shutdown on the console.
 Example: 24shutdown
 There will be 1 WTOR that needs replied
o @xx ENTER CV NUMBER (01) TO CONFIRM SHUTDOWN OF
IDMSPROD
o Enter xx,01

o After the command is entered continue to monitor the main console for
IDJI0103 jobs. Once they have ended successfully confirm that
IDMSPROD is no longer displayed in the active jobs view of the TSO
session. (Use the command “DA”). Once IDMSPROD is down continue to
the next step.

IPO1 defrags (ISWDFWKY): MUST BE RUN PRIOR TO SPLITS


o As a requirement of the backups and whenever there is no batch running,
CICSP100 – CICP500 must be down before defrags (ISWDFWKY) are
run. Release this job
o Check IOP1 to make sure only 8000 & 9000 jobs are running
o ISWDFWKY should be in CA7 with a usr requirement
o USR=CICSPROD MUST BE DOWN. DEFRAGS MUST
o SCHID=000
o USR=RUN STAND ALONE - RELEASE AFTER
o SCHID=000
o USR=BATCH IS COMPLETED.

Note: all previous steps must be completed before running the splits.

00:10 –
o Release BUDTRIG1 in CA7 after IDMS & CICS regions are down on
IPO1 & the IPO1 defrags completed successfully. (You will be able to log
on to TSO1 and/or TSO2)
o This will trigger BUDDBS2D on IPO2
o BUDDBS2D triggers BUDCA7RD on IPO1
o Verify that BUDDBS2D & BUDCA7RD have completed
before moving to the next step
o Release BUDSTART in CA7
o This will trigger three jobs” Jobs BUDSNPCR, BUDSNPLK, and
BUDSPQRB which will run on IPO2/TSO2 consecutively.
o NOTE: These jobs output to IPO1.
o After these jobs have completed check the output for condition codes
o From the IPO1/TSO1 session in the command input field type
“pre buds*;o”
o These run on IPO2
o Then place an “S” next to each job output and press CTRL, the first
output will display, press F3 to scroll thru each output. With a clean
run of each job continue to the next step.

00:15 –
o Successful completion of BUDSPQRB will trigger BUDTAPON.
This starts the backups and will kick off ISJW0047 (Submit time of 00:45)

o Look for WTOR ON IPO1:


@---> NOTICE ****** NOTICE
@---> THIS WILL BRING DOWN STARTED TASK EXBSTART
@---> WHICH CONNECTS CICS TO THE WEBMETHODS SERVER!
@---> PLEASE VERIFY EXBSTART IS COMPLETELY DOWN.
@14 REPLY C TO CANCEL MESSAGE
Reply C

o Look for WTOR on IPO2


WTOR on IPO2:
@========> DAILY BACKUPS ARE ABOUT TO START
@========> ******************************
@33 REPLY C TO CANCEL MESSAGE
REPLY C

ISJW0047 brings up IDMSPROD & CICSP0IT

o Around this time ISJDCHCK will run automatically – this issues a WTOR
message on the IPO1 console to check if CICSP0IT is up
@========> *** OPS ***
@========> CHECK TO SEE THAT CICSP0IT IS ACTIVE
@13 REPLY C TO CANCEL MESSAGE
Verify that CICSP0IT is up. In SDSF on IPO1, enter
Pre cicsp0it;da. Once it is verified that CICSP0IT is up, reply C to the
WTOR. xx,c

Before releasing ISCICSWK, verify that job TSJD0150 has completed


successfully. In SDSF on IPO1, enter Pre TSJD0150:st

00:20 – Send Shift handoff and Complete Ops Daily Turnover.


Name Change Date Made
Michael Earl Updated splits jobs to new job stream in 2/18/2019
Budstart step
Michael Earl Removed references to BUDQURY1 – 2/19/2019
job decommed 2/17/19
Michael Earl Updated BUDTAPON to reflect auto- 2/19/2019
release

You might also like