You may need to delete the entries of a library from the managed list, or you may need to delete an entire hash table and have CA PMO rebuild it. For instance, this may be necessary if you are doing a non-standard update to a library, or if you are doing a cross-system update but you are not using PMO/XSYS.
PMO/XSYS communicates information about the refresh to other systems. As a result, all of the entries are refreshed for a library that resides on more than one system.
You delete library entries with the following command:
F PMO {,D=data set name}
{,D=LNKLST}
{,D=ALL}
This command has the following operands:
The CA PMO keyword.
You specify this operand as follows:
For LNKLST libraries, this deletes the directory entries of the specified library and all the directory entries of the LNKLST libraries that follow in the concatenation.
Deletes directory entries for all LNKLST libraries.
This option deletes all entries from the managed list and refreshes all of CA PMO hash tables.
If the library has entries in the managed list, CA PMO responds:
PMO340I nnn MANAGED LIST ENTRIES INVALIDATED
The variable nnn represents the number of entries that were deleted. CA PMO replaces these entries after there are more BLDL/FIND requests for them.
If the specified library has hash table entries, CA PMO responds:
PMO360I NEW HASH TABLE CONSTRUCTED FOR DSN=data set name
When CA PMO deletes entries for LNKLST library members, it also deletes entries for all LNKLST libraries following it in the concatenation. (CA PMO does this for all types of LNKLST library updates, such as compresses and IEBCOPYs.) This ensures that CA PMO always uses the appropriate member to satisfy a BLDL/FIND request. For instance, assume that CA PMO manages the following concatenation of LNKLST libraries:
LNKLST Library 1=SYS1.LIB1 LNKLST Library 2=SYS1.LIB2 LNKLST Library 3=SYS1.LIB3
Suppose that a member of SYS1.LIB3 is in the managed list. If you added a different member with the same name to SYS1.LIB2 (not using IEBCOPY), and CA PMO did not delete the old member from the managed list, the new member would never be used. To avoid this situation, issue the command F PMO,D=SYS1.LIB2, causing CA PMO to delete all members from SYS1.LIB2 and SYS1.LIB3 from the managed list. If any libraries followed these in the concatenation, CA PMO would also delete entries for their members. Finally, CA PMO would delete managed list entries that were created because of the RETNF parameter.
If you use LLA with CA PMO, and you specified the parameters LLA=AUTO and OPERMSG=YES, CA PMO responds:
PMO519D LNKLST UPDATE DETECTED - SHOULD LLA BE REFRESHED (YES OR NO)? PMO522I D=data set name M=member name
If you specified the parameters LLA=AUTO and OPERMSG=NO, CA PMOresponds:
PMO520I LNKLST UPDATE DETECTED - LLA TO BE AUTOMATICALLY REFRESHED AT hh:mm:ss PMO522I D=data set name M=member name
CA PMO responds:
PMO518I SELECTIVE LLA REFRESH TO OCCUR AT hh:mm:ss: FOR LNKLST LIBRARY=data set name
If you specified the parameter LLA=WARN, CA PMO responds:
PMO521I LNKLST UPDATE DETECTED - LLA REFRESH MAY BE REQUIRED PMO522I D=data set name M=member name
The messages shown above are CA PMO> messages. The corresponding PMO/XSYS messages are PMO750I, PMO751I, PMO752I, PMO758I, and PMO759I.
|
Copyright © 2011 CA.
All rights reserved.
|
|