CA Software Change Manager 521 Patch 3- MVS and USS Agents - CA Technologies
{{search ? 'Close':'Search'}}

CA Software Change Manager 5.2.1 Patch 3- MVS and USS Agents

Last Updated: October 13, 2004


1.0 Welcome

2.0 Operating System Support
2.1 USS Agent
2.2 MVS Agent and ISPF Client

3.0 System Requirements
3.1 USS Agent
3.2 MVS Agent and ISPF Client

4.0 Installation Considerations
4.1 For All Agents
4.2 For RACF Users
4.3 For Harweb and USS Agents Only

5.0 Known Issues
5.1 USS Agent, MVS Agent, and ISPF Client
5.2 USS Agent
5.3 MVS Agent

6.0 Contacting Technical Support

7.0 Downloads


1.0 Welcome

Welcome to the readme file for the z/OS components for AllFusion® Harvest Change Manager Release 5.2.1 (hereafter called Harvest). The Harvest z/OS components are the MVS agent, the ISPF client, and the z/OS UNIX Systems Services (USS) agent. This readme file contains operating system support, system requirements, and known issues for the MVS and USS agents only.

For information about other Harvest Release 5.2.1 components on Windows, UNIX, and Linux, see the Harvest Release 5.2.1 Patch 3 main readme file (readme_harvest.html or readme_harvest.txt) on our web site, https://support.ca.com.


2.0 Operating System Support

This section lists the operating systems supported by the Harvest Release 5.2.1 z/OS components. Computer Associates supports these operating systems for the duration of their life cycle (as determined by their manufacturer) or until Computer Associates announces that we are dropping support. For the latest information about supported operating systems, see our web site, https://support.ca.com.


2.1 USS Agent

The USS agent allows a Harvest client to access a remote USS file system. This agent requires z/OS 1.3 or 1.4.


2.2 MVS Agent and ISPF Client

The MVS agent and ISPF client require the following:

  • At a minimum, OS/390 V2R10 must be installed for non-IBM mainframes.

  • At a minimum, OS/390 V2R8 must be installed for IBM mainframes.


    3.0 System Requirements

    The MVS and USS agents for Harvest Release 5.2.1 require that Harvest Release 5.2.1 Patch 3 is installed on all Windows, UNIX, and Linux machines in your Harvest system.

    On z/OS, Harvest supports partitioned datasets with the ISPF client and MVS agent. Harvest supports HFS files with the USS agent.


    3.1 USS Agent

    The USS agent allows a Harvest client to access a remote USS file system. This agent requires z/OS 1.3 or 1.4.


    3.2 MVS Agent and ISPF Client

    The MVS agent and ISPF Client require the following hardware and software:

  • TSO region size of 4096

  • 550 tracks of temporary space

  • 620 tracks for permanent datasets

  • TCP/IP protocol

  • C ++ Runtime Libraries

  • AGNTD must be installed in an apf authorized load library for MVS installations.


    4.0 Installation Considerations


    4.1 For All Agents

    For instructions to install the MVS and USS Agents and other Harvest components, see the Harvest Install Guide on the Computer Associates web site, https://support.ca.com.

    Before you can use the MVS and USS agents, you must:

  • Install and configure the Harvest server on Windows, UNIX, or Linux.

  • Configure your agents and start them; for instructions, see the Harvest Administrator Guide and User Guide.


    4.2 For RACF Users

    For instructions to establish RACF security, see the IBM z/OS Unix System Services Planning Guide. This guide is available from IBM at http://ibm.com.

    The MVS agent uses USS and requires a valid OMVS segment for users using and starting the agent. If users do not have an OMVS segment defined, a default OMVS segment must be defined. The MVS agent issues authorization functions for user logged into it.

    The USS agent does not issue authorization functions for users logged into it. The USS agent is a process started for an individual user id.


    4.3 For Harweb and USS Agents Only

    The Harweb 5.2.1 installation overwrites files installed by Harvest 5.2.1 Patch 3. Consequently, to enable Harweb to connect to USS agents, follow these steps:

  • Uninstall Harvest 5.2.1 Patch 3, according to the instructions in the Harvest 5.2.1 Patch 3 main readme file (described in the Welcome section of this file).

  • Install Harweb 5.2.1, according to the instructions in the Harvest 5.2.1 Web Interface Install Guide.

  • Install Harvest 5.2.1 Patch 3, according to the instructions in the Harvest 5.2.1 Patch 3 main readme file.

  • Install Harweb 5.2.1 Patch 3, according to the instructions in the Harvest 5.2.1 Patch 3 main readme file.


    5.0 Known Issues


    5.1 USS Agent, MVS Agent, and ISPF Client

    PR3140: The USS agent, MVS agent, and ISPF client allow z/OS files to be checked into a Harvest repository as text files, performing ASCII-to-EBCDIC and record-to-stream conversion as needed. However, due to the limitations of code page conversion, not all permissible characters may be supported by this conversion. For information about code page conversion, see the IBM document z/OS V1R4.0 C/C++ Programming Guide (Document Number SC09-4765-03).

    Therefore, we strongly recommend that you test to ensure that the code pages and character sets you use are compatible. If you have any doubt that the conversion does not support the source files you need to manage, we recommend setting the repository options to manage MVS and USS files in binary mode only.


    5.2 USS Agent

    PR1205: When you start the USS agent using a UNIX X terminal remote connection to USS, your login password is echoed on the screen in plain text. This problem typically occurs when you start this connection by logging in to a non‑USS UNIX system from a Windows client and you telnet to USS from the remote UNIX shell. To prevent your login password from being echoed on the screen in plain text when you start the USS agent, use a direct telnet session, not an X terminal connection.

    PR3127: This problem occurs if the broker machine suddenly restarts after you start a remote USS agent and then connect to the same agent by using the Connect to New Agent option of the Remote Agent Neighborhood on the Files tab of the Harvest Workbench GUI. If the broker machine suddenly restarts for example, because of a power failure or other unintentional shutdown, you need to re-establish your connections. To do so, start the broker, start the Workbench, and double-click the remote agent connection to the USS agent. When you double-click the remote agent connection and enter your password, you may receive an incorrect error message that your username is incorrect.

    If this problem occurs, to reconnect to the agent, issue a kill -9 command to stop the agent and then restart the agent. After doing so, you can use the Workbench to connect to the newly started instance of the USS agent.

    PR3139: The Harweb 5.2.1 installation overwrites files installed by Harvest 5.2.1 Patch 3. To enable Harweb to connect to USS agents, follow the steps in For Harweb and USS Agents Only in the Installation Considerations section of this readme file.


    5.3 MVS Agent

    PR884: If you enter a fully qualified PDS name when selecting an initial directory from the Workbench GUI, you cannot expand the Agent node and clicking the plus sign (+) simply removes it (the plus sign). To correct this problem, right-click the agent and enter the PDS name without the final qualifier. The Agent node can now be expanded and it should be possible to select the required dataset.

    PR2190: When you exit the ISPF client, you may receive the following messages:
     "BPXP018I THREAD 1252A28000000001, IN PROCESS 83886182, ENDED WITHOUT BEING  UNDUBBED WITH COMPLETION CODE 0013E000, AND REASON CODE 00000000." 

    These messages relate to mixed mode (MVS and Open Systems Unix) process termination and can be ignored.

    PR3020: When the Harvest broker is shut down with the all option (bkrd -shutdown=all), the MVS agent issues a message indicating that the message was received. However, the agent stays active and consumes CPU time until the CPU time limit is reached. At that time, error message CEE5230S is issued. If you must shut down the MVS agent, first check that there are no active users and then simply CANCEL the job or started task.

    PR3113: For RACF users only. If your attempt to log in to the MVS agent fails because you have an invalid OMVS segment, you may receive the following misleading error messages: an "Inaccessible Initial directory" message followed by a "Wrong user name for agent" message. If you receive these messages and you believe that your OMVS segment, username, and password are valid, check the MVS agent job log for RACF messages indicating why your login attempt failed.

    PR3128: If you select an invalid Initial directory when connecting to an MVS agent from the Workbench GUI, clicking the plus sign (+) beside the remote agent name does not expand the node or display any datasets. The plus sign is removed, to indicate that this node cannot be expanded. In addition, the message "ERROR RETURNED FROM CATALOG SEARCH" is written to the Agent log. To correct this problem, right-click the agent and enter a valid initial directory.

    PR3129: If the MVS agent is restarted while Workbench users are connected, those users are no longer able to authenticate with the agent. Attempts to check in, check out, or list PDS contents fail, and no members are displayed in the selected datasets). The MVS Agent job log shows messages like the following:
     "FINDFILE 5758| Spec<//'PREFIX.FILE.NAME'> Recurs<0> Fm</pt_HClient://HARSERVER/  1508> |-160 | Hnd<8> #Item<0>" 

    The file I/O return code "-160" indicates that the security key is invalid. To correct this problem, either stop and restart the Workbench GUI, or remove and re-add the MVS agent in the Remote Agent Neighborhood on the Files tab of the Harvest Workbench GUI.

    PR3130: The MVS agent abends with a B37 or E37 error if you attempt to check out items to a full partitioned data set (PDS) or if you attempt to check out new items to a full directory. To prevent or address this problem, try one or more of the following:

  • Use partitioned data set/extended (PDS/E) format instead of PDS format. At publication time, IBM recommends PDS/E format.

  • Compress your data sets frequently.

  • Carefully monitor directory usage, extents, and free space in your data sets. Whenever necessary, create new data sets, or reorganize existing ones, to suit your needs.

  • Use a utility such as BrightStor CA-PDSMAN PDS Library Management. This Computer Associates solution addresses many common library issues and which can dynamically reallocate the unused or "dead" space in a PDS. For more details about this solution, see https://support.ca.com.

    If an ISPF client attempts to access an MVS data set, the list of members may not be displayed, without any corresponding error message. This problem occurs if the data set is protected by an MVS security product or if the attempt to read catalog information about the data set fails.

    PR3131: If you attempt to start the MVS agent before you start the Harvest server, the agent fails to connect and issues message like the following:
     Could not connect to <tcp:machine-name> RTserver. Skipping starting <start_never:tcp:machine-name> RTserver. HAgent | 1040303 09:58:07 | ERROR: Initialization fails HAgent | 1040303 09:58:07 | ---- stopped ---- connect: EDC8128I Connection refused. 

    Even if the Harvest server is subsequently started, the attempt to connect fails. To correct this problem, cancel and restart the MVS agent after you start the Harvest server.

    Note: Once the MVS agent has connected successfully, you can stop and restart the Harvest server, if necessary.

    PR3132: The file name filter is not supported on check in from the MVS agent. To check in a subset of members from an MVS PDS or library, use the Find button to return all members, and then select (using Shift+Click, Ctrl+Click, or both) to highlight the member(s) you require.

    PR3133: Unless you specify an override HARVESTMVSHLQ= parameter, the Harvest MVS agent, by default, creates and uses temporary datasets in the HFS subsystem in the /tmp directory. These files may not always be cleaned up when the agent is shut down. Your standard housekeeping policies should include removing any leftover files in this directory. The Harvest files may be identified as having the OWNER/GROUP set to match the userid associated with the MVS agent job or task and will have names like nnnnnnnn.POnnnnnn.SInnnnnn.Xnnnnnnn.Ynnnnnnn (where nnnnnn is numeric).

    PR3134: The Administrator, load repository facility does not support MVS agent files in this release. As a workaround, check in the files and members and promote them throughout your life cycle.

    PR3136: When you attempt to check out a sequential file using the ISPF client, the "new" file is always allocated as FB80. As a workaround, if other DCB parameters are required, copy the file to a PDS or PDS/E and check in or check out to that dataset instead.

    PR3137: The ISPF client does not support multiple invocations on split screens. A U4093 abend may occur if you attempt to issue an HCI or HCO command on a split screen while a second HCI or HCO command is active or while a Harvest client is active. If a U4093 abend occurs, switch to the alternate screen(s) and shut down any instances of the Harvest application that are not required.

    PR3138: If an item in an uncompressed repository is checked out to an MVS agent PDS and then simply checked back in (without being updated), Harvest creates a new version instead of reporting that no changes were detected in the file.

    PR3529: Check-in binary as text gives table lock agent error.

    PR3531: MVS agent does not support wild card.


    6.0 Contacting Technical Support

    If you need technical assistance with this product, access the Computer Associates web site, https://support.ca.com, where you can quickly locate answers to many questions. Technical support is available 24 hours a day, 7 days a week.


    7.0 Downloads

    CA Software Change Manager 5.2.1 MVS and USS agent downloads are available below:

    MVS Agent
    USS Agent


Chat with CA

Just give us some brief information and we'll connect you to the right CA Expert.

Our hours of availability are 8AM - 5PM CST.

All Fields Required

connecting

We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile


  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.


    How Did We Do?
    Let us know how we did so that we can maintain a quality experience.

    Take Our Survey >

    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing