Validating accounting code in job

henry_he01 · New User Joined: 14 May 2009 Posts: 9 Location: China

Is there any utility can validate accounting code before executing the following steps?

expat · Posted: Wed Aug 25, 2010 2:08 pm

You will need to talk to one of your sysprogs (site support / site admin or whatever else that they get called these days) regarding the JES exits.

henry_he01 · New User Joined: 14 May 2009 Posts: 9 Location: China

So besides getting this done by support team, no way to validate/restrict accounting code even for test job?
As I don't want to engage others only for a change in testing environment...

expat · Posted: Wed Aug 25, 2010 2:43 pm

If a tool is available for a specific task then why reinvent the wheel and create something else.

henry_he01 · New User Joined: 14 May 2009 Posts: 9 Location: China

OK~~

Why I'm asking this is we're going to follow a new standard of accounting code. To avoid submitting jobs with incorrect accounting code, we'd like to add some validation/restriction on this. Of course, our support team can help on this. But the process will be a little complex by engaging them:P....

Could you please provide any suggestions on this as per your experience? Thanks a lot in advance!

expat · Posted: Wed Aug 25, 2010 3:04 pm

Unfortunately no. I have only encountered the restriction of accounting information via the exit route. Maybe one of the sysprogs may know another way but I think probably not.

dbzTHEdinosauer · Posted: Wed Aug 25, 2010 3:10 pm

it is a little bailing-wire and rubberbanded, but:

1st establish what validation needs to be done -

are there some test jobs that can only use accounting codes 1 - 5 and others only 6-8
relationships between keywords in job and accounting code

create a file of valid accounting codes - include any relationship keywords.

write an ISPF MACRO that would validate the accounting code in your jcl based on the file-of-accounting-codes(above).

Other than that you need sysprogs, because the jes exits are not something to which you have access and the accounting-codes file/data that the jes exits use, again, you have no access.

Robert Sample · Posted: Wed Aug 25, 2010 4:54 pm

As far as I know, JES exit is the way to do this. ROSCOE supports its own way of validating job accounting information, but that has to be done as part of the ROSCOE installation, so again a systems programmer would be involved.

dick scherrer · Posted: Wed Aug 25, 2010 7:42 pm

Hello,

I'm confused as to why anything is needed. . .

Systems that validate the accounting info flush the job if it is invalid.

If the code is valid, but incorrect, it should also pass any newly implemented external edit . . .