ca.portal.admin

Re: DC205011 No Journals are AVAILABLE

Discussion created by ca.portal.admin on May 25, 2005
Do not have an exit but you have several alternatives. 1. Would be to
increase the size of the journals 2. Would be to increase the number of
journals 3. Would be to put the journals to a disk pool setup for them
exclusively.

There are advantages and disadvantages to each solution but the exit would
not be a solution at all for me.

I am assume that you have a special job class for the tape offload jobs (
journal jobs) so that there is no delay in starting the offloads and the
offload jobs should be set a notch above other batch jobs as well if
possible.

Dick

Richard C Borman/GIS/CSC
CSC/GIS Idms System Support
9305 Lightwave Ave
San Diego, Ca 92193-9011
office 858-573-3265
rborman@csc.com



----------------------------------------------------------------------------------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------





""Klan, Robert
(Corporate)"" To: IDMS-L@LISTSERV.IUASSN.COM
<Robert.Klan cc:
@CORPORATE.GE.CO Subject: DC205011 No Journals are AVAILABLE
M>
Sent by: IDMS
Public
Discussion Forum
<IDMS-L


05/25/2005 05:17
AM
Please respond
to IDMS Public
Discussion Forum






Has anyone come up with an automated or exit solution for those times in
which a run unit fills up the journals which requires a manual cancel run
unit to resolve?

Limits is active, however they are set high for legitimate run units.

SYSLOG Example.....

+IDMS DC205013 All Disk Journals are UNAVAILABLE; Reasons below.
+IDMS DC205004 Disk Journal is OFFLOADING/CONDENSING. Waiting for J1JRNL
+IDMS DC205014 ARCHIVE JOURNAL NOT yet RUN against full Journal J2JRNL
+IDMS DC205014 ARCHIVE JOURNAL NOT yet RUN against full Journal J3JRNL
+IDMS DC205011 NO Journals are AVAILABLE.   IDMS Waiting

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








Normal

Normal
Re: DC205011 No Journals are AVAILABLE
"Hey Bob, the wto exit seems like the good place to intercept the all
journals full message, and you can then set a flag in a universally
accessible place that your exit can interrogate. A long time ago I
coupled the limits exit with the sos flag and only blew limit excessors
away if the system was sos. Seems to me that a similar design might
meet your objective. Invoke a limit exit who looks at the no journals
available flag set by theh wto exit, and then blow the limit excessor
away.

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: [IDMSVENDOR-L] DC205011 No Journals are AVAILABLE
"do you have pre-alert or other external monitor?

if you do, or can otherwise detect that journals are full, as soon as
total-1 journals are full, kick off a job to cancel the oldest (or all)
application update run units ...

Chris Hoelscher
IDMS & DB2 Database Administrator
Humana Inc
502-580-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.

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








Normal

Normal
Re: DC205011 No Journals are AVAILABLE
"A sample Exit 20 I coded & tested but never implemented. . .

One of the cruelest ironies of the world-in-which-we-live is that DBAs
are smart enough to run the world, but powerless to do so. In which
case, it may be that a User Exit is your best option.

No warrantee or guarantee offered along with this software from anybody,
but I am happy to discuss endlessly. . .

***********************************************************************
* Cloned from sample exit:
* THIS SAMPLE USER EXIT 20 HANDLES RESOURCE LIMIT OVERFLOWS. *
* IT IS INVOKED BY RHDCLIMT WHENEVER A LIMIT IS FOUND TO BE *
* EXCEEDED. THE CONDITIONS HANDLED ARE AS FOLLOWS: *
* *
* Each limit is checked,
* IF exceeded, then determine whether dialog or not
* IF DIALOG, then search exclude list.
* IF NOT DIALOG, then fail.
* IF DIALOG Name on ""exclude"" list, then double call limit.
* IF NOT EXCLUDed, then FAIL.
***********************************************************************
UX20 TITLE 'RHDCUX20 -- EXAMPLE RESOURCE LIMIT EXIT'
* RHDCUX20 EP=UX20EP1
EJECT
#MOPT CSECT=RHDCUX20,ENV=SYS
COPY #CSADS .
COPY #LTEDS .
COPY #RLBDS .
COPY #TCEDS .
COPY #RCADS .
COPY #TSTDS .
#OTBDS TYPE=DSECT,EXPAND=ONLINE
***********************************************************************
* WORK AREA DSECT FOR LIMT ROUTINE. *
***********************************************************************
WORKD DSECT
SYSPLIST DS 12A
DS 0F
WORKDL EQU (*-WORKD+3)/4 LENGTH IN WORDS.
SPACE
XIT DSECT
XIT00 DS H FILLER
XITCD DS 0H RESOURCE CODE
DS X (RESERVED AT THE MOMENT)
XITSTG #FLAG X'01' CHECK STORAGE LIMIT
XITDBIO #FLAG X'08' CHECK DBIO LIMIT
XITLOCK #FLAG X'10' CHECK DB LOCKING LIMIT
XITCALL #FLAG X'20' CHECK SERVICE CALL LIMIT
XITFLG1 DS X
XITOF DS F LIMIT OFFSET IN TASK RLB
xitdslen equ *-xit
EJECT
***********************************************************************
* RHDCUX20 - USER EXIT TO HANDLE RESOURCE LIMITS
*
* ON ENTRY R1 WILL POINT TO A TWO WORD PLIST, FORMATTED *
* AS FOLLOWS: *
* +0 FULLWORD: EXIT # (20 IN THIS CASE) *
* +4 ADDRESS: PTR TO PLIST CREATED BY MODULE *
* THAT INVOKED THE EXIT *
***********************************************************************
RHDCUX20 CSECT
USING CSA,R10
USING TCE,R9
UX20EP1 #START
SPACE
*
* LOCATE PARAMETERS IN PLIST
*
SPACE
LR R2,R1 SAVE PARM REGISTER
#GETSTK =WORKDL,CLEAR=YES GET SOME WORK SPACE
USING WORKD,R11
L R3,4(R2) GET AT PARMS PASSED BY LIMTEP1
SPACE
*
* ACTUAL PROCESSING BEGINS HERE
* only checking service calls, now...
*
SPACE
USING XIT,R3 BASE THE PLIST AREA
#TEST XITCALL,On=chkbad ? SERVICE CALL LIMIT EXCEEDED
B XITok
* #TEST TCEERUS,on=xitok ? ignore erus
* #TEST XITSTG,On=xitok ? STORAGE LIMIT EXCEEDED
* #TEST XITdbio,On=xitok ? dbio LIMIT EXCEEDED
* #TEST XITlock,On=xitok ? lock LIMIT EXCEEDED
* B XITok
*--------------------------------------------------------------
* chase task rle chain in reverse, look for OTB, find dia.name
* check list of known baddies - abend them, pass the rest
*--------------------------------------------------------------
chkbad ds 0h
l r5,tcemrlea+4 get last rle
using rle,r5
loop ds 0h
l r7,rlercea get that rce
using rce,r7
l r7,rceraddr get that resource
la r7,8(r7) skip over prefix
using otb,r7
clc =c'OTB*',otbid an OTB?
be chklist yes, go chk dia.name
l r5,rlepria get prior rle
c r5,tcemrlea back to tce?
be xitfail not a dia., get out
B loop try next
chklist ds 0h
clc =c'TESTLIMT',otbdnam chk dia.name
be xitxtnd if hit, extend
clc =c'NEXTPGM ',otbdnam chk dia.name
be xitxtnd if hit, extend
*
b xitfail fail by default
*
xitok SR R15,R15 CLEAR REGISTER - OK
XIT099 DS 0H
#RTN
#BALI .
WTOM1 DC AL2(L'WTOM1TX)
WTOM1TX Ds CL70
ORG WTOM1TX
DC C'RHDCUX20: '
WTOpgm DS CL8
Dc C' extended to '
WTOM1lmt DS CL8
WTOM1TXT Dc C' service calls '
*
xitxtnd ds 0h
l r5,tcerlba get rlb
using rlb,r5
l r6,xitof offset of exceeded limit in rlb
ar r6,r5
l r4,0(r6)
sla r4,1 double limit
st r4,0(r6)
#enq rscid='LimitX',rgsv=(r2-r8) thread thru here. . .
xr r0,r0
mvc wtopgm,otbdnam set dialog name in wto msg
cvd r4,dbl
oi dbl+7,x'0f'
unpk wtom1lmt(8),dbl
* #wtl instead?
wto text=(wtom1,d) write wto
#deq rscid='LimitX',rgsv=(r2-r8)
#snap area=((r5),rlbdslen),title=' rhdcux20 rlb',rgsv=(r2-r8)
b xitok
dbl ds d
XITfail DS 0H ABEND LIMIT OVERFLOWS
LA R15,4
B XIT099
DROP R11,R10,R9,R3
END

Outcomes