JCL to trigger job using U7SVC

Addsmiles · New User Joined: 26 Oct 2007 Posts: 2 Location: US

We are receiving some files on our mainframe system from a UNIX box. We want some mainframe jobs to be triggered as soon as those files land.

We asked UNIX folks to send the following JCL to JES after the actual data file. This JCL is supposed to create a CA7 trigger dataset which is set to kick off our mainframe job.

//TRIGJOBA JOB (TRIG),'TRIGGER JOB JOBNAMEA',
// MSGCLASS=G,USER=ABCD,REGION=0M
//JS00010 EXEC PGM=U7SVC,
// PARM='D=CA7TRIG,CA7TRIG.ABCD.JOBNAMEA.AS4CS01'
//

The JCL is getting executed, but we are getting the error "VOLSER ENTRY FOR DATASET INVALID".

Hence the CA7 trigger is not working as expected.

dick scherrer · Posted: Thu Dec 25, 2008 8:31 am

Hello and welcome to the forum,

If you post more completeinfo from the problem run, we may be better able to help.

Where do you see the error message? What messiag id is shown? How is the jcl being "sent"?

Addsmiles · New User Joined: 26 Oct 2007 Posts: 2 Location: US

I see this error message in SAR.

The JCL is directly being sent to JES by using the command quote site type=jes on Unix side.

The problem may also be that even though the JCL is visible in SAR, it may not have executed under CA7.

ae86ibm · New User Joined: 18 Feb 2009 Posts: 1 Location: Hong Kong

I think CA7 has a method called trigger by dataset. When a dataset is received completely, CA7 will trigger the job you setup.

shanuss · New User Joined: 16 Jul 2008 Posts: 17 Location: Chennai

Please try the above solution. I have seen one job that gets triggered whenever a new file arrive. So this is feasible with CA-7

northman22 · Posted: Tue Mar 03, 2009 11:14 am

IF you want to run the Job from CA7 it first needs to be set up to run in ca7. Then you can demand the job with the FTP batch trailer step after the file transfers ok, or post a requirement to an existing job. In the "old days" a dataset had to be created by CA7 for it to recognize a new version of the gdg. So auto posting by dsn will probably not work.

//CA7stepxx exec CA7BTI
//sysprint dd sysout=*
//sysin dd *
/logon
/demand job=jobxxxxx
/logoff

You may need other reqiurements such as jclid= or sched=.
To post and existing job check the manual. You have to go through the steps like you are on CA7.

/logon
/dbm
/jobdep,job=*********, usr=xxxxxxx,post=x
/logoff

I know that second command is not accurate. There are several types of dependencies you can put on a job in CA7. I don't have books in front of me any more, so this stuff is oldy moldy. The job will have to have access to CA7 also. Good luck.