|
View previous topic :: View next topic
|
| Author |
Message |
mohitsaini
Warnings : 1
New User
Joined: 15 May 2006
Posts: 92
|
|
|
|
Hi there,
The below step basically reads a file (from Sortin), takes 3 characters from this file and writes to a JCL which is then submitted thru INTRDR thru SORTOUT.
Step's snapshot is below:
| Code: |
//STEP01 EXEC PGM=SORT,COND=(1,LT)
//SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(100,50),RLSE)
//SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(100,50),RLSE)
//SORTIN DD DSN=&&TEMP3,DISP=SHR
//SORTOUT DD SYSOUT=(*,INTRDR)
//SYSIN DD DSN=ENVIORN.CSLIB(cslibmem),DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSLIST DD SYSOUT=* |
cslibmem snapshot is below (here I have shown only the JCLCard. A long JCL follows this):
| Code: |
SORT FIELDS=COPY
OUTFIL OUTREC=(C'//TSUBU',8,3,C' JOB (SXXXXXBL----------,RA40),''DDF *
INPUT'',',18X,
/,C'// CLASS=M,MSGCLASS=M,',38X,
/,C'// USER=BLL,TIME=NOLIMIT',36X,
/,C'//*',69X, |
Query:
If the sortin file is empty then jobcard will have only 5 characters name (which is invalid). So I am not sure what happens to the dynamic JCL that is created and submitted in Sortout.
During testing, I have figured out is that if Sortin file is having a record then JCL thru INTRDR is submitted successfully and I can see that in the spool which is fine because in this case the jobname is composed with full 8 characters. But if the Sortin file is empty then the dynamic JCL name will only of 5 characters (which is invalid) and I can't see the dynamic JCL submitted (if submitted at all) thru INTRDR in spool and infact no where. So I am just wondering what happens to that job and where does it go.
I hope I have explained my requirement clearly.
Regards,
Mohit |
|
| Back to top |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
Five-character JOB names are not invalid. The way you are creating the JOB name is invalid for an input with fewer than three characters on a record.
You are using OUTFIL OUTREC (should be OUTFIL BUILD), so your JOB only gets created when there is at least one record on a file. There will be no output for an empty file.
What you need to do is to deal with the blanks inserted when your (single record, you should do that) has fewer than three characters at the start.
EDIT: Corrected from "the JOB name is valid for an input with fewer than three characters on a record" |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| But if the Sortin file is empty then the dynamic JCL name will only of 5 characters (which is invalid) and I can't see the dynamic JCL submitted (if submitted at all) |
Why do you believe a 5-char job name would be invalid? Might this be a site-specific limitation?
If you are permitted to use the sdsf log function, submit the job and watch the log. You should see it entering the system and some foot print as to what happened.
Have you successfully submitted jobs via the internal reader or is this the first attempt? |
|
| Back to top |
|
|
mohitsaini
Warnings : 1
New User
Joined: 15 May 2006
Posts: 92
|
|
|
|
| Quote: |
| Why do you believe a 5-char job name would be invalid? Might this be a site-specific limitation? |
I believe so because when I open a JCL thru PDS member and give a 5 char jobname and then submit it - I just get a message on the screen saying that job is with invalid name and the job doesn't come in spool at all.
| Quote: |
| If you are permitted to use the sdsf log function, submit the job and watch the log. You should see it entering the system and some foot print as to what happened. |
Thanks for this. I need to check with my admin for the same.
| Quote: |
| Have you successfully submitted jobs via the internal reader or is this the first attempt? |
Yes, in my application, such jobs have been successfully submitted in Live region but as I had stated earlier those jobs are having a full 8 character jobname. However, when the job name is less than 8 characters then I can't see the job in the spool (Live region again). So that's why I asked this query on where exactly this invalid job is going thru INTRDR if it is not submitted. |
|
| Back to top |
|
|
mohitsaini
Warnings : 1
New User
Joined: 15 May 2006
Posts: 92
|
|
|
|
| Quote: |
| You are using OUTFIL OUTREC (should be OUTFIL BUILD), so your JOB only gets created when there is at least one record on a file. There will be no output for an empty file. |
Thanks for this tip but the example that I showed you is already running in Live and my query basically popped up from there. This live job is picking 3 characters from an input file to have different connect direct jobs running for different pos ids (a bit specific to my domain here but just mentioned to set the context). So if the input file is not having any pos id then I want to know where exactly this connect direct job goes because I can't see that in spool. It is not executed for sure because I can't see any file getting transferred too.
| Quote: |
| What you need to do is to deal with the blanks inserted when your (single record, you should do that) has fewer than three characters at the start. |
Thanks but I am not looking for a solution to handle this. Instead, I would like to know how a job with 5-character jobname is submitted thru INTRDR and where exactly does it go because I can't see any "invalid" job submitted in Live region. Dick has advised to use SDSF log to check what happens once the job with "invalid" jobname is submitted. I will check that and update you on that. Thanks for your time. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8700
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
| a job with 5-character jobname is submitted thru INTRDR |
YOU do not understand. A job name can be one to eight characters, so there is nothing special about a five-character job name. And sites often have site requirements for job names -- and if there is a requirement AT YOUR SITE to use longer job names, you must contact someone that works at your site to resolve the issue. Nobody on this forum works for your site, so nobody on this site can help you since we do not know your site standards.
And if the job name is invalid, either due to something wrong with the job parameters or because it fails site standards, the job is not submitted. Whether or not you can view such failed jobs depends upon your site and how it is doing things, so again you need to talk to your site support group for assistance. |
|
| Back to top |
|
|
mohitsaini
Warnings : 1
New User
Joined: 15 May 2006
Posts: 92
|
|
|
|
| Thanks Robert for your inputs |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
At my site, bad job cards with bad names end up with a nasty looking system-assigned job name.
I have to look them up by owner-id instead of job name. Since we use Flasher, that's easy to do. |
|
| Back to top |
|
|
|
|
  |
All times are GMT + 6 Hours |
|
