ca.portal.admin

Re:Re: [IDMSVENDOR-L] Strange thing in IDMS 17.0 SP1 DCLOG

Discussion created by ca.portal.admin on May 5, 2010
are you checking for ""both"" log full msgs?

DC050001
DC050004

i believe DC050004 is spit out when the log is 100% full - this message is
NOT checked by vanilla WTOexit

i have seen a log fill up so quicly due to a dump that the DC050001 is
never issues - only the DC050004 - and the vamilla wtoexit would never
catch it




Chris Hoelscher
IDMS/DB2 Database Architect
Humana Inc
502-476-2538
choelscher@humana.com

you only need to test the programs that you want to work correctly






From:
""William M. Allen, Jr."" <archcons@ARCHCONS.COM>
To:
IDMSVENDOR-L@LISTSERV.IUASSN.COM
Date:
05/05/2010 04:29 PM
Subject:
[IDMSVENDOR-L] Strange thing in IDMS 17.0 SP1 DCLOG
Sent by:
IDMS 3rd-party providers forum <IDMSVENDOR-L@LISTSERV.IUASSN.COM>



Hello All:



I just upgraded another Client to 17.0 SP1 and we are having a few issues;
one was with TSSMAI from Top Secret and there is a fix for that from CA.



The next issue is that the CV is not spitting out the log % full message
so
what is happening is that the log is filling up and the offload job is
never
getting submitted?



The exit is fine because it is submitting the Journal archive just fine.



The Messages for the Journal and log have the same destination and OS
route
codes, I have checked all of that. I have even restored and re-received
and
applied the startup user modification with no change.



The Log was formatted before we brought the CV up using IDMS 17.0 SP1
software.



We also had an issue with easy test causing system module program checks
near RHDCUXIT with all the tool kit exits installed. We have pulled all
the
exits from RHDCUXIT and easy test works fine. We still have to work with
the
vendors on a resolution for this one.



The last issue is the submission of the log archive, I know the exit is
working and the log has filled many times, but the IDMS Region is simply
not
issuing the log % full message?



And here is another strange thing when we view the log with LOGD we see
these system module program checks from four days ago and the log has
filled
at least five times since then because we have to archive it manually.



So my question is how does IDMS issue that log message, is there some sort
of header record in the log that might be corrupted?



We can always format the log but the Client is reluctant to do that
without
an explanation of why this is happening.



William M. Allen, Jr.

ARCH Consulting Associates, Ltd.

(704) 641-0296



The information transmitted is intended only for the person or entity to
which it is addressed and may contain CONFIDENTIAL material. If you receiv=
e
this material/information in error, please contact the sender and delete or
destroy the material/information.
"
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: [IDMSVENDOR-L] Strange thing in IDMS 17.0 SP1 DCLOG
"I am using the default, provided WTOEXIT with our IDMS R17SP1 systems without issue. We had gone from linking it into the startup module, to linked stand alone module(all pre-17), and then went with the default as part of the 17 installed and it works fine. There are some options related to the exit that can be set, so you could look there. Then I guess the possibility of a rogue module laying around somewhere.

Outcomes