How are Cataloged Procedures used on your system(s)?

dick scherrer · Posted: Tue Jan 27, 2009 5:26 am

Hello,

Recently, a fairly new client asked about ways to reduce errors in submitted Production jobs. When they showed me how they process production, i was more than a little surprised (shocked?) that they do not support application PROCs. Everything is run inline and all run-specific info is modifed for every job submitted.

I'm looking for feedback on how your organizations use cataloged procedures. For this poll the term "cataloged PROC" refers to one or multiple PROCs executed in a job.

Thank you for your time and your reply,

d

Craq Giegerich · Posted: Tue Jan 27, 2009 5:42 am

All of our production jobs use proc's and all of our compiles are done using proc's. The proc's are developed as the jobs move thru test & development and are then moved to production. Test versions of the proc's are used for testing changes. We use a lot of symbolics in our proc's so when a job is moved from test to production all we need to change is the jcllib and an include statement that set DSN HLQ's etc for either test or production and the job card accounting codes.

Robert Sample · Posted: Tue Jan 27, 2009 6:40 am

Most but not all of our production jobs run using PROC's. Some jobs, such as FTP jobs, are not run via PROC -- although there are some NETFTP files to provide remote server security. All of our production jobs do go through CA-7, triggered by time or other jobs.

gcicchet · Posted: Tue Jan 27, 2009 7:13 am

Most but not all of the production jobs use PROC's. A lot of the parameters are passed via the scheduling tool used on that system.

Gerry

Arun Raj · Posted: Tue Jan 27, 2009 9:03 am

All of our production jobs use PROCs. And we use symbolics for HLQs, DB2 system names, etc. These will be initialized within the PROC to PROD values. So while testing we just override these with TEST environment values.

But recently I have been working for a new client where everything is coded in-line in jobs. All FTP cards, control cards,sort cards etc are coded straight away within the job. But they have a few exceptions of built-in procs for executing a COBOL-DB2 program, Multiple Dataset deletion using IEFBR14 etc. I was really surprised by these strange(bad) coding standards.

dick scherrer · Posted: Tue Jan 27, 2009 9:22 am

Hi Arun

Arun Raj · Posted: Tue Jan 27, 2009 10:45 am

Hi Dick,

I am currently not sure of this. Actually this is a new project which started a few months back and everybody is new to the application. And I came here for a small enhancement task only a few days ago. I asked my peers about this and they dont seem to know the exact reason for following this approach. I saw some 3000-line jobs running in production !!.

dick scherrer · Posted: Wed Jan 28, 2009 3:32 am

Hi Arun,

Anuj Dhawan · Posted: Wed Jan 28, 2009 3:06 pm

Hi Dick,

All the production JOBs use Cataloged Procedures, similar to the standards at Arun's shop, we also use symbolics for HLQs, DB2 system names.. etc. These will be replaced within the PROC to PROD values and there are differnt values for test regions..

Hope my vote counts..Have a good one..

-Ad

dick scherrer · Posted: Wed Jan 28, 2009 3:16 pm

Hi Anuj,

Arun Raj · Posted: Wed Jan 28, 2009 9:24 pm

Hi Dick,

mtaylor · Posted: Wed Mar 04, 2009 6:47 pm

My .02:

The one really large system I worked on previously was similar to others here: All jobs contained cataloged procs and symbolic values that made migrating between test and prod easy. There was some customization of procs for different reasons and these were stored with slightly different names in one main proclib.

For some jobs there was some fairly significant customization done to the proc via overrides and control cards from the JCL.