>This will make things slightly easier (but only slightly) when upgrading in >the future. At the next upgrade, the S1CFG1 disk can be made part of the new >configuration, for the time it takes to complete the job. During that time, >the contents of libraries on S1CFG1 can be used as a source for equivalent >libraries on the 'new' xxCFG1 disk.
But it sounds like one still needs to go through quite some contortions to keep old settings/customization. In any case, I have now divorced just about everything from what is delivered on ADCD on my system, but I got a few scars this weekend when I could not get my system up because the linklist was broken (after the second library). The linklist was broken because IEBCOPY repeatedly destroyed the DCB on a copy operation for a PDSE: //COPY125 EXEC PGM=IEBCOPY,REGION=0M //SYSPRINT DD SYSOUT=* //SYSUT1 DD DISP=SHR,DSN=SYS1.SIEALNKE //SYSUT2 DD DISP=(,KEEP),DSN=SYS1.SIEALNKE.N,DSNTYPE=LIBRARY, // SPACE=(TRK,(4000,0,0)),UNIT=3390,VOL=SER=TGT001 //SYSIN DD * COPY INDD=SYSUT1,OUTDD=SYSUT2 This JCL results in IEBCOPY 'unloading' SYS1.SIEALNKE into arecfm=VS data set (but ending with RC=0) which brings linklist to a screeching halt. For other PDSEs, the same JCL (for other DSNs) dutifully copies the data set, using the DCB information from the input. I had 3 broken PDSEs, two of those in linklist. Brought IPL to a screeching halt, first with wait state for abend806, later when JES2 didn't come up. SYS1.SIEALNKE is the third data set in the linklst concatenation. When I fully specify the output DCB, the copy operation works. I don't know if this is specific to running iebcopy under z1090 code or not since servicelink doesn't let me login today. But I know of one other problem with IEBCOPY only occuring under z1090 code (we have it too, but not the fixing ptf since our distribution is too old.) Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
