|
View previous topic :: View next topic
|
| Author |
Message |
Savitha Muthukrishnan
New User
Joined: 31 Dec 2006
Posts: 8
Location: Chennai
|
|
|
|
Hi,
Iam getting the following warning message in my JCL "DDNAME REFERENCE REFERS ONLY TO FIRST CONCATENATION".
The step has a JI card to copy a file in to a GDG only on specific days. Can you please let me know what this warning means.
Thanks. |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
| Is there a message number such as IEF??? associated with the message? Is the message coming out when you submit the JCL or when you run some JCL checker on it? If you're having trouble with a job stream, don't you think it might be a good idea to post the JCL (using BBcode) so we can see what you're talking about and not having to guess? |
|
| Back to top |
|
|
Savitha Muthukrishnan
New User
Joined: 31 Dec 2006
Posts: 8
Location: Chennai
|
|
|
|
I get this warning message when I try to "JEM" the JCL to spot errors. This is the step in my JCL :
| Code: |
#JI,ID=(051,052,053,054,055)
//STEP01 EXEC PGM=ICEGENER,
// COND=(0,NE)
//*
//SYSUT1 DD DSN=DATASETNAME,
// DISP=SHR
//*
//SYSUT2 DD DSN=GDG DATASET NAME,
// DISP=(NEW,CATLG,DELETE),
// UNIT=SYSDA,SPACE=(CYL,(50,91),RLSE),
// DCB=(RECFM=FB,LRECL=319,BLKSIZE=0)
//*
//SYSPRINT DD SYSOUT=*
//*
//SYSIN DD DUMMY
//*
#JEND |
code'd
The step has to copy the dataset into a GDG on the specific days mentioned in the JI CARD.
Thanks. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Suggest you look in the JEM documentation.
You could also submit the job with typrun=scan. JCL checkers are notorious for detecting "errors" that are not . . . |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
| If you're not specifying the (+1) generation on SYSUT2, you are referring to all cataloged generations of the GDG. This may be what the error message is about -- especially since your job isn't going to go well when it attempts to open for output all generations at the same time. |
|
| Back to top |
|
|
Savitha Muthukrishnan
New User
Joined: 31 Dec 2006
Posts: 8
Location: Chennai
|
|
|
|
| The warning remains the same despite having a (+1) on SYSUT2. |
|
| Back to top |
|
|
Arun Raj
Moderator
Joined: 17 Oct 2006
Posts: 2481
Location: @my desk
|
|
|
|
| Quote: |
| This is the step in my JCL |
Do you have other steps in the same JCL? If there are multiple steps, how did you conclude that the problem is in this step?
You cant always believe "JCL checkers'. So how about following Dick's suggestion here
| dick scherrer wrote: |
| You could also submit the job with typrun=scan. JCL checkers are notorious for detecting "errors" that are not . . . |
|
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
1. Sugget you JEM the JCL, you'll get something like this:
| Code: |
****** ***************************** Top of Data ******************************
==MSG> *** ERROR SUMMARY AND COUNTS *** JEM JS7.2.0 08/16/2009 23:34:26
==MSG> 0 ADVISORY LEVEL
==MSG> 1 WARNING LEVEL
==MSG> 0 ERROR LEVEL
==MSG> 1 TOTAL ISSUED 0 SUPPRESSED.
==MSG> THE HIGHEST SEVERITY CODE ENCOUNTERED WAS 04.
==MSG> LABEL SV MSG.NO. ERROR MESSAGE
==MSG> -------- -- -------- -------------------------------------------------
==MSG> .JAAA 4 DSS4731W - STMT NOT RECOGNIZED - SYSIN DD GENERATED BY
==MSG> JOB/SCAN |
post that here as it is.
2. Do you concatenate PDS/PDSe and they have same member names -- though what you posted it does not look like that you are delaing with PDS/PDSe but that is what you posted, may be that's not happening actually. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
If you are still having problems, suggest you post the actual expanded jcl that is run rather than what has been posted. . .
To protect your "real" dataset name(s) and job info, replace the actual name with something very similar using the same number of nodes in the dataset names as well as any generation specification. |
|
| Back to top |
|
|
|
|
