IBM Support

PM66822: RDZ INTERNAL V8510 DEFECTS/ENHANCEMENTS (NON-RSE)

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • RDz internal v8510 defects/enhancements (non-RSE)
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: 01.SCLM Developer toolkit users              *
    *                 02.SCLM Developer toolkit users              *
    *                 03.All Remote Index Users (z/OS UNIX or MVS) *
    *                    who use either files with different       *
    *                    encodings, or who run the RDz server with *
    *                    a different code page than what is        *
    *                    configured in the the RSE connection on   *
    *                    the client.                               *
    *                 04.all Fault Analyzer Integration users      *
    *                 05.Users of COBOL Compiled XML Conversion    *
    *                    artifacts generated by the Enterprise     *
    *                    Service Tools Batch Processor in the IMS  *
    *                    COBOL top-down synchronous callout        *
    *                    scenario.                                 *
    *                 06.RDz users wanting to browse CA Endevor    *
    *                    repository elements to which they only    *
    *                    have read-only access                     *
    *                 07.RDz users who access the Endevor          *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM                               *
    *                 08.RDz users who access the Endevor          *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM                               *
    *                 09.RDz users who access the CA Endevor       *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM                               *
    *                 10.RDz users who access the CA Endevor       *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM                               *
    *                 11.RDz users who access the Endevor          *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM                               *
    *                 12.RDz users who access the Endevor          *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM                               *
    *                 13.RDz users who access the Endevor          *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM                               *
    *                 14.RDz users who access the Endevor          *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM                               *
    *                 15.RDz users who access the Endevor          *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM                               *
    *                 16.RDz users who access the Endevor          *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM                               *
    *                 17.RDz users who access the Endevor          *
    *                    repository using the IBM supplied RDz     *
    *                    Endevor RAM                               *
    *                 continued in AM77375                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: 01.Possible incorrect change code in    *
    *                         properties table for selected member *
    *                      02.Invalid error on missing environment *
    *                         variable displayed in SCLM           *
    *                         operations log                       *
    *                      03.When the client RSE connection, or   *
    *                         the MVS subsystem is configured with *
    *                         a different code page than what is   *
    *                         being used on the server, MVS member *
    *                         names may be misrepresented in the   *
    *                         Remote Index search results,         *
    *                         resulting in the inability to open   *
    *                         the matching file from the Remote    *
    *                         Index Search view.                   *
    *                         In addition, searches where users    *
    *                         have defined mixed code pages for    *
    *                         files that are indexed may fail to   *
    *                         find matches, since the files will   *
    *                         have been indexed using the code     *
    *                         page that the RDz server is running  *
    *                         with.                                *
    *                      04.Error parsing closing tags in report *
    *                      05.Support for mapping XML elements and *
    *                         attributes of type xsd:boolean has   *
    *                         been added to COBOL Compiled XML     *
    *                         Conversion in the IMS COBOL          *
    *                         top-down synchronous callout         *
    *                         scenario.                            *
    *                      06.RDz users are not able to browse the *
    *                         CA Endevor elements to which they    *
    *                         only have read-only access           *
    *                      07.The RDz users need reduced number of *
    *                         steps to locate and access the CA    *
    *                         Endevor elements and to work with    *
    *                         them.                                *
    *                      08.The RDz users need to customize      *
    *                         jobs before they are submitted.      *
    *                      09.The label for the message that       *
    *                         results from an action says "Error   *
    *                         Message" even when the operation     *
    *                         completed successfully. This can     *
    *                         create confusion.                    *
    *                      10.A logical record length of 80 is not *
    *                         sufficient to provide the            *
    *                         information that are needed for some *
    *                         of the items.                        *
    *                      11.When attempting to edit an element   *
    *                         and saving it at a lower level that  *
    *                         would cause jumping over another     *
    *                         version of that element in the build *
    *                         map, the CA Endevor API provides a   *
    *                         caution return code. The Endevor RAM *
    *                         interpreted the caution as an error, *
    *                         when it should not.                  *
    *                                                              *
    *                         When editing an element at a higher  *
    *                         level environment and choosing as    *
    *                         target a lower level environment,    *
    *                         the changes made to the element are  *
    *                         being saved at the entry stage of    *
    *                         the higher level environment instead *
    *                         of at the entry stage of the lower   *
    *                         level environment.                   *
    *                      12.When attempting to edit an element   *
    *                         and CARMA tries to get the memberid  *
    *                         of the element at the new location,  *
    *                         the stage name is missing from the   *
    *                         memberid. This causes the RAM not to *
    *                         be able to correctly locate the      *
    *                         element.                             *
    *                      13.When editting an element and saving  *
    *                         it in batch mode, if the temporary   *
    *                         edit dataset name is too long, the   *
    *                         SCL will contain a statement that    *
    *                         goes past column 72 and thus result  *
    *                         in the statement being truncated.    *
    *                         This causes the Add Element to fail. *
    *                      14.When searching for elements by CCID, *
    *                         the CCID fields of the search dialog *
    *                         are being ignored. This results in   *
    *                         search results with other elements   *
    *                         and not just the desired ones.       *
    *                      15.When retrieving elements by CCID in  *
    *                         batch mode, in the generated SCL,    *
    *                         the line containing the WHERE CCID   *
    *                         clause has binary zeroes at the end  *
    *                         of it. This causes errors in the     *
    *                         execution of the JCL because the SCL *
    *                         is then considered invalid as a      *
    *                         result of the binary zeroes being    *
    *                         contained within it.                 *
    *                      16.When creating a new Endevor element  *
    *                         using the New -> Endevor Element     *
    *                         function, the ability to specify the *
    *                         processor group is not provided in   *
    *                         the "New Endevor Element" dialog.    *
    *                         This is needed when a site does not  *
    *                         allow default processor group when   *
    *                         creating a new element.              *
    *                                                              *
    *                         When creating a new Endevor element  *
    *                         using the New -> Endevor Element     *
    *                         function, the return dialog          *
    *                         sometimes give an error stating that *
    *                         the number of expected return values *
    *                         is not what is expected.             *
    *                      17.When creating a new package using    *
    *                         the New -> Endevor Package function, *
    *                         the target Stage Id dropdown in the  *
    *                         "New Endevor Package View" dialog    *
    *                         contains an error message instead of *
    *                         the list of stages.                  *
    *                      continued in AM77375                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    01.SCLM members with a large number of includes or copybooks
       may have incorrect change code displayed in properties table
       when selecting the member in the SCLM views.
    02.The following invalid error message may be displayed in the
       SCLM operations log.
       ***ERROR:environment variable _CMDSERV_BASE_HOME not set
    03.The Remote Index Search function was running using the code
       page that is defined in the rsed.envvars file
       (_RSE_HOST_CODEPAGE) regardless of whether a connection or
       the MVS subsystem has a different code page configured.  This
       can result MVS PDS names, and MVS PDS member names which
       contain character code points 0x5B, 0x7B, 0x7C being
       incorrectly represented in the Remote Index Search View.
       In addition, since the Remote Index also used the RDz host
       code page to generate indexes, if a z/OS UNIX directory or
       file was defined in the RSE view to be a different code page
       than the server, or if the MVS PDS or MVS PDS member was
       defined on the client to be in a different code page, the
       index would have been incorrectly generated, resulting in
       missing matches when searches are performed.
    04.Report fails to load
    05.Since the valid lexical space of the xsd:boolean type is
       limited to only 'true', 'false', '1', or '0', XML2LS
       conversion needs to validate the content of XML elements and
       attributes that are of type xsd:boolean.
    06.The RDz Endevor CARMA RAM makes use of the CA Endevor
       Retrieve Element API to retrieve elements being opened for
       browsing. The RDz users who only have read-only acess to
       those elements are not able to browse them because of this
    07.The number of steps needed in RDz to locate, access and work
       with the Endevor elements need to be reduced in order to make
       the development process simpler.
    08.The RDz users need to be able to have their own customized
       jobcards before submitting the JCL.
    09.The text of the Message label is "Error Message" but a text
       of "Message" may be more appropriate to avoid confusion.
    10.In order to be able to provide more information for each of
       the items that are needed for the RDz client's internal
       processing a record length greater than 80 is needed to hold
       the data for each item whose information is extracted from
       the CA Endevor repository
    11.When attempting to edit an element and saving it at a lower
       stage while jumping over another version of that same element
       at an intermediate stage, the caution return code from the CA
       Endevor API should not be treated as an error.
    
       When editing an existing element, the memberid associated
       with the element being edited needs to be the one provided by
       the host and not the memberid of the selected element.
    12.When attempting to edit an element, the stage name is missing
       from the memberid for the new location.
    13.When editting an element, a long temporary edit dataset will
       cause the update of the element to fail when submitted in
       batch
    14.When searching for elements by CCID, the CCID fields of the
       search dialog are being ignored.  The CCIDs specified in the
       the search request were not being used in the request for the
       elements that match the specified CCIDs.
    15.When retrieving elements by CCID in batch mode, the line that
       contains the WHERE CCID clause in the generated SCL has
       binary zeroes at the end of it.  This causes errors in the
       execution of the JCL because the SCL is then considered
       invalid as a result of the binary zeroes being contained
       within it.
    16.The New Element dialog needs to allow specifying a processor
       group.
       The number of return values is not correctly set for the New
       Endevor Element function.
    17.The LRECL definition for the SPCLLIST DD dataset has been
       changed from 80 to 256. The programs that access that dataset
       need to also be changed to account for the new LRECL.
    continued in AM77375
    

Problem conclusion

  • 01.Correct change code now displayed in SCLM properties table.
    02.changed from  _CMDSERV_BASE_HOME to CGI_ISPHOME in
       rsed.envvars. The misleading error message is no longer
       displayed in the SCLM operations log.
    03.The Remote Index function will now respect client
       configurations for code pages, at the connection, and MVS
       subsystem level, as well as the z/OS UNIX directory and file,
       MVS PDS, and MVS PDS member code page configurations when
       generating an index, in addition to searching an index.
    
       Client APAR PM56858 is also required to be applied for this
       fix to be fully functional.
    04.Fixed parsing error
    05.The following new COBOL Compiled XML Conversion runtime
       message IRZ0279S has been added.  This message will be issued
       by COBOL Compiled XML Conversion when the content of an XML
       element or attribute that is of type xsd:boolean does not
       match 'true', 'false', '1', or '0'.
    
       IRZ0279S XML to language structure conversion could not
       complete in program PROGRAM-NAME because conversion of the
       character content of an XML element or attribute that is of
       type xsd:boolean did not match 'true', 'false', '1', or '0'.
       The error occurred at XML path XML-PATH with the character
       content CHARACTER-CONTENT.
    
       Explanation: XML to language structure conversion detected
       that the content of an XML element or attribute that is of
       type xsd:boolean did not match 'true', 'false', '1', or '0'.
    
       Programmer response: Correct the input XML message. Ensure
       that the message is valid according to the XML Schema upon
       which the XML to language structure converter is based.
    
       System action: The converter will either signal a Language
       Environment condition or, if the optional feedback code
       argument is provided, a condition token representing the
       condition will be placed in the argument.
    06.The RDz Endevor CARMA RAM is being modified to make use of
       the CA Endevor Extract Element API to allow users with
       read-only access to the CA Endevor elements to open them for
       browsing.
    07.This new release of the RDz Endevor RAM provides an Enhanced
       Element Retrieval and Processing to improve the user
       experience and simplify the process needed to locate, access
       and work with the CA Endevor elements from within RDz.
    08.This new release of the RDz Endevor RAM provides the RDz
       client with the ability to request that the batch action JCL
       be sent to it for the JCL to be customized on the client
       before being submitted.  Also, the Job number is provided to
       the end user.
    09.The text of the message label is being changed to say
       "Message" to avoid confusion.
    10.The logical record length of the dataset associated with the
       DD name SPCLLIST is being increased to 256 to allow for more
       information to be provided for the items provided to the RDz
       client from the host for internal processing.
    11.The change to the RDz Endevor RAM is to accept the caution
       return code from the CA Endevor API and to not treat it as an
       error.
    
       The change to the RDz Endevor RAM is to provide the new
       memberid of the element to the RDz client.
    12.The change to the RDz Endevor RAM is to specify the stage
       name in the memberid.
    13.The change to the RDz Endevor RAM is to place the member name
       on a line separate from the dataset name in the generated SCL
       statement for the Add Element action.
    14.The change to the RDz Endevor RAM is to make use of the CCIDs
       specified in the search dialog
    15.The change to the RDz Endevor RAM is to make sure that the
       statements in the SCLs are terminated by spaces and not
       binary zeroes
    16.The change to the RDz Endevor RAM is to allow a processor
       group to be specified for the New Element dialog. Also, the
       number of return values is now set to what is expected by
       CARMA.
    17.The change to the RDz Endevor RAM is to make sure that the
       program that access the SPCLLIST DD use a LRECL of 256.
    continued in AM77375
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM66822

  • Reported component name

    RD/Z HOST

  • Reported component ID

    5724T0723

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-14

  • Closed date

    2012-11-20

  • Last modified date

    2012-12-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK83670

Modules/Macros

  • AZUTSTUB BWBINT   BWBRPTN  CRA$VCAD CRA$VDEF
    CRABATCA CRABCFG  CRABJOBC CRAMAJAR CRANDVRA CRANORAM CRAREXX
    CRARNDVR CRARPKGS CRASCFCA CRASRV   CRASSTUB CRASUBCA CRA0VCAD
    CRA0VCAS FEK#LVL# FEK@OPTN FEK@PRIM FEKAPF   FEKAPPL  FEKBPXXX
    FEKCARB1 FEKCARB2 FEKCARVD FEKCARVM FEKCARVP FEKCARVS FEKCLOGR
    FEKCOMXX FEKCOPY  FEKCRASR FEKCRCNE FEKCRCNF FEKCRSED FEKCSET
    FEKDSN   FEKFBLD  FEKFFAMI FEKFIVPC FEKFIVPL FEKFLOCS FEKFMLUC
    FEKFMVSL FEKFRSES FEKFT001 FEKINIT  FEKISPF  FEKJCMD  FEKJCNFG
    FEKJMON  FEKLINK  FEKLISTU FEKLOCK  FEKLOGR  FEKLOGS  FEKMAIN
    FEKPOE   FEKPROGM FEKPROGU FEKPTKT  FEKRACFI FEKRACFJ FEKRDZE
    FEKRDZI  FEKRDZM  FEKRDZT  FEKRSEDE FEKSCLMS FEKSCLMT FEKSCMTR
    FEKSERV  FEKSETUP FEKSTC   FEKUSER  FEKXML   IRZMENG  IRZMSGT
    IRZMUEN
    

Fix information

  • Fixed component name

    RD/Z HOST

  • Fixed component ID

    5724T0723

Applicable component levels

  • R850 PSY UK83670

       UP12/12/14 I 1000

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: Rational Developer for System z

Software version: 8.5

Reference #: PM66822

Modified date: 14 December 2012