Re: ALWSAV and Virtual Optical in library mode

I was having problems where the catalog entries were not being loaded
properly after an IPL I had to write a CL which uses a TAATOOL command to
dump a list of the catalog entries to an outfile. I then do a LODIMGCLGE
on each one. I could never prove to IBM the entries weren't loading. I
wasn't initially unloading them prior to the IPL. After I implemented the
unload, they started loading properly. IBM still won't agree that anything
wasn't working. SInce the catalog entries will only be unloaded if the
system is taking down using my routine, I do the LOGIMGCLGE everytime it
starts (I actually do it as a prestart job in our Imaging subsystem. I
restart the subsystem daily so I LODIMGCLGE daily),


Gord



On Tue, Aug 18, 2015 at 12:14 PM, Jim Franz <franz9000@xxxxxxxxx> wrote:

Gord,

What we save was the directory and catalogs saved, but not the catalog
entries!
I've just gone back a see that in our executing code for the IPL, we are
not unloading the images, and letting the OS do it... That could be our
issue.
Jim


On Tue, Aug 18, 2015 at 11:44 AM, Gord Hutchinson <

gordm1@xxxxxxxxxxxxxxx>

wrote:

Jim,

I've checked our development and production catalogs (which we also use

in

library mode). On each system they show 'Can be saved' as Yes in

WRKLNK

'Display Attributes'. The catalogs are currently loaded.

I've been backing these up to tape in development. BRMS is showing the
catalogs as being backed up. I'm having a DSPTAP done to confirm. I
haven't yet backed the completed volumes to tape on production but I

have

used the virtual optical replication utility to save them and load them

on

our HA system.

I unload the catalogs before taking the system down for our weekly

backup

and IPL.


Gord

On Tue, Aug 18, 2015 at 9:46 AM, Jim Franz <franz9000@xxxxxxxxx>

wrote:

We have a number of Virtual Optical Catalogs (in library mode) that

are

static and we do not save daily. Four catalogs are changing daily.

When the catalogs are loaded, the ALWSAV attribute is flipped to no

(by

IBM), and when later unloaded the attribute is back to yes (by IBM).

However, we have noticed when unloaded prior to an IPL (or SAVE 21) -

after

the ipl, and catalogs loaded then unloaded for next nightly save, the
catalog entries are set to no (when they had been set to yes prior to

ipl)

Has anyone else (who is saving virtual optical) had this issue? We

have

talked to IBM before about this, but the issue is not resolved.
Since no last save date in IFS attributes, we are having to dump

DSPTAP

*SAVRST to verify.
Not finding any apparent ptf.
V7R1

Jim Franz
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
Gord Hutchinson
TST Overland Express
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
Gord Hutchinson
TST Overland Express
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.