CA PDSMAN PDS Library Management 7.7 1 CA RS 1411 Service List Description Type 7.7 RO73184 FCO415A MESSAGE WHEN PROCESSING PDSFAST DIREDIT PTF RO73404 ENHANCE PDSMAN LAST REFERENCE DATE RECORDING PTF RO74545 PDSM00-44 MESSAGE INCORRECTLY ISSUED PTF The CA RS 1411 service count for this release is 3
CA PDSMAN PDS Library Management 2 CA RS 1411 Service List for CPDS770 FMID Service Description Type CPDS770 RO73184 FCO415A MESSAGE WHEN PROCESSING PDSFAST DIREDIT PTF RO73404 ENHANCE PDSMAN LAST REFERENCE DATE RECORDING PTF RO74545 PDSM00-44 MESSAGE INCORRECTLY ISSUED PTF The CA RS 1411 service count for this FMID is 3
CA PDSMAN PDS Library Management 7.7 3 CA RS 1411 - PTF RO73184 7.7 RO73184 RO73184 M.C.S. ENTRIES = ++PTF (RO73184) FCO415A MESSAGE WHEN PROCESSING PDSFAST DIREDIT PROBLEM DESCRIPTION: FastCopy issues message FCO415A with reason: EDITDIR REQUIRES RENAME/DELETE/RETAIN STATEMENTS if no EDITDIR rename, delete, or retain statements are specified. This is working as designed for FastCopy, but competing product PDSFAST (SEA) does not require any additional statements and gives return code 0. This fix modifies FastCopy to operate the same as PDSFAST when processing the DIREDIT (PDSFAST's syntax for EDITDIR) control statement. The behavior is unchanged when processing the EDITDIR control statement and the FCO415A message will be issued. SYMPTOMS: FastCopy issues message FCO415A with reason EDITDIR REQUIRES RENAME/DELETE/RETAIN STATEMENTS if no rename, delete, or retain statements are supplied to the PDSFAST DIREDIT control statement. IMPACT: Impact is limited to the FastCopy EDITDIR facility. CIRCUMVENTION: None. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 Star Problem(s): PDSM 1011 Copyright (C) 2014 CA. All rights reserved. R00152-PDS770-SP1 DESC(FCO415A MESSAGE WHEN PROCESSING PDSFAST DIREDIT). ++VER (Z038) FMID (CPDS770) PRE ( RO18637 RO24163 RO25866 RO36320 RO37159 RO40737 RO43636 RO44914 RO45963 RO46743 RO52466 RO52549 RO58121 RO62179 RO68088 ) SUP ( AR58121 RO38262 RO44646 RO57158 RO60050 TR38262 TR44646 TR57158 TR60050 TR73184 )
CA PDSMAN PDS Library Management 7.7 4 CA RS 1411 - PTF RO73404 7.7 RO73404 RO73404 M.C.S. ENTRIES = ++PTF (RO73404) ENHANCE PDSMAN LAST REFERENCE DATE RECORDING PROBLEM DESCRIPTION: The PDSMAN Last Reference Date Recording facility allows users to identify inactive PDS and PDSE library members by recording the date on which a member was last referenced. When the last reference date is recorded for a data (nonprogram object) PDSE library, the z/os operating system requires the accessing user to have update authority for the library. This can cause operational issues and in some cases require a choice between granting all users to update authority or not using PDSMAN Last Reference Date Recording for those PDSE libraries. Note: Throughout this description, the term PDSE refers to "data" PDSE libraries that do not contain executable modules. PDSMAN records last reference dates for executable PDSE modules (known as program objects) using a different method. This fix addresses the operational issues caused by this z/os requirement by allowing last reference dates for PDSE members to be recorded by the PDSMAN address space instead of by the accessing user. With this fix, only the PDSMAN address space needs have update authority to the PDSE libraries. This fix also introduces the ability to issue a message when the last reference date for a PDS or PDSE member is successfully recorded. --------------------------------------------------------------- Processing Description A Last Reference Date Recording request is queued to the PDSMAN address space when all of the following are true: * Last Reference Date Recording is enabled for the member ($ACCESS REF=Y) * Last Reference Date Recording needs to be performed (the first access for a member each day) * The member resides in a PDSE library * The accessing user does not have authority to update the library. A new PDSMAN subtask, the Last Reference Date Recording subtask (PDSMLRDR), wakes up at regular intervals to process the queued requests. The PDSMLRDR subtask runs within the PDSMAN address space and is normally started automatically when PDSMAN is started. Note that there may be a slight delay (generally less than 15 seconds) in actually recording the last reference date because the process is being performed asynchronously. PDSMAN performs the enhanced recording process automatically. You do not need to make any changes to your PDSMAN environment or rules. However, you must ensure that the PDSMAN address space has authority to update the PDSE libraries into which it is recording the last reference dates. See the section "Security System Considerations" for additional information. If you have previously chosen to disable (or not enable) Last Reference Date Recording for PDSE libraries due to these authorization considerations you should now reevaluate that decision and enable recording as desired. --------------------------------------------------------------- Security System Considerations The PDSMAN address space must have update authority to all PDSE libraries for which last reference date recording is being performed. You can grant this authority to the PDSMAN address space or you can further limit update authority to only the PDSMLRDT program (when running in the PDSMAN address space) that is used to record the last reference dates. The operating system requires you to completely stop and
CA PDSMAN PDS Library Management 7.7 5 CA RS 1411 - PTF RO73404 restart PDSMAN to activate the new security rules granting the necessary access. To minimize the number of times you must stop and restart PDSMAN, we suggest that you grant update authority to all libraries at one time instead of making multiple changes to the security rules. ---------------------------------------------------------------- Controlling the Last Reference Date Recording (PDSMLRDR) Subtask The PDSMLRDR subtask is controlled using commands issued to the PDSMAN address space. You issue these commands by entering: F PDSMAN,<command> To an operator console where PDSMAN is the name of the PDSMAN address space started task and <command> is one of the following: * STARTLRDR Start an inactive PDSMLRDR subtask * STOPLRDR Stop an active PDSMLRDR subtask * NEWLRDR Stop (if necessary) and then restart the PDSMLRDR subtask * LRDRSTATUS Show the status of the PDSMLRDR subtask * LRDRDETAIL Show detailed information about the PDSMLRDR subtask * LRDRPERF Show performance information for the PDSMLRDR subtask Refer to the chapter "Address Space Commands" in the PDSMAN Administrator Guide for a description of how similar commands are used with other PDSMAN subtasks. By default, the PDSMLRDR subtask is automatically started when PDSMAN is initialized. You can suppress the automatic startup of the subtask by starting PDSMAN with a execution parameter of NOLRDR. For example: S PDSMAN,PRM='NOLRDR' This parameter is not intended for normal use. Generally, you should allow the subtask to start automatically with the rest of PDSMAN. Note: PDSMLRDR is not automatically started if you are not licensed for PDSMAN feature "D" (LMP code F3). ---------------------------------------------------------------- Queuing Considerations Once the PDSMLRDR subtask is activated, Last Reference Date Recording requests will continue to be queued even if the subtask subsequently becomes inactive. The request queues have a maximum size of 40,000 entries and PDSMAN issues PDSMLRDR-03 messages when request queue usage reaches 50, 80, 90, 95 and 100 percent. If the PDSMLRDR-03 message is issued with a status other than "Notify", check the status of the PDSMLRDR subtask by issuing the LRDRSTATUS command and start the subtask using STARTLRDR if it is not active. ---------------------------------------------------------------- Recording Considerations The PDSMLRDR subtask must be able to allocate the library into which a last reference date is to be recorded. This allocation is performed using DISP=SHR. If the library is allocated to another task using DISP=OLD, the recording is not performed. PDSMLRDR issues PDSMLRDR-05 and PDSMLRDR-06 messages indicating the library could not be allocated. ---------------------------------------------------------------- Issuing Messages for Successful Updates This fix adds the ability to have PDSMAN issue a PDSMLRDR-02 message when the last reference date is successfully recorded for members of PDS or PDSE libraries. You control the PDSMLRDR- 02 message by specifying the new LRDRMSG parameter on a matching $ACCESS control statement. The following settings are valid for the LRDRMSG parameter: LRDRMSG=N Do not issue the message (default). LRDRMSG=W Issue the message to the operator console using
CA PDSMAN PDS Library Management 7.7 6 CA RS 1411 - PTF RO73404 WTO. LRDRMSG=L Issue the message to the system log. The messages are displayed by the accessing user task or by the PDSMAN address space, depending on which performs the last reference date recording. Important Note: The PDSMLRDR-02 message is issued once per day for each member that is accessed and has its last reference date recorded. Be cautious when setting LRDRMSG=W that you do not overload your console with messages due to high access activity. --------------------------------------------------------------- Messages issued by PDSMLRDR Last Reference Date Recording The following new messages can be produced during Last Reference Date Recording: PDSMLRDR-01 PDSMAN Last Reference Date Recording <status> This message reports the status of the PDSMAN Last Reference Date Recording environment. <status> The Last Reference Date Recording environment: * Active * Not Active * Already Active * Ended PDSMLRDR-02 Last Reference Date set to <date> for <resource> This message reports successful recording of a PDSMAN last reference date. <date> The last reference date that was recorded. <resource> The name of the resource in the format libraryname(member)/volser. The output destination for this message is controlled by the setting of the $ACCESS LRDRMSG parameter. PDSMLRDR-03 LRDR Queue <status> - <queuename> is <percent> full - <action> This message reports the usage status of a PDSMAN Last Reference Date Recording request queue. <status> The status of the request queue: * Exhausted * Critical * Warning * Notify <queuename> The name of the request queue. <percent> The percentage of the maximum number of queue entries currently in use. <action> The suggested action to be taken: * Start the PDSMLRDR Subtask * Check the PDSMLRDR Subtask Response Note: No notification is provided when the queue usage returns below the threshold value. PDSMLRDR-04 Last Reference Date Recording <function> <status> - <reason> This message reports status information related to the PDSMAN Last Reference Date Recording environment. <function> = The Last Reference Date Recording service function being processed. <status> = The status being reported. <reason> = The reason for the reported status: * Queue func RC=nn RSN=xxxx Data=xxxxxxxx * Invalid LRDR Request - <information> * <count> Requests Purged - <name> Queue PDSMLRDR-05 Last Reference Date Recording <result> for <resource> This message indicates that a last reference date recording operation has completed with a result other than successful. <result> The result of the Last Reference Date Recording operation: Error Recording failed for the resource
CA PDSMAN PDS Library Management 7.7 7 CA RS 1411 - PTF RO73404 Failed Recording failed for the resource Warning Recording completed but an abnormal condition was detected Bypassed Recording was bypassed because the library was migrated or due to a previous error when recording to the library. <resource> The name of the resource in the format: libraryname(member)/volser. For all results except "Bypassed", this message is followed by a PDSMLRDR-06 message that provides the reason for the result. PDSMLRDR-06 <reason> (- <data>) This message is issued following a PDSMLRDR-05 message to provide the reason for the error or warning and additional information about the result, if available. <reason> The reason for the error or warning: * Data Set Not Found * Unable to Obtain DCB Information * Data Set is Not Partitioned * Library is Migrated * Update Authorization Required for UserId <userid> * Unable to Allocate Library * Unable to Open Library for <mode> * Unable to Deallocate Library * PDSMAN Database Recording is Not Supported * BLDL I/O or Storage Error * Member Not Found in Library * Unrecognizable User Data is Present * Unable to Update Directory * The Member Has Moved since Last Access * Unable to Queue LRDR Request * Unable to Retrieve LRDR Request <data> Specific information about the condition when such data is available. SYMPTOMS: There are no symptoms associated with this fix. IMPACT: This change modifies PDSMAN Last Reference Date Recording to add the new support. Users may notice new PDSMLRDR-xx messages issued with recording or other differences as described in the section "Description". CIRCUMVENTION: There is no circumvention. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 Star Problem(s): PDSM 1012 Copyright (C) 2014 CA. All rights reserved. R00153-PDS770-SP1 DESC(ENHANCE PDSMAN LAST REFERENCE DATE RECORDING). ++VER (Z038) FMID (CPDS770) PRE ( RO21043 RO21122 RO21214 RO21781 RO21954 RO22426 RO24163 RO24296 RO25010 RO25866 RO28420 RO30006 RO30074 RO32065 RO33883 RO37159 RO37791 RO40737 RO42345 RO45849 RO45963 RO46743 RO49416 RO50409 RO50415 RO50594 RO52549 RO58121 RO58236 RO59424 RO61136 RO61137 RO62179 RO62417 RO62773 RO66087 RO68088 RO68291 RO68485 RO69258 RO69784 RO70838 RO71686 RO72095 ) SUP ( RO31442 TR31442 TR73404 ) ++HOLD (RO73404) SYSTEM FMID(CPDS770) REASON (RESTART) DATE (14286) COMMENT ( +----------------------------------------------------------------------+
CA PDSMAN PDS Library Management 7.7 8 CA RS 1411 - PTF RO73404 CA PDSMAN PDS Library Management Release 7.7 SEQUENCE Before Apply PURPOSE Ensure proper loading of resident modules. USERS All users. AFFECTED KNOWLEDGE CA PDSMAN administration REQUIRED ACCESS CA PDSMAN console commands REQUIRED ************************** * STEPS TO PERFORM * ************************** 1. Issue the following operator command: P PDSMAN 2. Wait for PDSMAN address space to successfully shut down. 3. APPLY the PTF. 4. Issue the following operator command: S PDSMAN ).
CA PDSMAN PDS Library Management 7.7 9 CA RS 1411 - PTF RO74545 7.7 RO74545 RO74545 M.C.S. ENTRIES = ++PTF (RO74545) PDSM00-44 MESSAGE INCORRECTLY ISSUED PROBLEM DESCRIPTION: During PDSMAN initialization, the PDSM00-44 message may be issued when it should not have been. This message can incorrectly indicate one or more Linklist data sets have been renamed, deleted or moved since the last IPL. This problem can only occur if a Linklist data set's first extent is allocated at cylinder 32768 (x'8000') or higher. This fix removes an obsolete instruction which checked for the presense of a PDSE. The high starting cylinder address triggers the incorrect decision to issue the PDSM00-44 message. SYMPTOMS: PDSM00-44 message is issued during initialization. IMPACT: This change avoids the incorrect PDSM00-44 message. CIRCUMVENTION: There is no circumvention. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 Star Problem(s): PDSM 1014 Copyright (C) 2014 CA. All rights reserved. R00157-PDS770-SP1 DESC(PDSM00-44 MESSAGE INCORRECTLY ISSUED). ++VER (Z038) FMID (CPDS770) PRE ( RO21883 RO24163 RO28420 RO30006 RO32119 RO52549 RO62446 RO66087 ) SUP ( AR22324 RO22748 RO22824 TR22748 TR22824 TR74545 )