Unsolved
This post is more than 5 years old
15 Posts
0
667
August 28th, 2009 12:00
Timid users
I am migrating from z/OS v1.4 to z/OS v1.7. I have applied the maintenance to TERASAM for the migration. I need the users to test, but they are afraid to run the segment definition job, because it as been a very long time since it has run. They would like another to test the migration fixes without necessarily re-assembling the segment table. Is there a way to do this? The users do not like the fact that all of the datasets both production and test are in the same assemble. Is there another method of separating the test and production datasets? Thank you.
No Events found!
Davidy8s
154 Posts
0
August 28th, 2009 12:00
1: Use the TeraSAM SEGDEF utility for your test data sets. This uses Catalog control, marks the excpexit field of the data set & uses that to identify candidate data sets to TeraSAM. This would mean you would need to have TeraSAM enabled with CONTROL=BOTH - meaning use segment tables and catalog control.
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-001-881.pdf#page=60
2: You can also use a Test Segment Definition table.
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-001-881.pdf#page=100
Your test jobs would need the //SEG@nnnn DD statement as described in the manual above.
Does that help?
Dave Yates
EMC TSE3
Benevolent Host S/W & Mainframe Forum Moderator
"Il Moderatore Benevolo"
jrtumb
15 Posts
0
August 28th, 2009 13:00
I do think this would help. Can I turn Catalog=BOTH on when I next enable TERASAM? I will start my research now.
James.
Lehlia
24 Posts
0
August 28th, 2009 13:00
Davidy8s
154 Posts
0
August 28th, 2009 13:00
I attached 2 files as examples.
Best regards,
Dave Yates
EMC TSE3
Benevolent Host S/W & Mainframe Forum Moderator
"Il Moderatore Benevolo"
2 Attachments
seg@xxxx.txt
ts.txt
Davidy8s
154 Posts
0
September 10th, 2009 05:00
Dave Yates
EMC TSE3
Benevolent Host S/W & Mainframe Forum Moderator
"Il Moderatore Benevolo"
1 Attachment
ASMSEGTB EXEC ASMHCL.txt