ca.portal.admin

Re:Re: [IDMSVENDOR-L] Diagnostics and Symbol tables - another

Discussion created by ca.portal.admin on Jan 31, 2008
question

the PROG-xx information is correct ONLY if the dialog was generated in
production - if a dialog load module was copied from ""somehwhere else"" -
there will be no correlation between the dictionary contents and the
load module contents


Chris Hoelscher
Senior IDMS & DB2 Database Administrator Humana Inc
502-476-2538
choelscher@humana.com



The information transmitted is intended only for the person or entity to
which it is addressed and may contain CONFIDENTIAL material. If you
receive this material/information in error, please contact the sender
and delete or destroy the material/information.


The information transmitted is intended only for the person or entity to
which it is addressed and may contain CONFIDENTIAL material. If you
receive this material/information in error, please contact the sender
and delete or destroy the material/information.
"
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] Diagnostics and Symbol tables - another question
"Here are the error messages. You were close, Jim.

DC466004 V27 Unable to display source. Error status= 1494

DB347011 V27 T488706 DBNAME HRQDICT INVALID - BINDING SUBSCHEMA IS
IDMSNWKA PROGRAM USGALOD
DC027007 V27 T488706 TASK:ADS2 PROG:USGALOD ABENDED WITH CODE 1494

Just to clarify: It was never our intention (and not Dan's either, I
suspect) for this to work in production. I think we all agree that it
should be turned off in production, for performance reasons. The
question is, how do you verify that both symbol table and diagnostics
are turned off in production? Since they are normally used together,
maybe checking for the symbol table alone is good enough.

Outcomes