IBM Mainframe Forum

Hi all,

I have a requirement where the name of PS file A will be present in another PS file B. My requirement is to take the backup of PS FILE A into a GDG base by reading the data in PS FIle B. I am able to meet the above requirement.

THe issue /query is the attributes of PS file A changes on a daily basis. So, while creating the PROC, how do i get the DCB attributes of the PS FileA? if we can get the PS file A attributes dynamically then we can create a generalised PROC for the same

Thank you all in advance

If the RECFM is variable, you don't have an issue -- just use a long record length for the LRECL (VB,27994,27998 for the DCB would work) since variable length records are okay as long as there are no records with record length larger than the LRECL.

If the RECFM is fixed but changes daily, you have two major issues -- first, there will be no way to have a PROC with the LRECL in it (although you could pass the DCB parameters as PROC parms), and second, a program retrieving generations will have to know -- FOR EACH GENERATION -- what the LRECL is and handle it separately.

Depends on the product that you use to create the backup
In some cases the RECFM / LRECL of the input dataset is irrelevant - DF/dss being one said product
ICEGENER can be used without specification of the RECFM / LRECL

Maybe the JCL LIKE parameter can do the trick?

Thankyou all for the quick reply and solutions. I tried with ICEGENER but that didnt work and LIKE parameter will take the attributes that of PS FILEB but not PS FILEA

but that didnt work

is a meaningless phrase unless you specify how it did not work.

LIKE parameter will take the attributes that of PS FILEB but not PS FILEA

only if you specify the DDNAME of FiLEB - I presume you mean data set B.

It was line 4 of the JCL that caused the problem

Psychic day rules OK

If the name of dataset B could be in a member and be in the JCL SET format, like // SET DSB='name.of.b', then it could be done like in this sample:

WJ.REF.LIB(NAMEA)

A preceeding IEBGENER could put the sequential dataset into a pds member, but the format must still be a JCL SET.
If this is still not satisfactory, then I think you need start looking at a programmable solution.

Or maybe this would work too

A quick change to the SYSUT2 definition

willy jensen wrote:If the name of dataset B could be in a member and be in the JCL SET format, like // SET DSB='name.of.b', then it could be done like in this sample:

Select all

//*                                                          
//  JCLLIB ORDER=WJ.REF.LIB                                  
//*                                                          
//P1       PROC DS=,REFM=                                    
//         INCLUDE MEMBER=&REFM                              
//G1       EXEC PGM=IEBGENER                                  
//SYSPRINT DD SYSOUT=*                                        
//SYSIN    DD DUMMY                                          
//SYSUT1   DD DISP=SHR,DSN=&DS                                
//SYSUT2   DD DISP=(,PASS),SPACE=(CYL,(1,40)),DCB=*.SYSUT1
//         PEND                                              
//*                                                          
//DSA      EXEC P1,DS=WJ.TEST.DS1,REFM=NAMEA                  
//DSB      EXEC P1,DS=WJ.TEST.DS2,REFM=NAMEB                  

WJ.REF.LIB(NAMEA)

Select all

// SET REFNAME='WJ.TEST.DS1'  

A preceeding IEBGENER could put the sequential dataset into a pds member, but the format must still be a JCL SET.
If this is still not satisfactory, then I think you need start looking at a programmable solution.