Phase 6: Initial program load of the COD system
This chapter describes how to initial program load (IPL) the Customized Offering Driver (COD) system to a point where z/OS system programmer can log on to Time Sharing Options/Extended (TSO/E) by using a local non-SNA 3270 console.
This chapter includes the following topics:
9.1 Goals
The Phase 6 goal is to IPL the COD z/OS driving system to a point where the z/OS system programmer can log on to TSO/E by using a local non-SNA 3270 console.
Phase 6 is required to achieve Milestone 2: Stand-alone Restore of COD and IPL. Where this milestone is positioned in the overall process is shown in Figure 9-1.
Figure 9-1 Phase 6 Milestone 2
9.2 Requirements
You often use the documents and resources that are described in this section while completing Phase 6 tasks.
9.2.1 Documentation
For more information, see the following documentation:
•Customized Offerings Driver Installation Guide for Program Number 5751-COD
•Your I/O configuration design that meets the COD requirements
9.2.2 Resources
Ensure that the following resources are available:
•z13 server that is installed by IBM Customer Engineer (CE) and is power-on reset (POR)
•COD logical partition (LPAR) activated
•Three direct data storages device (DASD) volumes on your storage subsystem with COD data restored
•User IDs and Passwords for the use of the Hardware Management Console (HMC) and SE with SYSPROG user profiles
•Two local non-SNA 3270 terminals
9.3 Related documents
The following IBM publications provide relevant information during Phase 6:
•IBM z13 Technical Guide, SG24-8251
•IBM z13s Technical Guide, SG24-8294
•IBM z13 Configuration Setup, SG24-8260
•Introduction to the New Mainframe: z/OS Basics, SG24-6366
•Hardware Management Console Operations Guide 2.13.0
•z/OS MVS System Messages Vol. 6, SA22-7636
•z/OS MVS System Messages Vol. 7, SA22-7637
•z/OS MVS System Messages Vol. 8, SA22-7638
•z/OS MVS System Messages Vol. 9, SA22-7639
•z/OS MVS System Messages Vol. 10, SA22-7640
•z/OS MVS System Codes, SA22-7626
•z/OS MVS System Commands, SA22-7627
•z/OS JES2 Commands, SA22-7526
9.4 Scenario
It is assumed that a new z13 server is installed and powered-on reset with IOCDS A0, which is your minimum I/O hardware configuration to meet COD requirements. In addition, it is assumed that you have COD data that is restored on three DASD volumes on your storage subsystem and two local non-SNA 3270 terminals that are defined according to your I/O configuration. COD LPAR also must be activated.
9.5 Workflow
The Phase 6 tasks that are shown in Figure 9-2 are based on our scenario.
Figure 9-2 Workflow to IPL COD z/OS driving system.
After you initial program load (IPL) your COD z/OS driving system, you can expand your driving system configuration and use it for z/OS ServerPac installation.
9.5.1 IPL COD z/OS driving system
We complete the following steps to load your COD z/OS driving system:
1. We log on to the HMC by using the SYSPROG profile.
2. We select Systems Management → Systems → P02B63B7 (our z13 server name), and then, COD (our COD LPAR name) from the images list that is in the center of window.
Figure 9-3 Load COD z/OS driving system
4. The Load window opens, as shown in Figure 9-4. We select Load Type normal and complete the Load Address field with the first SYSRES volume address (in our case, device address 1200). Then, we click OK.
Figure 9-4 Load information
Figure 9-5 Load confirmation window
6. A disruptive task confirmation window opens, as shown in Figure 9-6. We enter the password and click Yes to proceed.
|
Note: Verify that the correct LPAR is used before proceeding.
|
Figure 9-6 Disruptive task confirmation window
The hardware portion of the IPL starts until a message is displayed that indicates it is completed, as shown in Figure 9-7.
Figure 9-7 Hardware portion of IPL
7. We click OK to close the pop-up window and you can see the Nucleus Initialization Program (NIP) messages on the NIP console, which is our case is the local non-SNA 3270 console address 00A1, as shown in Figure 9-8.
Figure 9-8 NIP console messages
As shown in Example 9-1, the messages that are shown from the system (“System:”) are followed by the command that is entered by the user (“User”).
Example 9-1 NIP console messages
System: IEA101A SPECIFY SYSTEM PARAMETERS FOR z/OS 01.13.00 HBB7780
User: R 00,CLPA,SYSP=00
System: IEE600I REPLY TO 00 IS;CLPA,SYSP=00
IEA376I VIODSN PARAMETER IS 'IGNORE'. NO VIO JOURNALING
IEA598I TIME ZONE = W.00.00.00
IEA549I SYSTEM CONSOLE FUNCTIONS AVAILABLE
System: ICH509I SYSRACF DD STATEMENT NOT SPECIFIED IN MSTRJCL OR
ALLOCATION FAILURE FOR IBM RACF DATA SET.
*01 ICH502A SPECIFY NAME FOR PRIMARY RACF DATA SET
SEQUENCE 001 OR 'NONE'
User: R 01,SYS1.RACF
System: IEE600I REPLY TO 01 IS;SYS1.RACF
*02 ICH502A SPECIFY NAME FOR BACKUP
SEQUENCE 001 OR 'NONE'
RACF DATA SET
User: R 02,NONE
System: IEE600I REPLY TO 02 IS;NONE
System: ICH520I z/OS SECURITY SERVER (RACF HRF7780) IS ACTIVE.
System: *03 $HASP426 SPECIFY OPTIONS - JES2 z/OS1.13
User: R 03,COLD,NOREQ
System: IEE600I REPLY TO 03 IS;COLD,NOREQ
System: *$HASP479 UNABLE TO OBTAIN CKPT DATA SET LOCK-MEMBER=CPAC
04 $HASP454 SHOULD JES2 BYPASS THE MULTI-MEMBER INTEGRITY
LOCK? ('Y' OR 'N')
User: R 04,Y
System: IEE600I REPLY TO 04 IS;Y
*$HASP436 CONFIRM COLD START ON
* CKPT1 - VOLSER=Dxxxxx DSN=SYS1.HASPCKPT
* CKPT2 - NOT IN USE
* SPOOL - PREFIX=Dxxxx DSN=SYS1.HASPACE
*05 $HASP441 REPLY 'Y' TO CONTINUE INITIALIZATION OR
'N' TO TERMINATE IN RESPONSE TO MESSAGE HASP436
User: R 05,Y
System: $HASP493 JES2 COLD START IS IN PROGRESS
$HASP423 Dxxxxx IS BEING MINI-FORMATTED
$HASP266 JES2 CKPT1 DATA SET IS BEING FORMATTED
$HASP267 JES2 CKPT1 DATA SET HAS BEEN SUCCESSFULLY FORMATTED
$HASP492 JES2 COLD START HAS COMPLETED - z11 MODE
IEF403I INIT - STARTED - TIME=19.59.50
$HASP309 INIT 1 INACTIVE ******** C=A
BPXI004I OMVS INITIALIZATION COMPLETE
User: S VTAM
System: $HASP100 VTAM ON STCINRDR
$HASP373 VTAM STARTED
IST093I TSOAPPL ACTIVE
IST020I VTAM INITIALIZATION COMPLETE FOR CSV1R13
IST1349I COMPONENT ID IS 5695-11701-1D0
IST1348I VTAM STARTED AS SUBAREA NODE
User: S TSO
System: IEF403I TSO - STARTED - TIME=tt.tt.tt
IKT007I TCAS ACCEPTING LOGONS
IKT005I TCAS IS INITIALIZED
8. Terminal 00A0 must be brought online because it is the local non-SNA 3270 console for our TSO/E session. We enter the following command:
V 00A0,ONLINE
9. We must activate a console major node on IBM VTAM® that defines the console to be used during TSO/E session, which depends on your I/O configuration. For more information, see the COD documentation. In our scenario, we enter the following command:
V NET,ACT,ID=D0A00BF
10. We log on to TSO/E by using the second local non-SNA 3270 console (as shown in Figure 9-9) and respond by entering the following command:
LOGON DRVUSER
Figure 9-9 TSO/E session
11. A panel is displayed in which all of the necessary information is completed except for the password. We enter the password DRVUSER in the PASSWORD field. The following information is shown:
ICH70001I DRVUSER LAST ACCESS AT HH:MM:SS ON
IKJ56455I DRVUSER LOGON IN PROGRESS AT HH:MM:SS
IKJ56951I NO BROADCAST MESSAGES
The CUSTOMPAC MASTER APPLICATION MENU window is displayed, as shown in Figure 9-10.
Figure 9-10 CustomPac primary option menu
Now we are logged on to TSO/E and can continue to customize the COD z/OS driving system to install ServerPac.
Shutdown
If the COD z/OS driving system must be shut down in an orderly manner, we must proceed with a controlled process.
We complete the following steps:
1. We exit ISPF from the CUSTOMPAC MASTER APPLICATION MENU by using the X command (exit) from the Primary Option menu. The Log and List Defaults data set panel is displayed.
2. After we leave ISPF, we log off TSO/E by entering LOGOFF at the system READY prompt.
3. TSO/E displays several messages. We select Enter. The system displays the following message:
THIS TERMINAL IS LOGGED ON TO UNFORMATTED SYSTEMS SERVICES.
We are now logged off and the console is disconnected.
4. We stop TSO/E by entering P TSO on the console.
The system displays the following information:
IKT006I TCAS ENDED
IEF404I TSO - ENDED - TIME=hh.mm.ss
$HASP395 TSO ENDED
5. We stop VTAM by entering Z NET,QUICK.
The system displays the following information:
IST097I HALT ACCEPTED
IST133I VTAM TERMINATION IN PROGRESS
$HASP395 VTAM ENDED
IST102I VTAM IS NOW INACTIVE
6. When VTAM ends, LLA and VLF can be stopped by entering the following commands:
STOP LLA
STOP VLF
The system displays the following information:
COF033I VLF HAS TERMINATED BECAUSE OF AN OPERATOR STOP REQUEST
IEF404I VLF - ENDED - TIME=hh.mm.ss
IEF352I ADDRESS SPACE UNAVAILABLE
IEF404I LLA - ENDED - TIME=hh.mm.ss
IEF352I ADDRESS SPACE UNAVAILABLE
CSV210I LIBRARY LOOKASIDE ENDED
7. When LLA and VLF end, JES2 can be stopped by entering $PJES2,TERM.
The system displays the following information:
$HASP314 INIT 1
$HASP314 INIT 2
$HASP314 INIT 3
DRAINED ******** C=A
DRAINED ******** C=AB
DRAINED ******** C=ABC
$HASP085 JES2 TERMINATION COMPLETE
IEF404I JES2 - ENDED - TIME=hh.mm.ss
8. We stop z/OS by entering Z EOD.
The system displays the following information:
IEE334I HALT EOD SUCCESSFUL
We now move on to Phase 7.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.