Comments on: CL Back up job failing

By: guy553

guy553 — Tue, 01 Nov 2011 09:36:04 +0000

Excellent, thanks for all your help !! I expect you’ll see me back quite often now.

Right where is that programmer of mine hiding, Singapore is not far enough away.

Thanks everyone.

By: charliebrowne

charliebrowne — Mon, 31 Oct 2011 20:15:10 +0000

To answer your 2nd question.
Since this is all in one CL program, the 2nd SAVLIB will not start to execute until the 1st one is completed. There is no need to do anything with allocation of the tape drive in between the two SAVLIB commands snce this job has it allocated until it finishes or does the DLCOBJ.

By: tomliotta

tomliotta — Mon, 31 Oct 2011 19:19:28 +0000

Sorry for needing an idiots guide but I just don’t know Every one of us started at some point. Wait until you do something really dumb. You'll know it when it happens, and you won't be posting about it in an on-line forum. You'll just let it fade quietly in your distant memories. (There is no point in asking how I know that.) Until then, forums are where basic questions get answered. Tom

By: guy553

guy553 — Mon, 31 Oct 2011 10:09:54 +0000

OK so just so I have this right, with the additional loop in as described, the program will insure it have the tape drive and keep it until the program is finished. So when the first SAVLIB command is executed it will be able to access the tape drive and save the library. My question is, does the second SAVLIB wait until the first SAVLIB to complete before executing or does it try and allocate the tape drive while it is still in use with the first SAVLIB.

Sorry for needing an idiots guide but I just don’t know and apparently there are no stupid questions. I just need my backups working.

Guy

By: tomliotta

tomliotta — Sat, 29 Oct 2011 01:27:59 +0000

One minor programming note — line 3400 was never going to do anything.

The MONMSG at 2800 occurs in the source before the executable statements. It becomes a ‘global MONMSG’ that will apply to every executable statement in the program.

The MONMSG at 3400 was down in the executable area, so it becomes associated with whatever executable command preceded it. In this case, that was a CHGVAR; and a CHGVAR shouldn’t ever run into a CPF1002 exception.

But note that CharlieBrowne’s code also uses MONMSG and checks for CPF1002. The extended help for the ALCOBJ command shows that CPF1002 is a potential exception from ALCOBJ.

Tom

By: charliebrowne

charliebrowne — Fri, 28 Oct 2011 18:30:57 +0000

The code allocates the tape before the 1st save starts and then keeps it allocated until the last save is done.

By: guy553

guy553 — Fri, 28 Oct 2011 17:44:33 +0000

I’m guessing this will make sure tape is ready for the first save but won’t the second find the tape in use?