Hello,
We have two sets of IPL volumes named IPLVL1 and IPLVL2. 
Data sets on these volumes are cataloged to volser ******
If the system is IPLed on IPLVL1, then we rebuild some data sets on IPLVL2, and 
vice versa.

We are IPLed on volume IPLVL1 and we want to rebuild data set SYS2.TSO.CLIST on 
volume IPLVL2.
Data set SYS2.TSO.CLIST on volume IPLVL1 is in use by many logon procs.

We are having a problem building dataset, SYS2.TSO.CLIST on IPLVL2.  .
We build data set SYS2.TSO.CLIST.BUILD on IPLVL2 by copying many different 
clists to it. This data set is cataloged to volume IPLVL2 during this process.
We then want to copy SYS2.TSO.CLIST.BUILD, on IPLVL2, overtop the existing data 
set, SYS2.TSO.CLIST, on IPLVL2. 
We used the following JCL to do this:
//RENAME    EXEC PGM=ADRDSSU                                    
//SYSPRINT  DD SYSOUT=*                                        
//RESVOL     DD DISP=SHR,UNIT=SYSALLDA,                         
//                      VOL=REF=SYS2.TSO.CLIST.BUILD                            
      
//SYSIN       DD *                                               
   COPY                                                                         
  -           
    INDDNAME(RESVOL)                                                    -       
    
    OUTDDNAME(RESVOL)                                                 -         
  
    DATASET(INCLUDE(SYS2.TSO.CLIST.BUILD))                 -           
    RENAMEU((SYS2.TSO.CLIST.BUILD,SYS2.TSO.CLIST))    -           
      NULLMGMTCLAS NULLSTORCLAS                                 -           
      TOL(ENQF) REPLACEUNCONDITIONAL                          -           
      ALLDATA(*)  ALLEXCP  PURGE  SPHERE     

Sometimes this job runs successfully and sometimes it fails with the following 
error:
        ADR380E (001)-ALLOC(05), DATA SET SYS2.TSO.CLIST.BUILD NOT PROCESSED, 
10    

The cause of this error is as follows:
ADR380E (xxx)-mmmmm(yy), DATA SET dsname NOT PROCESSED, {reason_code |
        reason_code-xxx} [INDEX dsname VOLUME volser]

Explanation: The data set was not copied, restored, converted, or released. The 
reason codes (reason_code or reason_code-xxx) are:
10 
The movable data set on the receiving volume is smaller than the data set on 
the source volume. Failure occurred in the scratch; the data set cannot be 
scratched and reallocated. 

In this particular case, data set SYS2.TSO.CLIST.BUILD is indeed smaller than 
data set SYS2.TSO.CLIST on volume IPLVL2.
The IBM manual recommends we Scratch the data set and rerun the job.

However, scratching the data set before we run the above JCL is a problem:
The data set is always in use, so the following JCL does not run:
  //CLEANUP2 EXEC PGM=IEFBR14                                   
  //DD1      DD  DISP=(MOD,DELETE,DELETE),DSN=SYS2.TSO.CLIST,   
  //             UNIT=SYSALLDA,                                 
  //             VOL=REF=SYS2.TSO.CLIST.BUILD    

A DISP of (SHR,DELETE,DELETE) has the same problem.

NOTE we use volume references for the volser, so the same JCL will work for 
both sets of IPL volumes.

We cannot use the IEHPROGM utility, as you cannot use volume references with 
this utility.

Any suggestions to get around this problem would be appreciated.


                  

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to