CA PDSMAN PDS Library Management CA RS 1404 Service List

Transcription

1 CA PDSMAN PDS Library Management CA RS 1404 Service List Description Hiper 7.7 RO66063 $DEMO MAY FAIL WITH I/O ERROR AND U0001 ABEND RO66078 PDSMENT-2 OR U0001 ABEND TERMINATING HEALTH CHECKS RO66087 ENHANCE PDSMAN RULE PROCESSING RO66803 EZYEDIT MAY SHOW ZERO PRIMARY ALLOCATION AMOUNT RO66882 PDSMAN PREVENTS USAGE OF ISPF COMMAND STACK RO66989 ALLOCATION ERROR USING MASTER MENU OPTION 10 RO68024 EZYEDIT INCORRECTLY ISSUES 'INVALID DSN - QUOTES' MSG RO68025 EZYEDIT PANEL FIELD IS TOO LARGE RO68088 SUPPORT FOR IEBCOPY USER EXITS RO68136 DISPLAY TITLE PERCENT USED WHEN TITLE COMMAND IS USED RO68291 $DEMO STEP FCOIEXT ABEND S0C4-4 The CA RS 1404 service count for this release is 11

2 CA PDSMAN PDS Library Management 2 CA RS 1404 Service List for CPDS770 FMID Service Description Hiper CPDS770 RO66063 $DEMO MAY FAIL WITH I/O ERROR AND U0001 ABEND RO66078 PDSMENT-2 OR U0001 ABEND TERMINATING HEALTH CHECKS RO66087 ENHANCE PDSMAN RULE PROCESSING RO66803 EZYEDIT MAY SHOW ZERO PRIMARY ALLOCATION AMOUNT RO66882 PDSMAN PREVENTS USAGE OF ISPF COMMAND STACK RO66989 ALLOCATION ERROR USING MASTER MENU OPTION 10 RO68024 EZYEDIT INCORRECTLY ISSUES 'INVALID DSN - QUOTES' MSG RO68025 EZYEDIT PANEL FIELD IS TOO LARGE RO68088 SUPPORT FOR IEBCOPY USER EXITS RO68136 DISPLAY TITLE PERCENT USED WHEN TITLE COMMAND IS USED RO68291 $DEMO STEP FCOIEXT ABEND S0C4-4 The CA RS 1404 service count for this FMID is 11

3 CA PDSMAN PDS Library Management CA RS PTF RO RO66063 RO66063 M.C.S. ENTRIES = ++PTF (RO66063) $DEMO MAY FAIL WITH I/O ERROR AND U0001 ABEND The $DEMO job can fail in the AUDP28 step with a U0001 abend and these messages showing in the job log : PDSMEXCP-3 MEMBER mmmmmmmm TTR RESOLUTION ERROR PDSMRPDS-1 DDNAME PDSMPDS I/O ERROR READING MEMBER mmmmmmmm This problem is very rare because it requires that the PDSMAN CPDSLINK target library has a very specific track content. This fix changes the $DEMO job so the track content can not cause this problem. As described above. This problem only affects the $DEMO job. The problem can be circumvented by compressing the PDSMAN CPDSLINK target library and rerunning the $DEMO job. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 PDSM 983 Copyright (C) 2014 CA. All rights reserved. R00125-PDS770-SP1 DESC($DEMO MAY FAIL WITH I/O ERROR AND U0001 ABEND). PRE ( RO36050 ) SUP ( TR66063 )

4 CA PDSMAN PDS Library Management CA RS PTF RO RO66078 RO66078 M.C.S. ENTRIES = ++PTF (RO66078) PDSMENT-2 OR U0001 ABEND TERMINATING HEALTH CHECKS Health checks alert you to potential problems with your PDSMAN software. PDSMAN uses the CA Health Checker Common Service to manage the health checks it provides. Some users have experienced PDSMENT-2 messages followed by U0001 abends when the PDSMAN health checks are being terminated as part of the shutdown of the PDSMAN address space. System S0C4 abends may also occur as storage is accessed for diagnostic purposes. This problem is the result of a timing issue between the CA Health Checker Common Service and PDSMAN shutdown. The CA common service has called a health check to terminate, but due to a delay in processing the termination request the PDSMAN processing environment has already been removed. When the health check runs without the PDSMAN environment in place the PDSMENT-2 message and U0001 abend occur. Important! This problem, including the associated abend, does not negatively impact your system. The health checks are terminated and the resources held by the health checks are freed when the address space termination completes. After application of this fix, the following message is issued when a health check is called without an active PDSMAN environment: PDSMHCHK-05 PDSMAN Health Check Error - PDSMAN is NOT Active for <healthcheckname> Where <healthcheckname> is the name of the health check. This message can be safely ignored when it appears during health check termination. PDSMENT-2 messages indicating that PDSMAN has not been initialized followed by U0001 abends when terminating the PDSMAN address space. System S0C4 abends may also occur. Occurrence of the problem does not have a negative impact on your system because completion of the PDSMAN address space shutdown frees all resources. There is no circumvention to this problem. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 PDSM 984 Copyright (C) 2014 CA. All rights reserved. R00126-PDS770-SP1 DESC(PDSMENT-2 OR U0001 ABEND TERMINATING HEALTH CHECKS). PRE ( RO31373 RO42345 RO47842 RO58121 ) SUP ( RO52915 TR52915 TR66078 ) ++HOLD (RO66078) SYSTEM FMID(CPDS770) REASON (ACTION ) DATE (14010) COMMENT ( CA PDSMAN PDS Library Management Release 7.7 SEQUENCE After Apply PURPOSE Ensure proper re-intialization after maintenance. USERS All users.

5 CA PDSMAN PDS Library Management CA RS PTF RO66078 AFFECTED KNOWLEDGE CA PDSMAN administration. REQUIRED ACCESS CA PDSMAN console commands. REQUIRED ************************** * STEPS TO PERFORM * ************************** 1. Issue the following operator command: F PDSMAN,NEWHCHK 2. Wait for PDSMAN started task to issue PDSMHCHK-nn messages which indicate the PDSMAN Health Check Services have been Terminated, Ended, Initialized and became Active again. ).

6 CA PDSMAN PDS Library Management CA RS PTF RO RO66087 RO66087 M.C.S. ENTRIES = ++PTF (RO66087) ENHANCE PDSMAN RULE PROCESSING PDSMAN Initialization Control Statements, also called PDSMAN "Rules", are used to control many of the facilities provided by PDSMAN. These statements are read, interpreted and activated when the PDSMAN address space is started (initialized) or when the product is reinitialized using an F PDSMAN,NEWRULES operator command. Note: In this description, references to initializing PDSMAN also include reinitializing the product if it is already active, unless otherwise indicated. This fix enhances how PDSMAN rules are processed and reported when the product is initialized. Specific enhancements include: * The Initialization Rule Report * The Initialization Summary Report * PDSMINIT-xx Message Changes * Rule Directives * The #INCLUDE Rule Directive This fix also corrects a small number of issues existing in the current code and automatically validates the control statements built by the enhanced code against those built by existing processing. The enhancements and corrections are described in detail in the following sections Initialization Rule Report A new report, the Initialization Rule Report, is written each time the PDSMAN rules are processed. The report shows the text of each line in the rule input stream, identifies the source of the line and provides information about the initialization processing performed. The Initialization Rule Report is particularly helpful in determining which rules are inactive when the $SYSID control statement is used. The report also makes it easier to determine the cause and location of syntax or other errors detected when the rules are processed. The following fields are shown on the Initialization Rule Report: Flag This field identifies lines of special note. For example, it indicates lines that are inactive due to a $SYSID specification or those on which an error was detected. Src This field shows the source from which the line originated. The value reported corresponds to the source identification number provided on the Initialization Source Report (described below). Line This field shows the relative line number within the input source. Statement This field shows the input statement text, up to 80 bytes in length. Note that PDSMAN rules must be specified in the first 72 bytes of the input line regardless of the actual line length. Notes This field shows the processing performed for the line, errors that have been detected or other information about the input line. Input This field shows the number for the line within the

7 CA PDSMAN PDS Library Management CA RS PTF RO66087 full rule input stream. The Initialization Rule Report is written to the output location (usually SYSOUT) defined on the PDSMRPT DD statement in the PDSMAN address space procedure JCL Initialization Source Report Although PDSMAN rules are typically coded in a single source location, it is also possible to provide input from multiple sources. For example, as a concatenation of library members on the PDSMINIT DD statement in the PDSMAN address space procedure JCL. In some cases, PDSMAN itself also provides internally generated lines for the rule input stream. Another new report, the Initialization Source Report, is also written each time the PDSMAN rules are processed. The report shows the text of each line in the rule input stream, identifies the source of the line, and provides information about the initialization processing performed. The following fields are shown on the Initialization Source Report: Num This field shows the identification number assigned to each input source. The number corresponds to the value reported in the Src field of the Initialization Rule Report. Type This field shows the type of input source: internal (INT), a DD Name (DDN or DD), or a library member or sequential data set (DSN). DDN-Concat# For DDN-type input sources, this field shows the concatenation number of the source within a DD concatenation. For other types of input sources, a longer version of the input source type is shown. Source This field shows the name of the input source, including the member name and DASD volume serial where applicable. The source name may be indented and prefixed by ">" characters to indicate the relative level of this source to others in the input stream. Source number 0, PDSMAN_Internally_Generated_Bootstrap, is a special internal source created by PDSMAN to initiate rule processing. A line for another internal source, PDSMAN_Internally_Generated_Statements, is shown when rule processing determines that other statements such as the default $EZYCMD or $EZYICD statements are required. Notes This field shows information about the input source and normally reports "Read Successful". Input This field shows the number of input lines read from the indicated source. The Initialization Source Report is written to the output location (usually SYSOUT) defined on the PDSMRPT DD statement in the PDSMAN address space procedure JCL. It follows the corresponding Initialization Rule Report PDSMINIT-xx Message Changes PDSMAN initialization processing has been restructured to reduce the overall number of messages issued and to provide more descriptive error information. The following new messages are now issued: PDSMINIT-21 Syntax Error: <reason> - <data>

8 CA PDSMAN PDS Library Management CA RS PTF RO66087 Issued when a syntax error is detected in the user-supplied initialization rules. <reason> describes the cause for the error while <data> provides specific information about errant value. This message is followed by a PDSMINIT-22 message that details the location of the error. PDSMINIT-22 Detected at position <posn> on line <line> of <source> Issued following a PDSMINIT-21 syntax error message to describe the location of the error. <Posn> is the position (column number) of the syntax error, <line> is the line number within the input source on which the error was found and <source> is the name of the input source. PDSMINIT-24 <type> Error: <reason> - <data> Issued when an error is detected during Control Statement or Rule Directive termination (end) processing. <Type> reports the Control Statement or Rule Directive in error (for example, $BSI or #INCLUDE), <reason> reports the cause of the error and <data> provides additional information about the error. PDSMINIT-25 Error Reading <source> - <reason> Issued when an error occurs reading or preparing to read an input source. <Source> is the name of the input source being read and <reason> reports the reason for the error. PDSMINIT-27 System Symbol Resolution Error - ASASYMBM RC=<code> Issued when an error is returned from the ASASYMBM system symbol resolution service or when an error occurs invoking the service. <Code> is the ASASYMBM service return code. PDSMINIT-28 PDSMAN Variable Resolution Error - <reason> RC=<retcode> RSN=<rsncode> Data=<data> Issued when an error occurs during PDSMAN variable substitution. <Reason> describes the cause of the error. <Retcode>,<rsncode> and <data> are diagnostic return code, reason code, and extended data, respectively. The following messages are no longer issued: PDSMINIT-1 Line xxxxx - CONTROL STATEMENT ERROR AT POSITION xx Replaced by the PDSMINIT-21 and PDSMINIT-22 messages with reason text: Invalid Control Statement. PDSMINIT-2 Line xxxxx - PARAMETER ERROR AT POSITION xx Replaced by the PDSMINIT-21 and PDSMINIT-22 messages with varying reason text. PDSMINIT-3 Line xxxxx - OPERAND ERROR AT POSITION xx Replaced by the PDSMINIT-21 and PDSMINIT-22 messages with varying reason text. PDSMINIT-4 REQUIRED CONTROL STATEMENT(S) NOT SPECIFIED Replaced by the PDSMINIT-24 message with reason text: Required Control Statement Not Specified. PDSMINIT-5 REQUIRED PARAMETER(S) NOT SPECIFIED Replaced by the PDSMINIT-24 message with varying reason text. PDSMINIT-7 PDSMAN BEING INITIALIZED FROM <datasetname> Removed. The names of all input sources are now reported on the Initialization Source Report. PDSMINIT-8 DUPLICATE $ CONTROL STATEMENT NOT PERMITTED Replaced by the PDSMINIT-24 message with reason text: Invalid Duplicate Control Statement. PDSMINIT-9 DUPLICATE PARAMETER xxxxx NOT PERMITTED Replaced by the PDSMINIT-21 and PDSMINIT-22 messages with reason text: Duplicate Parameter is Invalid. PDSMINIT-10 Line passed to ASASYMBM: <line> Removed. The original contents of lines on which system symbols are substituted are shown on the Initialization Rule report. PDSMINIT-11 Line returned from ASASYMBM: <line> Removed. The resulting contents of lines on which system

9 CA PDSMAN PDS Library Management CA RS PTF RO66087 symbols are substituted are shown on the Initialization Rule report Rule Directives A new type of statement, called a Rule Directive (or more simply a directive), can now be specified in the PDSMAN rule input stream. Directives are used to add flexibility to how you specify and manage your PDSMAN rules. They differ from the existing control statements in that they are not built into internal control structures. Directives begin with a hash (or pound) sign (#) to distinguish them from control statements that begin with the dollar (or currency) sign ($). Like control statements, they must begin on a new input line and may include a comment beginning with "/*". Directives must be completely specified on a single line with no continuation #INCLUDE Rule Directive The #INCLUDE directive allows rules from sources other than the PDSMINIT DD statement in the PDSMAN address space JCL to be dynamically included in the rule input stream. This increases flexibility by allowing you to indirectly specify PDSMAN rule locations. The syntax for this directive is: #INCLUDE DD=ddname LIB=datasetnameÝ(membername) Ý/volume One of the following mutually exclusive parameters is required: DD The name of a DD statement in the PDSMAN address space JCL that specifies a library member, sequential data set or concatenation of rule sources containing PDSMAN rules. LIB The name of a library member or sequential data set containing PDSMAN rules. The volume specification allows uncataloged data sets to be used. The following shows example #INCLUDE directives: #INCLUDE DD=PDSMTEST #INCLUDE LIB=PDSMAN.PARMLIB(DEMORULE) #INCLUDE LIB=PDSMAN.SEQ.RULES/MYVOL Corrections for Issues in Current Code The following issues existing in the current code are corrected by this fix: System Symbol Substitution on the $SECURITY Control Statement. Some PDSMAN control statements are specifically excluded from system symbol substitution because they have parameters for which a value containing an ampersand (&), the system symbol identification character, is valid. Symbol substitution must be bypassed in order to avoid incorrectly substituting for these parameters. The $SECURITY control statement has this type of parameter and is now excluded from substitution. Previously, substitution was performed but in practice it had no ill effect because the parameter values did not include symbol names that are typically defined. $EZYCMD Default Values If you do not specify $EZYCMD statements but $EZYEDIT CMDTABUPD=Y is set, PDSMAN provides default $EZYCMD rules that are added internally to the input stream. The maximum length of the $EZYCMD ACT= parameter is documented as 68 characters, but some of the internally generated lines for the TSO and SPACE commands have lengths of 73 and 74 respectively. This situation is not flagged as an error because only the total length of the ACT= parameter is checked. However it does

10 CA PDSMAN PDS Library Management CA RS PTF RO66087 result in the SCRNAME(...) text for these two entries being truncated. With this fix, the internally generated statements have been changed to move the SCRNAME(...) text to the next line Automatic Validation of Control Statement Results This fix adds a new module, PDSMININ, to process the PDSMAN rules. The current rule processing code, PDSMINIT, has been retained. PDSMAN will automatically validate rule processing results by comparing the control structures created by the new and old code. Results of the comparison are reported on the Initialization Validation Report. In the unlikely event the old and new control structures do not match, a PDSMINBV-01 message is issued to the operator console. PDSMAN initialization continues normally using the new control statement structures. IMPORTANT: All occurrences of the PDSMINBV-01 message should be investigated to determine the cause of the mismatch. Retain the address space output and contact PDSMAN support. Automatic validation is bypassed if the rule input uses new capabilities, such as the #INCLUDE rule directive, that would be treated as invalid syntax when processed by the old code. Automatic validation is intended to operate for a limited time and will be disabled at a future date. There are no symptoms associated with this fix. This change modifies PDSMAN initialization processing to add the new support. Users may notice additional report output, changed messages or other differences described in the section "Description". There is no circumvention. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 PDSM 982 Copyright (C) 2014 CA. All rights reserved. R00127-PDS770-SP1 DESC(ENHANCE PDSMAN RULE PROCESSING). PRE ( RO21883 RO24163 RO25010 RO28420 RO30006 RO32119 RO42345 RO45849 RO45963 RO46743 RO50409 RO50594 RO52549 RO57358 RO58121 RO58236 RO59424 RO62446 ) SUP ( AR22324 RO18841 RO22748 RO22824 RO31442 TR18841 TR22748 TR22824 TR31442 TR66087 ) ++HOLD (RO66087) SYSTEM FMID(CPDS770) REASON (ACTION ) DATE (14010) COMMENT ( 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

11 CA PDSMAN PDS Library Management CA RS PTF RO66087 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 ).

12 CA PDSMAN PDS Library Management CA RS PTF RO RO66803 RO66803 M.C.S. ENTRIES = ++PTF (RO66803) EZYEDIT MAY SHOW ZERO PRIMARY ALLOCATION AMOUNT EZYEDIT may calculate a data set's Primary Allocation amount as zero when the following are true: - the data set was allocated using the MEGABYTE or KILOBYTE allocation units - the data set's initial allocation was split, by SMS, into multiple extents, leaving the first extent smaller than one of the requested allocation unit The small first extent means EZYEDIT can display '0' in the Primary Allocation field of the 'Data Set Information' and 'Dataset Create' displays. EZYEDIT is changed to display '<1' or '1'. EZYEDIT shows '0' for the Primary Allocation amount. This problem only affects the 'I' and 'CREATE' Line commands of the EZYEDIT Data Set List Display. None. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 PDSM 986 Copyright (C) 2014 CA. All rights reserved. R00128-PDS770-SP1 DESC(EZYEDIT MAY SHOW ZERO PRIMARY ALLOCATION AMOUNT). PRE ( RO21534 RO35820 RO44359 RO62179 ) SUP ( TR66803 )

13 CA PDSMAN PDS Library Management CA RS PTF RO RO66882 RO66882 M.C.S. ENTRIES = ++PTF (RO66882) PDSMAN PREVENTS USAGE OF ISPF COMMAND STACK ISPF allows a command stack to be actioned when the user enters the ISPF environment. The command stack may be provided through a the ZSTART variable or through a user variable. There are two cases where PDSMAN prevents the command stack from being actioned by ISPF : 1. PDSMAN will prevent the ISPF default command stack, as defined in ISPF's ZSTART variable, from being actioned when the following are true : - PDSMAN's $EZYEDIT rule with CMDTABUPD=Y is active - User is getting into ISPF using IBM's 'ISPF' or 'PDF' alias command names - the ISPF's ZSTART variable exists in the user's ISRPROF profile member 2. PDSMAN will prevent the user's command stack, as defined in a user's variable, from being actioned when the following are true : - PDSMAN's $EZYEDIT rule with CMDTABUPD=Y is active - User is getting into ISPF using IBM's 'ISPSTART', 'ISPF' or 'PDF' command names - User has typed the user's variable name using lowercase characters, for example : ispf mystart - the user variable exists in the user's ISPPROF or ISRPROF profile member Problem 1 occurs because PDSMAN only honored the existance of ZSTART when the 'ISPSTART' command was used to get into the ISPF environment. This fix removes checking for ISPSTART entry. Problem 2 occurs because PDSMAN's ISPF frontend passes the user variable name to ISPF exactly as it was typed, that is, in lowercase. ISPF expects a command stack variable name to be uppercased. This fix uppercases the variable name. This problem can be circumvented by typing the variable name in uppercase characters, such as : ispf MYSTART ISPF's command stack is not allowed to run when PDSMAN is active. This problem is limited to the combination of factors explained in the description details. None. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 PDSM 987 Copyright (C) 2014 CA. All rights reserved. R00129-PDS770-SP1 DESC(PDSMAN PREVENTS USAGE OF ISPF COMMAND STACK). PRE ( RO62179 ) SUP ( TR66882 )

14 CA PDSMAN PDS Library Management CA RS PTF RO RO66989 RO66989 M.C.S. ENTRIES = ++PTF (RO66989) ALLOCATION ERROR USING MASTER MENU OPTION 10 A user can experience an unexpected Allocation error when using option 10 of the PDSMAN Master Menu, Member Compare and Update Control. The problem occurs with these steps : 1. select option 10 of the PDSMAN Master Menu 2. select any processing option (Compare, Diff, etc.) 3. specify an existing data set in the first data set name field 4. specify a non-existent data set name in either of the other data set name fields 5. press ENTER 6. an Allocation error is issued for the non-existent data set name 7. correct the data set name and press ENTER 8. a new Allocation error message is unexpectedly issued for the first data set name The problem occurs because the CLIST does not release the data set allocations before re-allocating with the corrected names. This fix corrects the CLIST. User gets an unexpected Allocation error. This problem only affects option 10 of the PDSMAN Master Menu. The circumvention is to avoid using incorrect data set name. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 PDSM 988 Copyright (C) 2014 CA. All rights reserved. R00130-PDS770-SP1 DESC(ALLOCATION ERROR USING MASTER MENU OPTION 10). PRE ( RO36524 RO40379 ) SUP ( TR66989 )

15 CA PDSMAN PDS Library Management CA RS PTF RO RO68024 RO68024 M.C.S. ENTRIES = ++PTF (RO68024) EZYEDIT INCORRECTLY ISSUES 'INVALID DSN - QUOTES' MSG After PTF RO65714, EZYEDIT's Dataset List Display may incorrectly show this short message : 'Invalid DSN - quotes' This problem occurs when the 'B', 'E', 'S' or 'V' line command is issued against a 43- or 44-character data set name. This problem occurs because EZYEDIT passes a parameter to the ISPF service, which includes a trailing binary '00' character. When the data set name is 42 characters or less, there is still a separating blank character present, so the ISPF services can stop parsing before the binary '00'. As described above. This problem only affects the E, B, S and V line commands of EZYEDIT Dataset list display. Instead of explicitly using the line commands, use Point and Shoot to select the data set. PRODUCT(S) AFFECTED: CA PDSMAN PDS Library Management Release 7.7 PDSM 991 Copyright (C) 2014 CA. All rights reserved. R00131-PDS770-SP1 DESC(EZYEDIT INCORRECTLY ISSUES 'INVALID DSN - QUOTES' MSG). PRE ( RO21534 RO23088 RO42345 RO58121 RO62446 RO62902 RO63402 ) SUP ( RO23152 RO29208 RO65714 TR23152 TR29208 TR65714 TR68024 )

16 CA PDSMAN PDS Library Management CA RS PTF RO RO68025 RO68025 M.C.S. ENTRIES = ++PTF (RO68025) EZYEDIT PANEL FIELD IS TOO LARGE The EZYEDIT Dataset List Display uses panel EZY2P20 to allow a user to rename a data set. The new data set name field allows user to type many characters beyond the maximum length of a data set name. While there is editting to reject an invalid data set name, the reporting user said the end users were confused by the fact so many characters could be typed. This fix changes the new data set name field definition to allow only 46 characters. As described above. None. None. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 PDSM 992 Copyright (C) 2014 CA. All rights reserved. R00132-PDS770-SP1 DESC(EZYEDIT PANEL FIELD IS TOO LARGE). SUP ( TR68025 )

17 CA PDSMAN PDS Library Management CA RS PTF RO RO68088 RO68088 M.C.S. ENTRIES = ++PTF (RO68088) SUPPORT FOR IEBCOPY USER EXITS This modification adds CA PDSMAN support for IEBCOPY user exits, which were added at the z/os 2.1 level. IEBCOPY user exits are described in z/os 2.1 DFSMSdfp Utilities Appendix A. PDSMAN support for IEBCOPY user exits is implemented as follows: 1) If a Control Statement exit is detected, PDSMAN code will drive the exit and interpret control statements supplied by the exit. This is required so that PDSMAN can detect the presence of PDSMAN interest ($UPDATE, $DYNBLDL, and/or $LLA) in the IEBCOPY operation. 2) If a Member Selection exit is detected, PDSMAN code will drive the exit and perform member selection based on the exit's processing only when FastCopy is turned on. Otherwise the exit parameters are passed on to IEBCOPY unchanged. There are no symptoms associated with this fix. FastCopy is modified to support the new IEBCOPY user exit facility. The following new messages may be issued by FastCopy when an IEBCOPY user exit parameter list is detected: FCO118I IEBCOPY USER EXIT(S) ACTIVE: xx This message is issued to document the presence of an IEBCOPY user exit parameter list. xx identifies the exit or exits that are specified as follows: 'Control Statement' and/or 'Member Selection'. A new syntax error reason has been added to the FCO412A message: * SELECT AND EXCLUDE INVALID WHEN A MEMBER SELECTION USER EXIT IS ACTIVE SELECT and EXCLUDE control statements are not valid when a member selection user exit is active. FCO436A IEBCOPY USER EXIT ERROR - UNEXPECTED xx-i Return Code nnnn An invalid return code, nnnn, was received on a call to the xx, CONTROL STMT or MEMBER SEL, user exit. The -I is present only if the call was to perform exit initialization. The operation is terminated and the exit will not be called again. FCO436A IEBCOPY USER EXIT ERROR - SEVERE ERROR RETURN CODE - 36 The user exit gave return code 36, which indicates a severe error occurred. The operation is terminated and the exit will not be called again. There is no circumvention. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 PDSM 985 Copyright (C) 2014 CA. All rights reserved. R00133-PDS770-SP1 DESC(SUPPORT FOR IEBCOPY USER EXITS). PRE ( RO22426 RO24163 RO24391 RO25866 RO28420 RO33883 RO36320 RO36641 RO37159 RO38674 RO40737 RO42037 RO44914 RO45963 RO46743 RO50409 RO52466 RO52549 RO58121 RO59424 RO61432 RO62179 ) SUP ( AR58121 RO18637 RO36247 RO38262 RO43636 RO44646

18 CA PDSMAN PDS Library Management CA RS PTF RO68088 RO51012 RO57158 RO60050 TR18637 TR36247 TR38262 TR43636 TR44646 TR51012 TR57158 TR60050 TR68088 ) ++HOLD (RO68088) SYSTEM FMID(CPDS770) REASON (ACTION ) DATE (14064) COMMENT ( CA PDSMAN PDS Library Management Release 7.7 SEQUENCE After Apply PURPOSE Complete activation of PTF. USERS All users. AFFECTED KNOWLEDGE CA PDSMAN administration REQUIRED ACCESS CA PDSMAN console commands REQUIRED ************************** * STEPS TO PERFORM * ************************** 1. Issue the following operator command: F PDSMAN,NEWRULES 2. Ensure the PDSMAN address space issues PDSM00-1 message : PDSMAN BLDL/STOW INTERFACE RE-INITIALIZATION COMPLETE. ).

19 CA PDSMAN PDS Library Management CA RS PTF RO RO68136 RO68136 M.C.S. ENTRIES = ++PTF (RO68136) DISPLAY TITLE PERCENT USED WHEN TITLE COMMAND IS USED This fix adds a status message to reflect the current percentage of title space used. The message will appear when user issues the TITLE line command from EZYEDIT's Member List Display. If the percentage used exceeds 90%, the message will be changed into a warning to highlight that the title data is probably full and needs to be reorganized. This change alerts the user that the title data is almost full and the title update could fail. As described above. This change only affects the TITLE line command. None. PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 PDSM 993 Copyright (C) 2014 CA. All rights reserved. R00134-PDS770-SP1 DESC(DISPLAY TITLE PERCENT USED WHEN TITLE COMMAND IS USED). PRE ( RO36607 RO42345 RO43732 RO50409 RO63402 ) SUP ( RO46854 TR46854 TR68136 )

20 CA PDSMAN PDS Library Management CA RS PTF RO RO68291 RO68291 M.C.S. ENTRIES = ++PTF (RO68291) $DEMO STEP FCOIEXT ABEND S0C4-4 S0C4-4 abend in $DEMO job step FCOIEXT. $DEMO job S0C4-4 abend in PDSMDUPD at offset 543C. The $DEMO job demonstration of the automatic directory expansion function may fail. This is a timing problem that has very rarely been seen on lightly active systems. To allow the $DEMO job to run to completion change the FCOIEXT member of your CPDSDATA library as follows: On the second line, change: ALTERDIR OUTDD=DEMOSRC,BLOCKS=10 to * ALTERDIR OUTDD=DEMOSRC,BLOCKS=10 PRODUCTS AFFECTED: CA PDSMAN PDS Library Management r7.7 PDSM 994 Copyright (C) 2014 CA. All rights reserved. R00135-PDS770-SP1 DESC($DEMO STEP FCOIEXT ABEND S0C4-4). PRE ( RO21122 RO21781 RO21954 RO24163 RO24391 RO25866 RO28420 RO37159 RO38674 RO45963 RO49416 RO50415 RO52466 RO52549 RO58121 RO61137 RO62773 ) SUP ( AR24391 RO28618 TR28618 TR68291 ) ++HOLD (RO68291) SYSTEM FMID(CPDS770) REASON (ACTION ) DATE (14077) COMMENT ( CA PDSMAN PDS Library Management Release 7.7 SEQUENCE Before Apply PURPOSE Complete activation of PTF. USERS All users. AFFECTED KNOWLEDGE CA PDSMAN administration REQUIRED ACCESS CA PDSMAN console commands REQUIRED ************************** * STEPS TO PERFORM * ************************** Steps to perform: 1. Issue the following operator command: F PDSMAN,NEWRULES 2. Ensure the PDSMAN address space issues PDSM00-1 message : PDSMAN BLDL/STOW INTERFACE RE-INITIALIZATION COMPLETE. ).