ca.portal.admin

Re:Non V 1 DC-COBOL calling Non V 1 DC-COBOL

Discussion created by ca.portal.admin on Jul 31, 2008
Hi,

=20

I thought that this was fixed many years ago but here goes.

=20

We have a unique situation where a production user can put our CV into a
very tight loop that can only be fixed by cancelling the CV. We have an
ADS dialog that makes a call to a DC-COBOL program that then calls at
least one other DC-COBOL program. Our investigation involves making a
version 2 of the ADS dialog and version 2's of the DC-COBOL programs. I
have created the V0002 entry that points to the load library that the
version 2 loads exist in and run DCMT VDP statements to define them to
the CV. When we run a test the first DC-COBOL program V 2 gets loaded
and executed but then when it calls the next DC-COBOL program it
disables the V 2 load and puts it out of service so it runs the V 1
load. Same happens with the other DC-COBOL program that gets called
afterwards.

=20

We are on z/OS 1.8 running 16 SP1 (0408) with many apars using the 3.4
COBOL compiler.

=20

Other than using V 2 programs the only thing that is different from V 1
of the first DC-COBOL program is the number of SNAP TITLE xxxx from AAAA
to BBBB. Would these snaps cause the problem?

=20

Thanks

=20

Chris Wood

Alberta Department of Energy

CANADA
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Non V 1 DC-COBOL calling Non V 1 DC-COBOL
"Thanks for your comments Gary.

We are doing a CALL from COBOL. Actual code is move 'PRGRAMA' to
WS-PROGRAM-NAME, CALL WS-PROGRAM-NAME using WORKREC. PRGRAMA has
PROGRAM-ID. PRGNAMEA V 1 IS INITIAL. This way the working storage is
refreshed every call.

We dummied the SNAPs out and it still disables the called DC-COBOL
programs so it wasn't that.

Chris

Outcomes