> Subject: Confused on concatenated parmlib and IEASYSxx
>
> If IEASYSNV in VENDOR.PARMLIB specifies PROG=VN and IEASYSLX in
LVL0.PARMLIB
> specifies PROG=LV and when I IPL I state:
>
> SYSP=(LX,NV)
>
> What PROG members will be executed?
>
First, I would suggest if you have not done so, get Mark Zelden's IPLINFO
Rexx. It will display after an IPL what parms are in place from IEASYSxx.
This may help with this type of question.
Next, the IEASYSxx member used at IPL Time is what controls PROGxx.
So what does your LOAD parm show for IEASYSxx?
IPLPARM = 7328Z9 1 (merged)
IPL load parameter data set name: SYS1.IPLPARM
IPL load parameter data set device address: 7328
HWNAME=SRM1 LPARNAME=LPARXX1 VMUSERID=
LOADxx parameters from the IPA (LOADZ9):
*---+1+2+3+4+5+6+7
ARCHLVL 2
IEASYM (PS,L)
IODF 03 SYSH LPARXX1 00
NUCLEUS 1
PARMLIB SYS1.MYCOMP.PARMLIB DCMCAT
PARMLIB SYS1.IBM.PARMLIB Z1BRS3
PARMLIB SYS1.PARMLIB
SYSCAT DCMCAT123CCATALOG.MYCOMP.MASTER
SYSPLEX MYCOMP
So from my environment using Mark's IPLINFO. You can see I have nothing
specified in col 10-11 on SYSPARM statement, therefore that defaults to 00.
During system initialization, NIP first processes the IEASYS00 parmlib
member to establish parameters. Then it determines, from the suffixes
specified on the SYSPARM statement in LOADxx, the SYSPARM parameter in
IEASYMxx, or by the operator, which IEASYSxx members are to be used. See
"Step 2. Determine where to specify system parameters" in topic 2.3.2 for a
description of how the system determines which IEASYSxx members are to be
used.
>From there I go to SYS1.MYCOMP.PARMLIB and pick up IEASYS00. Since I have
multiple PARMLIBs specified, it will seach them to find the first occurrence
of IEASYS00.
I then go to the PROG section in Mark's IPLINFO and see that I have coded:
PROG=(AP,01,H8,02),IEASYS00
This matches my coding in IEASYS00
PROG=(AP,01,&SYSCLONE,02),APF AND LNKLST ACTIVATION
Does this help? Depending on how your LOAD data is coded, is how the system
will load your values.
1) Identify your LOADxx member in your IPL Parms (SYSx.IPLPARM typically)
2) Identify you IEASYSxx in the LOADxx member ( there may be a SYSPARM xx
specified in your load deck)
3) Go to that IEASYSxx member in your PARMLIB dataset.
4) See how the PROGxx entry is coded
Get IPLINFO and analysis is a little easier. Mark's Rexx is either on his
Website or on the CBTTAPE.ORG website.
Check out the MVS Init and Tuning Reference - the section on LOADxx
Lizette
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN