IBM Tools Base Connection Server for z/OS Documentation Updates

Product documentation


Abstract

Updates that apply to IBM Tools Base Connection Server for z/OS User's Guide, Version 1 Release 4 (SC19-3766-00)

Content

The most recent update is listed first.



Update 2

Date of change:
August 22, 2013

Topic: Ch. 4 Stopping the Connection Server

Change Description: Procedure for shutting down a Connection Server instance.


    New chapter title: Shutting down the Connection Server

    To shut down a Connection Server instance with a quiesce, issue a MODIFY command to the corresponding MVS batch job.

    F jobname,SHUTDOWN

    On receiving a SHUTDOWN quiesce command the Connection Server instance rejects new client request threads and shuts down when all active client request threads have completed.

    To force a Connection Server instance to terminate immediately, cancelling any active client request threads, issue the following MODIFY command to the corresponding MVS batch job.

    F jobname,SHUTDOWN FORCE

    Note that SHUTDOWN FORCE can be specified while a shutdown quiesce attempt is still in progress. This upgrades the quiesce shutdown to a forced shutdown.

    As a shorthand alternative, a STOP command can be used to drive a SHUTDOWN quiesce.

    P jobname

    Note: If a STOP command is used the Connection Server instance will not respond to subsequent MODIFY commands. As such the MODIFY shutdown method is preferable.





Update 1

Date of change:
August 22, 2013

Topic: New and changed messages for IBM Tools Base Connection Server for z/OS.

Change Description: New messages have been added to or changed in IBM® Tools Base Connection Server for z/OS® since the publication of the Connection Server User's Guide V1R4 (SC19-3766-00).

New messages


    FUD0011W

    Listener socket connection dropped out. New client connections are suspended

    Explanation: Due to events external to the Connection Server, the Listener socket connection has dropped out.

    System action: Without the Listener socket connection the server is unable to accept new client connections. Existing client connections may be able to continue depending on the event that has caused the Listener socket to be dropped. For example, if the cause was that TCP has ended, then all client connections will have been dropped too.

    User response: Use the RESTARTIP command, or recycle the Connection Server, to reestablish the Listener socket connection.

    FUD0012I

    Insufficient access authority - UserID=user_id SAF class: safcl Access intent: intent Resource: profile

    Explanation: The Connection Server detected an unauthorized request (a violation) made by a user.

    System action: The user request is rejected.

    User response: Follow the security procedures established for your installation. If no such procedures have been established, report the complete text of this message to the security administrator.

    FUD2028I

    Product product_code stopping

    Explanation: The server has commenced the process of stopping the named product.

    System action: STOP processing continues. Note that a product cannot stop while active request threads are outstanding, so the STOP process might be prolonged. No new external client requests will be accepted for the product at this stage.

    User response: This message is for informational purposes only.

    FUD2034E

    PassTicket generation failed RC=rc - Class=PTKTDATA, UserID user_id, ApplName=appl_name

    Explanation: Connection Server encountered an error while trying to generate a PassTicket with the user ID and application name shown in the message text.

    rc contains the return code from the RACF routine:

    • 04 Incorrect PassTicket.
    • 08 No PTKTDATA profile found for the application.
    • 12 No task or address space ACEE found.
    • 16 Caller is not authorized.
    • 20 The RACF PTKTDATA class is not active.
    • 24 Error in the session key generator process.

    user_id contains the user ID associated with the failed request.

    appl_name contains the application name associated with the failed request.

    System action: The processing thread that requested the PassTicket is terminated.

    User response: Contact IBM Software Support.

    FUD5307E

    Dynamic allocation ALLOC|FREE failed for DSN=dsname, UID= user_id

    Explanation: Dynamic allocation failed for the named object, where the allocation request was driven as part of user request processing. One or more dynamic allocation messages precede this message.

    dsname contains either the data set name or INTRDR.

    user_id contains the user ID associated with the failed request.

    System action: Processing continues but the user request associated with the dynamic allocation fails.

    User response: Determine the cause of the dynamic allocation failure. Correct and retry the user request.

    FUD5308E

    JCLIN data set is not a card-image PDS, DSN=dsname

    Explanation: For a FUDSUBMIT request, the specified JCLIN data set was found not to be a card-image (LRECL=80) PDS.

    System action: The FUDSUBMIT request fails.

    User response: Specify a card-image PDS and retry the request.

    FUD5309E

    Access denied to JCLIN data set, DSN=dsname

    Explanation: For a FUDSUBMIT request, the requesting user is not authorized to read from the JCLIN data set.

    System action: The FUDSUBMIT request fails.

    User response: Correct the user authorization or modify the data set specification and retry the request.

    FUD5310E

    JCLIN member member_name not found, or found to be empty

    Explanation: For a FUDSUBMIT request the specified JCLIN data set member was not found, or was found but had no records.

    System action: The FUDSUBMIT request fails.

    User response: Modify or respecify the JCLIN member and retry the request.

    FUD5311E

    JCL submitted to INTRDR but no job resulted

    Explanation: For a FUDSUBMIT request the specified JCLIN data set member was tailored and submitted. However, no job resulted, which is indicative of invalid JCL with no JOB card.

    System action: The FUDSUBMIT request fails.

    User response: Modify or respecify the JCLIN member and retry the request.



Changed messages

    FUD1012E

    Invalid maximum number of TCP sockets: nnnn. Valid range is 50 through 2000

    Explanation: Where:

    nnnn The TCP_MAXSOC value specified in the FUD configuration member

    The TCP_MAXSOC server configuration parameter value is invalid. If specified, the value must be in the range 50 - 2000. The default is 50.

    System action: The server will terminate.

    User response: Correct the parameter value and rerun the job.

    FUD2100I

    DISPLAY PRODUCT product
    Status . . . . . . . . :
    status

    Explanation: Result of a console DISPLAY command.

    F server,DISPLAY product

    status=

      Stopped
      Starting
      Starting, STOP scheduled
      Available
      Stopping
      Not initialized

    System action: None.

    User response: This message is for informational purposes only.


Publication number

SC19-3766-00

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tools Base for z/OS
Connection Server

Software version:

1.4.0

Operating system(s):

z/OS

Reference #:

7039458

Modified date:

2013-08-28

Translate my page

Machine Translation

Content navigation