Page 2 of 3

Re: Replacing PS name with new name

PostPosted: Tue Feb 14, 2012 1:59 pm
by vamsyk9
Yes Enrico, I want to replace the old generations with new Generation of which i am getting from previous step. Instead of creating a new JCL with those Generations manually. I created a master PARM file with old files and format ,so I am trying to replace the old generations with new generations and new volume serial numbers.

Hope this is clear, If not please let me know.

Re: Replacing PS name with new name

PostPosted: Tue Feb 14, 2012 2:16 pm
by enrico-sorichetti
the explanation is clear... but,
the approach is against any good judgement and good practices !
again i ask what is wrong in using the proper GDG naming convention <gdgbase>(0) to address/use the latest/current GDG ???

in any organization with reasonably QA your solution will be rejected, and You might even reprimanded for wasting time

Re: Replacing PS name with new name

PostPosted: Tue Feb 14, 2012 2:55 pm
by vamsyk9
I am using this for copying some database to test regions, So it is not going to implement in Live... This will make my job more simpler..

Re: Replacing PS name with new name

PostPosted: Tue Feb 14, 2012 2:57 pm
by BillyBoyo
and to reiterate enrico's earlier point about the volume numbers. Why are those being allocated outside your tape-management system?

Crossing in the post, how does it make your job simpler? Instead of writing and submitting a piece of JCL, you are trying to do all this just to save the SUBmit? And give yourself the chance of screwing-up in the process?

Re: Replacing PS name with new name

PostPosted: Tue Feb 14, 2012 3:04 pm
by vamsyk9
No, I am fectching all the GDG's and respective volume serial numbers from spool from previous steps, I need to do like this. No other alternative with me.

Re: Replacing PS name with new name

PostPosted: Tue Feb 14, 2012 3:15 pm
by BillyBoyo
OK then, explain clearly please why you can't use "normal" GDG referencing and why you can't use catalogued volumes.

Also bear in mind you only think you are getting the volumes from a previous step. Most of the time you will be, and then there will be an almighty mess when you don't.

Re: Replacing PS name with new name

PostPosted: Tue Feb 14, 2012 3:29 pm
by vamsyk9
I will be getting volumes as i am extracting from ran job(already completed) this is mainly to keep track of GDG's generations for future use. I am basically trying to take the back-up of live database to test region. Some times we require those GDG'S will be helpful to load that week database.

Re: Replacing PS name with new name

PostPosted: Tue Feb 14, 2012 3:40 pm
by BillyBoyo
Now I'm really confused. You have access to production data? And you want to sometimes copy it to another environment, just like that? What is your job title? How come you and your colleagues can't come up with a more standard sort of solution?

The point about copying the vols from a previous step is, the time that your code fails to do this, for whatever reason, will cause you a problem. You have a catalog entirely seperate from the one production uses?

Re: Replacing PS name with new name

PostPosted: Tue Feb 14, 2012 3:57 pm
by vamsyk9
You are not answering my question, U are simply wasting my time.that is my requirement, I am trying to do that. If possible please help me rather than asking unnecessary questions. If you have the solution or logic, Please let me know.

Re: Replacing PS name with new name

PostPosted: Tue Feb 14, 2012 4:13 pm
by BillyBoyo
I'm trying to avoid you wasting your time,

File 1

a line
a line
a line
an important line with a <unique way of identifying> followed by unimportant stuff
another line
a second important line with <another unique identifier> maybe with unimportant stuff


File 2 (parameters)
<first unique identifier> <value to replace>
<second unique identifier> <second value to replace>


Where "<" and ">" are delimiters of any type you choose which are not naturally going to appear in the thing to be acted upon.

Forget it is JCL. Just get the substitution correct. Don't forget it is JCL when designing the parameters/skeleton - can you extend over more than one line with the vols?