Scanning JCL's in PDS

Shriram Jogdand · New User Joined: 14 Oct 2008 Posts: 65 Location: Pune

I have 1000's of JCLs in a PDS. Few of them have TIME parameter and few don't have.

1. I want to search this PDS and find out the list of JCL's which don't contain this Parameter.
2. Once I get the list, I want to add the TIME parameter (TIME=5).

How can I do these 2 tasks?

Sorry if similar post is already available on forum. I searched but didn't get it.

prino · Posted: Fri Feb 13, 2015 4:59 pm

You don't use a TIME= parameter, you use the correct CLASS=, so that one change to the CLASS definition will automatically change all jobs that use that class.

Marso · Posted: Sun Feb 15, 2015 3:44 pm

1. Easy: use ISRSUPC with option LNFMTO
2. Not easy: you may need to split the JOB card if there is not enough space on the line, or the JOB may already be split.

Pete Wilson · Posted: Mon Feb 16, 2015 2:01 pm

Firts I'd suggest you take a copy of the PDS to test your options on so you don't screw up the original!

PDSMAN scan/replace, or FileAid utilities could do this. Another option might be SAS or REXX so you can read the whole member in and modify it before writing it back. This way it might be easier to deal with instances where the jobcard will have to extend to a new line.

Worth exploring Prino's suggestion too. Most companies will have certain jobclasses that are set to allow a fixed amount of CPU time. Different classes will have different times values, so you'd modify the JCL to match the best fit jobclass. It seems primitive to have a fixed TIME= value which will definitely cause the jobs to fail if exceeded, unless that is what you want, for testing jobs perhaps?

steve-myers · Posted: Mon Feb 16, 2015 5:51 pm

Mr. Wilson's third paragraph is not quite correct. The job class setting in JESx defines a default limit for a job step, not for a job. Many ill informed people seem to think the JESx default time is for the entire job. I can't tell you how often I set a large time for a job only to get blown away because of the default step time. I've always thought the default step time should be set high so that the job time would rule.