When we run a batch job where the application program library is included
in the system linklist, we get an ABND4005 (out of IDMSSTRT) saying that
IDMS fails trying to do a BLDL on the program. Include the library in
CDMSLIB and all is well. Any way I can convince the IDMS batch startup
routines to request its load from the linklist rather than restricting to
the available DD cards??

When we run a batch job where the application program library is included
in the system linklist, we get an ABND4005 (out of IDMSSTRT) saying that
IDMS fails trying to do a BLDL on the program. Include the library in
CDMSLIB and all is well. Any way I can convince the IDMS batch startup
routines to request its load from the linklist rather than restricting to
the available DD cards??

I was afraid that was the answer. This stuff all worked just fine in R14
and prior. Obviously, the load routines have been um,er, uh, enhanced
since then. And, worse, in this case, the program that IDMS is looking for
is the main program being executed in a batch job (e.g. EXEC PGM=xxxx and
the BLDL failure is fir xxxx). Actually, it kind of makes sense. The
system wants to know what kind of application program it is dealing with so
it can build the correct mini-CV environment in the user address space.

Anyway, now all I have to do is convince my applications folks that they
have to insert a CDMSLIB DD card in every jobstream in the house (yeah,
right!). Any other thoughts out there??The phone calls go to CA support
first thing Monday morning.

Alan Fields

I don't think you can. I'm about to get out of my league here, so take
this with a grain of salt.
The IDMS run time system wants to load it's programs out of CDMSLIB (or
CDMSLIBx) using it's own load routines. The normal operating system LOAD
instructions want to load from STEPLIB/JOBLIB, or the LINKLIST. Two
different animals.
Simply, I don't believe the IDMS load operation(s) are designed to look
at
LINKLIST. Personally, I think that's good as it gives you a lot of control
as to where you're going to search.

When we run a batch job where the application program library is included
in the system linklist, we get an ABND4005 (out of IDMSSTRT) saying that
IDMS fails trying to do a BLDL on the program. Include the library in
CDMSLIB and all is well. Any way I can convince the IDMS batch startup
routines to request its load from the linklist rather than restricting to
the available DD cards??

Interesting. There is a PGRSTPG module in our R14.1 IDMS load lib, but
not in our R16 one. There are a number of other 'PG******' modules that
have apparently also been dropped between releases.

Now if I only knew why someone thought we needed an extra copy of it in
the user load lib. And what release that copy is from - it's older than
the R14.1 copy.

look at the load module (or run AMBLIST) to look for zaps applied -
many DBAS will place newly-zapped modules in a higher-up (but
non-system software) loadlib so it can be easily removed if it causes
a problem - but then they forget to move it to the real system software loadlib

I was afraid that was the answer. This stuff all worked just fine in R14
and prior. Obviously, the load routines have been um,er, uh, enhanced
since then. And, worse, in this case, the program that IDMS is looking for
is the main program being executed in a batch job (e.g. EXEC PGM=xxxx and
the BLDL failure is fir xxxx). Actually, it kind of makes sense. The
system wants to know what kind of application program it is dealing with so
it can build the correct mini-CV environment in the user address space.

Anyway, now all I have to do is convince my applications folks that they
have to insert a CDMSLIB DD card in every jobstream in the house (yeah,
right!). Any other thoughts out there??The phone calls go to CA support
first thing Monday morning.

Alan Fields

I don't think you can. I'm about to get out of my league here, so take
this with a grain of salt.
The IDMS run time system wants to load it's programs out of CDMSLIB (or
CDMSLIBx) using it's own load routines. The normal operating system LOAD
instructions want to load from STEPLIB/JOBLIB, or the LINKLIST. Two
different animals.
Simply, I don't believe the IDMS load operation(s) are designed to look
at
LINKLIST. Personally, I think that's good as it gives you a lot of control
as to where you're going to search.

I may have missed something - but this sounds like all you're asking for
is the program name in the EXEC PGM=*** statement of your batch job to
be found in the linklist. That shouldn't have changed as IDMS doesn't
interfere the STEPLIB, JOBLIB and linklist searches - and there should
be no reason for IDMS to issue a BLDL for that program.

If you're running CV mode there should be no requirement for a CDMSLIB,
if you're running local mode only the IDMS system programs need to be in
CDMSLIB. We did not have to make any JCL changes for our upgrade from
14.1 to 16.0. So perhaps there's something about your run-time
environment that I don't understand that is causing your problem.

This e-mail message and any attachments are qualified as follows:
Addressing: If you have received this e-mail in error, please advise by
reply e-mail to the sender. Please also destroy the original
transmission and its contents.
Confidentiality: This e-mail may contain confidential information which
also may be legally privileged. Only the intended recipient(s) may
access, use, distribute or copy this e-mail.
Individual Views: Unless otherwise indicated, the views expressed are
those of the sender, not Justice Technology Services.
Computer Viruses: It is the recipient's responsibility to check the
e-mail and any attached files for viruses.

I may have missed something - but this sounds like all you're asking for
is the program name in the EXEC PGM=*** statement of your batch job to
be found in the linklist. That shouldn't have changed as IDMS doesn't
interfere the STEPLIB, JOBLIB and linklist searches - and there should
be no reason for IDMS to issue a BLDL for that program.

If you're running CV mode there should be no requirement for a CDMSLIB,
if you're running local mode only the IDMS system programs need to be in
CDMSLIB. We did not have to make any JCL changes for our upgrade from
14.1 to 16.0. So perhaps there's something about your run-time
environment that I don't understand that is causing your problem.

This e-mail message and any attachments are qualified as follows:
Addressing: If you have received this e-mail in error, please advise by
reply e-mail to the sender. Please also destroy the original
transmission and its contents.
Confidentiality: This e-mail may contain confidential information which
also may be legally privileged. Only the intended recipient(s) may
access, use, distribute or copy this e-mail.
Individual Views: Unless otherwise indicated, the views expressed are
those of the sender, not Justice Technology Services.
Computer Viruses: It is the recipient's responsibility to check the
e-mail and any attached files for viruses.

Normal
ADS Generator has been dropped from R15 and up
"The ADS Generator has been dropped from R15 and up. I cannot find this
documented in any of the release guides.

Although we no longer use this product to generate new code, we do still
have some production code that was originally created by ADS Generator.
And this code makes calls to at least one ADS Generator load module (the
PGRSTPG load module I was asking about in an earlier thread). So
beware! If you have any such code, it will abend when you upgrade to
anything higher than R14.1.

CA's recommendation is to copy the needed load modules to one of your
own load libraries, where they will be considered ""user-written""
programs from now on. The ADS Generator load module names start with
'PG'. Displaying your program pools will tell you whether these
programs have been loaded, and how many times they have been executed.

As we all know, there is not now nor has there ever been a need to include
CDMSLIB in any batch job that talks to IDMS, CV or local mode. What
appears to be happening is IDMS looking at the application program via a
BLDL so it can build the appropriate environment in the user address
space. If you include CDMSLIB, IDMS will look for your programs there. If
you leave out the CDMSLIB DD cards, he looks at STEPLIB/linklist just like
it's supposed to. When included with all the application libraries, stuff
works. When not included at all, stuff works. When included without all
of the application libraries, the job fails with the 4005.

As best I can tell, this is a change in behavior since R14.1. Back then,
the existence of CDMSLIB in the jobstream was irrelevant; it never got
used. In the R16.2 world, it appears to be functional. It would be nice
if the CA folks on the list could confirm or deny my rather heavy
suspicions.

Our final answer, of course, is to eliminate the CDMSLIB DD cards for all
batch jobstreams. In this case, I had an applications test jobstream
which (incorrectly) included the problematic DD cards and got caught with
the upgrade. Pull the DD cards from the test set and verify that the
production ones are all correct and all will be well.

IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM> wrote on
12/01/2005 03:51:51 PM:

A question for the list:

I put up my first Release 16 in a real test system today (yeah, us!)

When we run a batch job where the application program library is

included

in the system linklist, we get an ABND4005 (out of IDMSSTRT) saying that
IDMS fails trying to do a BLDL on the program. Include the library in
CDMSLIB and all is well. Any way I can convince the IDMS batch startup
routines to request its load from the linklist rather than restricting

Normal
Re: [DB2-L] UDB - Estimate Size Tool in Control Center
"I think you meant to say that version 8.2 is correct. I just did the
math, and I came up with exactly the same answer that V8.2 came up with -
4,158.79 Mb.

I may have missed something - but this sounds like all you're asking for
is the program name in the EXEC PGM=*** statement of your batch job to
be found in the linklist. That shouldn't have changed as IDMS doesn't
interfere the STEPLIB, JOBLIB and linklist searches - and there should
be no reason for IDMS to issue a BLDL for that program.

If you're running CV mode there should be no requirement for a CDMSLIB,
if you're running local mode only the IDMS system programs need to be in
CDMSLIB. We did not have to make any JCL changes for our upgrade from
14.1 to 16.0. So perhaps there's something about your run-time
environment that I don't understand that is causing your problem.

This e-mail message and any attachments are qualified as follows:
Addressing: If you have received this e-mail in error, please advise by
reply e-mail to the sender. Please also destroy the original
transmission and its contents.
Confidentiality: This e-mail may contain confidential information which
also may be legally privileged. Only the intended recipient(s) may
access, use, distribute or copy this e-mail.
Individual Views: Unless otherwise indicated, the views expressed are
those of the sender, not Justice Technology Services.
Computer Viruses: It is the recipient's responsibility to check the
e-mail and any attached files for viruses.

Normal
Re: Release 16 program loads
"I may have missed something - but this sounds like all you're asking for is
the program name in the EXEC PGM=*** statement of your batch job to be found
in the linklist. That shouldn't have changed as IDMS doesn't interfere the
STEPLIB, JOBLIB and linklist searches - and there should be no reason for
IDMS to issue a BLDL for that program.

If you're running CV mode there should be no requirement for a CDMSLIB, if
you're running local mode only the IDMS system programs need to be in
CDMSLIB. We did not have to make any JCL changes for our upgrade from 14.1
to 16.0. So perhaps there's something about your run-time environment that I
don't understand that is causing your problem.

This e-mail message and any attachments are qualified as follows:
Addressing: If you have received this e-mail in error, please advise by
reply e-mail to the sender. Please also destroy the original transmission
and its contents.
Confidentiality: This e-mail may contain confidential information which
also may be legally privileged. Only the intended recipient(s) may access,
use, distribute or copy this e-mail.
Individual Views: Unless otherwise indicated, the views expressed are those
of the sender, not Justice Technology Services.
Computer Viruses: It is the recipient's responsibility to check the e-mail
and any attached files for viruses.

As we all know, there is not now nor has there ever been a need to
include CDMSLIB in any batch job that talks to IDMS, CV or local mode.
What appears to be happening is IDMS looking at the application program
via a BLDL so it can build the appropriate environment in the user
address space. If you include CDMSLIB, IDMS will look for your programs
there. If you leave out the CDMSLIB DD cards, he looks at
STEPLIB/linklist just like it's supposed to. When included with all the
application libraries, stuff works. When not included at all, stuff
works. When included without all of the application libraries, the job
fails with the 4005.

As best I can tell, this is a change in behavior since R14.1. Back
then, the existence of CDMSLIB in the jobstream was irrelevant; it never
got used. In the R16.2 world, it appears to be functional. It would be
nice if the CA folks on the list could confirm or deny my rather heavy
suspicions.

Our final answer, of course, is to eliminate the CDMSLIB DD cards for
all batch jobstreams. In this case, I had an applications test
jobstream which (incorrectly) included the problematic DD cards and got
caught with the upgrade. Pull the DD cards from the test set and verify
that the production ones are all correct and all will be well.