ca.portal.admin

Re:Re: 2 PDE copies in memory

Discussion created by ca.portal.admin on Aug 31, 2007
Last entry. Varying memory in a PDE program name (which is part of the
index) can cause lots of problems. Program not found, duplicate entries,

Cobol programs that are no longer defined as cobol etc.
So please do not vary a program name.
As Bill Allen said, it will definitely cause index corruption.
That being said, if you REALLY had to vary the name - make sure it fits
alphabetically into the index..
Ed McKinney
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] 2 PDE copies in memory
"But, cobol and assembler programs are not loaded using a null pde,
correct? they are either sysgenned or dcmt v dynamiced. Also,
technically, I dont understand why varying memory on a pde corrupts pde
searches when the pde's are indexed. If the pde search were binary,
then I understand that other pde's could be compromised in the search.
But an index search will find the index entry, go to the pde and then
loader decides the name in the pde doesn't match the search criteria and
return a not found condition. Exactly what the purpose was. No
question in my mind that this should not be a lightly taken approach,
but if a production system must be supported and the cv cycling produces
an expensive outage that the company is paying for, and CA can't fix the
corrupted pde problem because it's not recreatable, then what else can a
technician do?

Lutz Petzold

This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: 2 PDE copies in memory
"Oh well, what the heck.

Because you had inadvertently dynamically created a PDE but forgot to say
COBOL, so you didn't get the HLL (high level language) extension built and
there's no way to make the PDE go away before the next recycle so in
desperation you change the name in the PDE so you can try the DCMT V DYN PDE
statement again?

Do NOT try this at home.

* DQC

Outcomes