We have had times when we wanted to review the documents for a deployment set. Now, I am sure there is a better way, but at the time I was new. We took this simple command and wrapped it in a CL to be able to pass in the deployment set. Then we added a command--THISDEPLOY--to be able to call the CL quickly. Now, when we want to see what is happening or has happened, we type THISDEPLOY 000000 where 000000 is the number for the deployment set
WRKSPLF SELECT(ALDONCMS *ALL *ALL &DEPLOY)
------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------
Page 1 / 1
We have had times when we wanted to review the documents for a deployment set. Now, I am sure there is a better way, but at the time I was new. We took this simple command and wrapped it in a CL to be able to pass in the deployment set. Then we added a command--THISDEPLOY--to be able to call the CL quickly. Now, when we want to see what is happening or has happened, we type THISDEPLOY 000000 where 000000 is the number for the deployment set
WRKSPLF SELECT(ALDONCMS *ALL *ALL &DEPLOY)
------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------
WRKSPLF SELECT(ALDONCMS *ALL *ALL &DEPLOY)
------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------
Thank you for sharing your solution which looks great.
We normally recommend appending an "*" asterisk at the end of the deployment set to ensure that all related spool files are captured:
Example:
WRKSPLF SELECT(ALDONCMS *ALL *ALL 0001705*) <== note the "*" appended at the end of the deployment set number.
This ensures that, in addition to spool files having "User Data" = "0001705", spool files for "0001705 1" etc are also caught.
Once again, thank you for sharing a great article.
------------------------------
Jay Mikaiel
Senior Technical Support Engineer
Rocket Software
UK
------------------------------
Hi David,
Thank you for sharing your solution which looks great.
We normally recommend appending an "*" asterisk at the end of the deployment set to ensure that all related spool files are captured:
Example:
WRKSPLF SELECT(ALDONCMS *ALL *ALL 0001705*) <== note the "*" appended at the end of the deployment set number.
This ensures that, in addition to spool files having "User Data" = "0001705", spool files for "0001705 1" etc are also caught.
Once again, thank you for sharing a great article.
------------------------------
Jay Mikaiel
Senior Technical Support Engineer
Rocket Software
UK
------------------------------
Thank you for sharing your solution which looks great.
We normally recommend appending an "*" asterisk at the end of the deployment set to ensure that all related spool files are captured:
Example:
WRKSPLF SELECT(ALDONCMS *ALL *ALL 0001705*) <== note the "*" appended at the end of the deployment set number.
This ensures that, in addition to spool files having "User Data" = "0001705", spool files for "0001705 1" etc are also caught.
Once again, thank you for sharing a great article.
------------------------------
Jay Mikaiel
Senior Technical Support Engineer
Rocket Software
UK
------------------------------
CHGVAR VAR(&DEPLOY) VALUE(%trim(&Deploy) *TCAT '*' )------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.