ca.portal.admin

Re: CA-1 and Unload/Reload

Discussion created by ca.portal.admin on Jan 2, 2007
Hello All:

Here is where we stand. We got systems to give us our own work packs
outside of SMS and we were able to complete the U/R using this new DASD
as a one step reload operation reusing the work files.

The problem is not with VSE, DYNAM/T, VIO or DD Statements, the
problem is simply the tape management software CA-1. Once a tape is
written on it cannot be written on again in the same job step because
CA-1 will only allow this in very special situations, for example
DISP=MOD, or creating a second or subsequent file on the same tape.

In most if not all CA-1 shops there is a default retention assigned if
one is not assigned by any other means, in some shops that default is 1
day only, so if you wrote on the tape an hour ago, CA-1 will not let
you write on it again for at least 24 Hours.

I googled the CA-1 error message (IECTMS3 with code 64) and found some
interesting articles, one article said to use temporary data set names
(&&SYS005) on the work tapes, another said to use a LABEL=RETPD=0.

The next time that I have to do a large Unload Reload I will use both, a
temporary data set name and a LABEL=RETPD=0. Of course I will test this
out before we attempt a very large Unload and Reload.

I liked Tommy Peterson's suggestion of a stepped Unload and reload, but
then I would have to put all the JCL together for each and every step.

I really like the single step reload with SORTEXIT and REUSE WORK
FILES.

I know when using a single step reload that restarting is an issue but I
have not had any fail on me in a very long time, in fact, I think this
may be the first one to fail?

Thanks to everyone who responded, thanks for your time and support and
Happy New Year to everyone.

Bill Allen

In a message dated 1/2/2007 7:28:00 A.M. Eastern Standard Time,
TommyPetersen@NEWYORKLIFE.COM writes:

I had the same problem. Temporary data sets appear to work differently
for tape and DASD.
There are two solutions.
1. Run a stepped reload in separate jobs.
2. Don't use the REUSE parameter, you will however temporarily use
more tapes.
For small unload/reloads I like the second solution. For long running
reloads I prefer number 1 as it allows for restarts as long as the data
sets are cataloged.

Tommy Petersen





Bill Allen
<ARCHCONB@AOL.COM
To
Sent by: IDMS IDMS-L@LISTSERV.IUASSN.COM
Public Discussion cc
Forum
<IDMS-L@LISTSERV. Subject
IUASSN.COM> CA-1 and Unload/Reload


12/31/2006 07:44
PM


Please respond to
IDMS Public
Discussion Forum
<IDMS-L@LISTSERV.
IUASSN.COM>






Hello All:

When performing a very large unload and reload we are having to use
work tapes as DASD in unavailable. We are also using sort exit and
reuse work files but CA-1 will not allow this to happen when it tries
to write on the work tape a second time.

Is anyone aware of a work around for this situation?

Bill Allen
"
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] CA-1 and Unload/Reload
"In a few cases, yes. Hahaha yourself. We also run index rebuilds in
stepped mode. The CULPRIT and index rebuilds use procs though.

Outcomes