ca.portal.admin

Re: 4407/0371 errors

Discussion created by ca.portal.admin on Jul 29, 2007
Wayne -

Your post stirs some bad memories of queue problems I had at the turn of
the
century.
We haven't had them for 7 years now, but when we did, it was truly
awful.

Have you ever run a DBAN against the queue area after this happens?
If not, could you humor me and run one?

Also, try doubling the number of RUAL run-units you have defined for
QUEUE
and see if that possibly makes any difference.

Thanks.
Jon Gocher

----- Original Message -----
From: ""Doneker, John W (US SSA)"" <John.Doneker@BAESYSTEMS.COM>
To: <IDMS-L@LISTSERV.IUASSN.COM>
Sent: Monday, July 23, 2007 11:38 AM
Subject: 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
IDMS COBOL question
"Is there any IDMS-related reason that an IDMS batch COBOL LE program
needs to be AMODE(24) or RMODE(24)?

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS COBOL question
"Kay,

My notes on AMODE/RMODE from 1998 when I worked at Fidelity spcifically
note that 24,24 used to be a problem for IDMS, but have been resolved as
of then.

Tim Gortner


----- Original message -----
From: ""Rozeboom, Kay [DAS]"" <KAY.ROZEBOOM@IOWA.GOV>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Mon, 30 Jul 2007 09:44:05 -0500
Subject: IDMS COBOL question

Is there any IDMS-related reason that an IDMS batch COBOL LE program
needs to be AMODE(24) or RMODE(24)?

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: IDMS COBOL question
"For IDMS there's no problem for AM(31) and rm(31)

Look on your loadlib what the characteristics of module IDMS are .
probably AM(ANY) and RM(24).

IDMS will accept AM(24) and am(31)

The program IDMS will be loaded below the line RM(24).

Regards

Peter van de Ven
-----Original Message-----
From: IDMS Public Discussion Forum [mailTo:IDMS-L@LISTSERV.IUASSN.COM]
On
Behalf Of Tim Gortner
Sent: Monday, July 30, 2007 17:00
To: IDMS-L@LISTSERV.IUASSN.COM
Subject: Re: IDMS COBOL question

Kay,

My notes on AMODE/RMODE from 1998 when I worked at Fidelity
spcifically
note that 24,24 used to be a problem for IDMS, but have been resolved
as
of then.

Tim Gortner


----- Original message -----
From: ""Rozeboom, Kay [DAS]"" <KAY.ROZEBOOM@IOWA.GOV>
To: IDMS-L@LISTSERV.IUASSN.COM
Date: Mon, 30 Jul 2007 09:44:05 -0500
Subject: IDMS COBOL question

Is there any IDMS-related reason that an IDMS batch COBOL LE program
needs to be AMODE(24) or RMODE(24)?

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Converting Mainframe files to PDF
"Hi,



We are looking for products that will take a file on the Mainframe and
convert it to a PDF file. We are using XMITIP and this includes TXT2PDF.
There must be other products out there?



Thanks



Chris Wood

Alberta Department of Energy

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








Normal

Normal
Re: Optional APAR bits
"Bit 18 is no longer used. It has been withdrawn by CA.

Outcomes