Load LIB expansion

shr_amar · Active User Joined: 02 May 2005 Posts: 128 Location: UK

Hi,

We need to expand load library while jobs are using the loads, Is this is possible? Basically we need to add some new loads to load lib but that doesn't has storage and we expand it because online region are using some loads.

so do we have any way to expand the load while loads are used or only option is to stop the jon using loads and then expand?

enrico-sorichetti · Posted: Thu Apr 10, 2014 6:38 pm

ok for the language barrier...
but what You wrote is just unintelligible ( AKA clear as mud )

Nic Clouston · Posted: Thu Apr 10, 2014 7:13 pm

If the LOADLIB is allocated you will have to wait until it is free but you can create the new, larger, one ready to rename as soon as current one becomes free.

dick scherrer · Posted: Thu Apr 10, 2014 7:14 pm

Hello,

Stop the process(es) using the load libs.
Make a backup if there is not a current backup.
Expand.

Restart what was stopped.

Robert Sample · Posted: Thu Apr 10, 2014 7:58 pm

If the load libraries are used by online systems, you REALLY need to bring it (them) down before expanding the load library.

Rohit Umarjikar · Posted: Fri Apr 11, 2014 6:12 am

steve-myers · Posted: Fri Apr 11, 2014 7:02 am

In general, Rohit Umarjikar is correct. To some extent, it depends on what you mean by "expand." I recognize two meanings -

The library adds extents.
An entirely new library with more space, and possibly a larger directory.

The library adds extents

A job that causes the library to add an extent can be run while other jobs are using the library, but the other jobs cannot use any members that overflow into the new extent. At a minimum, this will cause I/O errors. It may be possible to "compress" the library while the other jobs are running, but it may cause problems with the other jobs.

An entirely new library with more space, and possibly a larger directory

The new library can be allocated using a different data set name, possibly on a different volume, and the existing library can safely - most of the time - be copied to the new library. But you cannot delete the existing library and rename the new library to the old library name until all the jobs using the original library have completed.