ca.portal.admin

Re: Test CV - Message at Startup - Just After the CV is

Discussion created by ca.portal.admin on Jul 20, 2007
Available

Mike this is the message you should have received

I would suggest that you look at your size parameter on your execute
statement, and do the calculations using the size of your partition and
make sure there is enough room. just a guess but worth a try.

Bill Gaddy
Technical Support
Memphis Light, Gas & Water
901-729-8544
Mike Semega <Mike_Semega@PROGRESSIVE.COM> 7/20/2007 7:28 AM >>>
Try message MESSAGE NAME IS DC055007



""Collins, John H."" <JOHN.H.COLLINS@SAIC.COM>
Sent by: IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM>
07/19/2007 06:43 PM
Please respond to
IDMS Public Discussion Forum <IDMS-L@LISTSERV.IUASSN.COM>


To
IDMS-L@LISTSERV.IUASSN.COM
cc

Subject
Test CV - Message at Startup - Just After the CV is Available






This below message is displayed at startup of our test CV, after
multiple IPLs. Late this morning the CPU crashed, bringing down all
LPARs. The problem has not been determined. The below message appeared
immediately after the ENTER NEXT TASK CODE ? message. It does not have
an associated DC message or any other identifying message number. I
contacted CA tech support, and the IDMS modules were scanned for this
message; however, there was not a hit. Also, we have tried scanning
Google and the IBM Message and Codes manuals. No hits have been
returned. CA tech support believes this message is coming from the
operating system; however, our system programmer believes it is not.



If anyone has any ideas how the message is initiated, please let me
know. Our CPU has crashed again, the cause is still unknown.







BUFFER EYECATCHER MISSING POSSIBLE STORAGE CORRUPTION



Regards,



John Collins

SAIC

858-826-3463
This e-mail and any attachments represent the views and opinions of only
the sender and are not necessarily those of Memphis Light, Gas & Water
Division,and no such inference should be made.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
DC-COBOL Abends with z/OS 1.8 RSU 0706.
"FYI,

We were getting T03C ABENDS in CA-IDMS release 16.0 SP4 on any DC-COBOL
program with Z/OS 1.8 RSU 0706. APAR QO88752 fixed the problem.

Steve Harmeson
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
4407/0371 errors
"Hi Listers:

I do not remember if I reported this to the List before or
not. I thought it wouldn't hurt to do so even though this issue is in
Level2.

Again, Level 2 is looking into this but I thought I'd ""throw it out
there"" and maybe someone else has had this problem.



We are having problems with queue run units. Every couple of weeks,
usually when there is a 4407 error status the CV starts filling up the

log with the following RHDCRUAL/0371 error messages over and over again
after a 4407 has been displayed.



IDMS DC799999 V220 DATA BASE ERROR 4407 OCCURRED

RECORD INVENTORY-BIN

AREA CAS-INV-AREA

ERROR SET PLANT-INVEN-BIN

ERROR RECORD INVENTORY-BIN

ERROR AREA CAS-BOM-AREA

PROGRAM NAME

DML SEQUENCE

DB NAME

IDMS DC027007 V220 T3274 TASK:ADS2 PROG:ADSOMAIN ABENDED

IDMS DC076010 V220 T3275 Program.....: RHDCRUAL

IDMS DC076011 V220 T3275 Subschema...: IDMSNWK7

IDMS DC076013 V220 T3275 Dbname......: SYSTEM

IDMS DC076014 V220 T3275 Error Status: 0371

IDMS DC076016 V220 T3275 Direct DBkey: 00B5AC05

IDMS DC076018 V220 T3275 Last Area...: DDLDCRUN

IDMS DC076021 V220 T3275 Error Area..: DDLDCRUN

IDMS DC245011 V220 T3275 TASK:*FACTOTUM*; QUEUE REQUEST

IDMS DC027007 V220 T3275 TASK:*FACTOTUM* PROG:*SYSTEM*

IDMS DC076010 V220 T3277 Program.....: RHDCRUAL

IDMS DC076011 V220 T3277 Subschema...: IDMSNWK7

IDMS DC076013 V220 T3277 Dbname......: SYSTEM

IDMS DC076014 V220 T3277 Error Status: 0371

IDMS DC076016 V220 T3277 Direct DBkey: 00B5AC05

IDMS DC076018 V220 T3277 Last Area...: DDLDCRUN

IDMS DC076021 V220 T3277 Error Area..: DDLDCRUN

IDMS DC245011 V220 T3277 TASK:*FACTOTUM*; QUEUE REQUEST

IDMS DC027007 V220 T3277 TASK:*FACTOTUM* PROG:*SYSTEM*

These 0371's keep repeating itself, and you cannot get into CV and of
course logs keep spinning out of control.

I end up hard canceling CV and warmstarting until the next time this
happens. Again, Level2 is looking into this but

I was curious if anybody else had this type of problem? We are on IDMS
15.0 SP5.



Thanks in advance.



J. Wayne Doneker

BAE Systems

York Pa.,

717 225 8109

John.Doneker@baesystems.com


"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: CWADISP in CICS
"We start at cwadisp of 40 and each cint and cicsopts modules must use
the same cwadisp for each cv. The next is 4 bytes higher so our next
modules would use cwadisp of 44. I not sue what uses 0 thru 39 but
something does.

HTH
Steve Harmeson

Outcomes