Warning Messages

This section is a complete listing of all the warning messages.

  • PGTS0104W Server Not authorized to purge MSGQ qqqqqqqq: Purging all records in Queue

    Explanation:

    The Platform Server was configured to use SSL. GLOBAL SSL_MESSAGE_QUEUE_NUMBER parameter defines the message queue number qqqqqqqq that is used. At the start of the Platform Server, the message queue is purged and then recreated.

    This message indicates that the Platform Server cannot purge the message queue. Instead, the Platform Server purges each record in the queue. This can happen because a message queue is created by a different started task. Each started task has to use a unique message queue.

  • PGTS0833W GET for Audit xxxxx Failed: Alternate Index does not point to base record - Record bypassed

    Explanation:

    The Platform Server was reading an alternate index (AIX) for the path defined by xxxxx and received RPLTNCD error x’90’. This means that AIX was pointing to a record in the base cluster that did not exist or indicates that the alternate index was corrupted. The Platform Server bypasses this record and attempts to read the next record in the path.

  • PGTS0834W GET for Audit xxxxx Failed: Alternate Index should be rebuilt using IDCAMS

    Explanation:

    The Platform Server read an alternate index (AIX) for the path defined by xxxxx and received RPLTNCD error x’90’. This means that AIX pointed to a record in the base cluster that did not exist or that the alternate index was corrupted.

    This error occurs on 10 consecutive readings so the Platform Server terminates the inquiry request. When this message is displayed, it typically means that the alternate index has become corrupted, and must be rebuilt using the IDCAMS utility.

  • PGTS1025W Initiator ACBNAME same as responder ACBNAME - they should be different

    Explanation:

    Check your GLOBAL definitions and correct the error.

  • PGTS1027W Responder GATELU not specified - please use format - DEFAULT_GATELU=(INITLU,RESPLU)

    Explanation:

    Check your GLOBAL definitions and correct the error.

  • PGTN1350W No xxxx received in request.

    Explanation:

    Contact TIBCO technical support if you receive this message.

  • PGTN1351W No Default xxxx specified in the Global Entry

    Explanation:

    The default packet size or window size is not specified in the GLOBAL parameters.

  • PGTN1352W Defaulting xxxx to a system default of yyyy

    Explanation:

    Because the default parameter mentioned in this message was not coded in the GLOBAL parameters, the system default value is applied.

  • PGTT1751W TCPTRAC ALREADY TURNED ON

    Explanation:

    The TCPTRON operator command was entered to start a TCP trace, but TCP tracing is already enabled.

  • PGTT1752W TCP Trace already on for: nnnnnnnnnn

    Explanation:

    The TCPTRON operator command was entered to start a TCP trace for a particular node, IPv4 or IPv6 address, but tracing is already enabled for that node or IP address.

  • PGTT1763W DNS Address lookup failed for IP Address=iiiiiiiiii: No host name returned on DNS lookup

    Explanation:

    A DNS request was executed for IP address iiiiiiii. The address lookup failed to find a host name. Because the IP name was not found, the IP name was not used to identify the node definition associated with the incoming request.

  • PGTE1911W Activity tttttttttt FUSEX06 set invalid value xxxx for parameter yyyy: using original value

    Explanation:

    The user exit FUSEX06 was invoked and an attempt was made to set an invalid value xxxx for the parameter yyyy. This is a warning message and the original value is used.

  • PGTF3111W Activity xxxx Delete Failed to: yyyy of zzzz

    Explanation:

    Delete failed to remote system.

    See previous diagnostic messages for the possible cause.

  • PGTF3508W Error=nn on gsk_fips_state_set "ON": SSL/TLS FIPS not enabled

    Explanation:

    Error code nn was detected when setting the TLS/SSL "gsk_fips_state_set" on.

    See the TLS/SSL error codes defined in Chapter 13: Messages and codes of the z/OS Cryptographic Services System Secure Sockets Layer Programming manual.

  • PGTB4111W REMOTE SYSTEM IS UNAVAILABLE

    Explanation:

    The Platform Server on the remote side is down.

  • PGTB4124W PARM STRING PARAMETER

    Explanation:

    A Platform Server parameter specified in the PARM statement of the EXEC JCL card overrides a parameter specified in the SYSIN file.

  • PGTB4125W ACTIVITY SUCCESSFULLY QUEUED AND WILL BE ELIGIBLE WHEN SERVER xxxx IS ACTIVE

    Explanation:

    This is a normal message that is displayed when a transfer is queued to a server that is not currently active.

  • PGTB4189W NODE, IPADDR, IPNAME and RUSER parameters ignored for transfer type: xxxxxxxx

    Explanation:

    The user performed a SCRIPT, REXX, or SUBMIT function and specified the NODE, IPADDR, IPNAME, or RUSER parameters. This is a warning message that indicates that these parameters are not used for a SCRIPT, RESS, or SUBMIT function. The transfer continues to execute, and these parameters are ignored.

  • PGTB4195W SCRIPT will not be throttled: Use NODE parameter to throttle execution

    Explanation:

    The user was queuing a SCRIPT, SUBMIT, or REXX EXEC to the Platform Server started task. The user did not specify the NODE parameter. When the NODE parameter is not defined, no throttling of transfers occurs. On a heavily utilized system, this can cause transfers to fail due to lack of available memory.

    Specify the NODE parameter, particularly when submitting scripts to execute. The Platform Server then uses the NODE CONTENTION_WINNERS parameter to throttle the number of transfers of this type that can be executed simultaneously.