Initial system use

Be certain you have the four volumes required to IPL. For release 10, these are OS39RA, OS3RAA, OS39M1, and OS39HA; for z/OS R1.1 these are Z1RES1, Z1RES2, OS39M1, and Z1USS1. Be certain your DEVMAP (P/390) or your DEVMAP+IOCDS (MP3000) is set correctly. For an MP3000, you need to perform a Power On Reset (POR) function with the correct IOCDS selected. The IPL address (0A80 or 0AA0 in our examples) and IPL parameter (0A82CS or 0AA2CS for your first IPL) can be set in the configurator F4 frame (P/390), or in the LOAD frame in the SE window (MP3000).

The complete IPL process, especially when using parameters that start DB2, CICS, IMS, and so forth, produce many console messages. Some of them may be error messages, and some may even look like serious error messages. Many of these are expected and will not harm the system; they are associated with initial startup, or with choices that were made when building the AD system. There is no easy guide for interpreting OS/390 console messages and knowing what can be ignored and what is cause for alarm.

The P390 or IBMUSER userid is normally used for all early administration, after installing an AD CD-ROM system. The IBMUSER userid can also be used if RACF is not functional because it (IBMUSER) is also defined in SYS1.UADS.

Additional characteristics of these userids include:

򐂰 IBMUSER (RACF definition)

– Attributes: SPECIAL, OPERATIONS

– Significant TSO authorities: OPER, ACCT, MOUNT – Password interval: N/A

– Group: SYS1

– Size : 4096, Maxsize: 2096128 – Unit: 3390

– UID: 0

– Home: /u/ibmuser

򐂰 IBMUSER (SYS1.UADS definition)

– Attributes: OPER, ACCT, JCL, MOUNT, RECOVER – Password (in UADS) IBMUSER

– Allowed procedures:

• IKJACCNT: Size: 4096, Unit: SYSALLDA • ISPFPROC: Size: 6072, Unit: (none)

򐂰 P390

– Attributes: SPECIAL, OPERATIONS, AUDITOR – Significant TSO authorities: OPER, ACCT – Password interval: N/A

– Group: SYS1 – Size: 6072, Maxsize: 2096128 – Unit: SYSALLDA – UID: 0 – Home: / 򐂰 P390A

– Attributes: SPECIAL, OPERATIONS, GRPACC – Significant TSO authorities: OPER

– Size: 5999, Maxsize: 6000 – Unit: 3390

– No OMVS segment

Userids P390A - P390Z do not have OMVS segments defined.

The AD system provides a large number of IPL options, and these are discussed in the next chapters. If the system volumes are assigned the recommended addresses, initial startup (without DB2, CICS, and so forth) can be done by IPLing address A80, with

IPLPARM=0A82CS; for an MP3000 using the primary disks, these values would be AA0 and 0AA2CS. This should load the system and permit you to log on with userid P390 or

IBMUSER.

Userid Password Authority Purpose

P390 P390 SPECIAL,

OPERATIONS

System administration

IBMUSER SYS1 SPECIAL,

OPERATIONS, SYS1.UADS

Emergency use if P390 userid or RACF is broken

The “CS” portion of the IPLPARM triggers the CLPA function and a cold start for JES2. These need to be done the first time you IPL. Thereafter, if you make no changes to LPA, you can use the parameter 0A8200 (or 0AA200 for primary disks). This will bypass the CLPA and JES2 cold start.

As distributed, the OS39M1 volume is mounted as a STORAGE volume and is the only PUBLIC or STORAGE volume among the distributed volumes. For R10, OS39M1 is approximately 25% full, leaving about 2400 cylinders free. This provides ample scratch space for initial system use.

OS39M1 contains data set SYS1.P390.CNTL. You can add members to this data set (or use any existing members, if appropriate) for your initial work, such as the migration jobs

described earlier. Many of the members in this data set were used to build the AD system, or earlier releases of the AD system. Do not assume all the members are relevant to the current

release.

You may notice that there is significant free space on some of the system volumes. We suggest you consider your future plans before using this space. For one thing, anything on the system volumes (other than OS39M1) will be lost if you use the AD migration functions to move to the next release. Also, free space on the system volumes may be needed for PTF or additional program product installation. Provided you understand these considerations, you can use free space on any of the system volumes.

1.7.1 P/390 error messages

The following OS/2 pop-up message may appear during IPL:

+---+ | P/390 Error | +---+ | AWSDEV908E CU=SCSI348: RC=006E | | opening device driver, DD=SCSI3480 | +---+

This means that you need to activate the SCSI3480.SYS device driver in CONFIG.SYS. Address 560 (in the DEVMAPs shown earlier) defines a SCSI tape drive. There must be a corresponding definition in the OS/2 CONFIG.SYS. You may need to consult the DOC file (or other P/390 documentation) to help you with the precise CONFIG.SYS statement needed. In the meantime, you can simply delete/cancel this message (using the OS/2 mouse) and continue the OS/390 IPL. You cannot use the OS/390 tape drive associated with the missing SCSI tape drive, but there are no other side effects.

If you receive the following pop-up message:

+---+ | P/390 Error | +---+ | AWSLCS350S Open error / | | AWSLCSDD Device Driver | | (Dos open / 110 ) | +---+

you need to activate the LCS3174.SYS device driver in CONFIG.SYS. The following

statement should be in the P/390 section of your CONFIG.SYS. Remove any rem characters before the statement.

See the LCS3172 DOC file for information about preparing your P/390 for OS/390 TCP/IP. In the meantime, you can delete/cancel this popup message and continue with your IPL.