|
View previous topic :: View next topic
|
| Author |
Message |
Peter Warren
New User
Joined: 08 Jul 2009
Posts: 4
Location: London, Uk
|
|
|
|
Can somebody please explain to me.
If I have a COBOL program that has two files defined :
FILEA ASSIGNED to DDNAME1 in JCL
FILEB ASSIGNED to DDNAME2 in JCL
and VSAM FILEC ASSIGNED to DDNAME3 - DDNAME3 isn't defined in the JCL but JCL does have a PARM statement. The program does not have any ACCEPT/LINKAGE or parameter input statements.
Does the FILEC become attached/assignedc to the PARM statement?
Many thanks. |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Code: |
//<stepname> EXEC PGM=<pgmname>,PARM='<some parm string>'
//<ddname> DD <the relevant dd tokens> |
there is no relation whatsoever between the PARM string and a present/missing DD specification
but it would be nice to clarify better Your concerns |
|
| Back to top |
|
|
Peter Warren
New User
Joined: 08 Jul 2009
Posts: 4
Location: London, Uk
|
|
|
|
Sorry. In the program the FILEC is accessed but there is no DD associated with this file in the JCL.
There is a PARM on the JCL but no access in the program.
Somehow the PARM data seems to be read via a keyed read within the program and I am at a loss as to how.
any help would be much appreciated! |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| the second paragraph in the procedure division provides the access |
|
| Back to top |
|
|
Peter Warren
New User
Joined: 08 Jul 2009
Posts: 4
Location: London, Uk
|
|
|
|
Very sorry guys - it turns out we have two programs with the same name in Endevor (different subsystems) and I have looked at the wrtong one in connection with the JCL.
Once again apologies. |
|
| Back to top |
|
|
Phrzby Phil
Senior Member
Joined: 31 Oct 2006
Posts: 1042
Location: Richmond, Virginia
|
|
|
|
So your installation allows duplicate program names?
They may be separate in Endevor, but how about in a loadlib? You must maintain those separately as well.
A bit sloppy methinks. |
|
| Back to top |
|
|
Peter Warren
New User
Joined: 08 Jul 2009
Posts: 4
Location: London, Uk
|
|
|
|
| Loadlibs are all at Endevor system/subsystem level. As we have upwards of 205 systems and > 65,000 COBOL programs (not to mention copybook, copycode, DBRM, CICS pgm, etc). I suppose individual teams/systems may use the same name. If I had checked the loadlib concatenation properly then I would have spotted the issue. Mea Culpa. |
|
| Back to top |
|
|
Phrzby Phil
Senior Member
Joined: 31 Oct 2006
Posts: 1042
Location: Richmond, Virginia
|
|
|
|
Well, with 65K programs (probably 64K more than I've managed), I should backtrack on my easily said, but not so easily implemented comments.
I hereby do so. |
|
| Back to top |
|
|
|
|
