Open topic with navigation

TIBCO® Managed File Transfer Platform Server for z/OS 8.1.0

# Information Messages

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

- PGTS0000I Another Server with the name: xxxx is active

Explanation:

Another Platform Server with the same name is already active. The second server will automatically shut down.

- PGTCB001I Activity Queued to Server: xxxxxxxxx with the following Transaction ID: tttttttttt

  Explanation:

  This message is displayed in the batch interface when a transfer is queued to the started task.

  xxxxxxxxx defines the STC name, LU name, or IP address/IP name of the started task. tttttttttt defines the transaction ID associated with the transfer.

- PGTS000I Platform Server xxxx INITIALIZED

  Explanation:

  The Platform Server signified by the xxxx has started.

- PGTS0012I OSIMSGS LOG File Freed

  Explanation:

  This is an information message that is issued in response to the RELEASE,LOG Platform Server operator command.

- PGTS0022I CPU Information: Version Code=xxxx Id Number=yyyy Model Number=zzzz

  Explanation:

  WTO to issue CPU information from the Platform Server.

- PGTS0024I Message xxxx not found

  Explanation:

  If you receive this message, contact TIBCO Support. Supply the message number that you receive as indicated by xxxx.

- PGTS0026I Platform Server Suite xxxx initialized

  Explanation:

  The Platform Server started task is starting.

- PGTS0029I Platform Advanced SNA services being [loaded | stopped]

  Explanation:

  This information message is issued at startup and shutdown.

- PGTS0031I Platform Advanced TCP services xxxx

  Explanation:

  This message states whether the TCP services is loaded or not and the reason.

- PGTS0032I [ FUSIONSNA | FUSIONTCP ] request by xxxx Denied - Application NOT authorized by GLOBAL key

  Explanation:

  This application must be authorized by applying the correct licensing key for the product in the GLOBAL member.

- PGTS0033I xxxx Locally initiated request Terminated - yyyy NOT authorized by GLOBAL key

  Explanation:

  This application must be authorized by applying the correct licensing key to the GLOBAL member.

- PGTS0034I xxxxxxxx request by yyyyyyyy Denied - Temporary key has expired

  Explanation:

  A Platform Server request was initiated by node yyyyyyyy. The request type was xxxxxxxx. The temporary key that was assigned has expired. The Platform Server no longer supports any incoming or outgoing requests.

  Contact TIBCO Support to get a new Platform Server key.

- PGTS0037I Another Server with the name xxxx is active

  Explanation:

  You attempted to bring up two Platform Server started tasks, each with the same name. This is not supported, so the second server will shut itself down immediately.

- PGTS0038I Platform Server xxxx Shutting Down

  Explanation:

  The Platform Server started task is in the process of termination. This is a normal message.

- PGTS0039I RDJFCB failed - Audit DSN not found

  Explanation:

  The audit dataset must be defined before bringing up the Platform Server started task.

  Use the DEFAUDIT member in the SAMPLELIB dataset as an example of how to define the audit dataset.

- PGTS0040I Platform Server xxxxxxxxxxxx processing stopped: Retry later

  Explanation:

  An initiator or responder request xxxxxxxx was detected by the Platform Server, but processing was quiesced by the INITIATORSTOP or RESPONDERSTOP commands. This message is meant to notify the user why a file transfer request was not processed.

- PGTS0042I Platform Server request from node nnnnnnnn exceeded contention loser max of xx: Try request later

  Explanation:

  A request was received from node nnnnnnnn. The Platform Server detected that the number of responder tasks associated with this node exceeded the LOSERS parameter defined in the node definition.

  The Platform Server sends this message back to the system that initiated the request. The request is terminated, but it can be retried at a later time.

- PGTS0047I Error opening TCPTRAC - tracing terminated

  Explanation:

  The Platform Server encountered an error trying to open the file specified in the TCPTRAC DD statement specified in the startup PROC.

  Check the contents of the DD statement to verify that they are specified correctly.

- PGTS0048I TCPTRAC DD statement opened successfully

  Explanation:

  The tracing for TCP/IP is started successfully.

- PGTS0049I TCPTRAC DD statement closed successfully

  Explanation:

  The tracing for TCP/IP is stopped successfully.

- PGTS0050I Work Queue Entry for Activity xxxx purged.

  Explanation:

  The work queue contains a transaction request that was purged. This is a normal message.

- PGTS0051I Invalid slot number for PURGEQ - xxxx

  Explanation:

  Contact TIBCO Support if you receive this message.

- PGTS0052I PURGEQ option xxxx not supported

  Explanation:

  Contact TIBCO Support if you receive this message.

- PGTS0053I Work Queue Entry address for PURGEQ is Invalid -xxxx

  Explanation:

  Contact TIBCO Support if you receive this message.

- PGTS0054I Activity xxxx for yyyy queued successfully zzzzzzzz

  Explanation:

  Activity for transaction xxxx for IP address or node yyyy was successfully queued to the started task. Parameter zzzzzzzz gives additional information about the source of the request.

  For example, on a request queued as a result of the EVERY command, by EVERY request is displayed.

- PGTS0055I Queue Entry for Activity xxxx Already in Purge KILL State - waiting for TASK termination

  Explanation:

  Someone attempted to purge activity xxxx that was already marked for purge from the work queue. No further action is necessary.

- PGTS0062I Resetting any nodes with errors

  Explanation:

  The RESETINTERVAL parameter was reached, and any nodes that were in error are now reset for transfers to be retried. This is an information message. No action is required.

- PGTS0063I STARTTCP command issued - TCP Already started: You must use TERMTCP command before restarting TCP interface

  Explanation:

  The STARTTCP operator command was issued, but the TCP interface was not stopped. No action takes place on the TCP interface.

  If you want to refresh the TCP interface, you have to issue the TERMTCP command before issuing the STARTTCP command.

- PGTS0067I Detail for xxx node nnnnnnnn

  Explanation:

  The NODE operator command is issued, and the node name to be displayed is specified as nnnnnnnn. xxxx indicates whether the display is for an SNA or a TCP. This message is followed with detailed information about the node.

- PGTS0068I iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii

  Explanation:

  The NODE operator command was issued. This message is used to display detailed information about the node that was displayed.

- PGTS0069I Error in DISABLE command syntax xxxx

  Explanation:

  An operator entered a modify DISABLE command that did not conform to the proper syntax. The correct syntax is `F servername,DISABLE,nnnnnn`, where nnnnnn is the member name in the CONFIG library.

- PGTS0070I Error in ENABLE command syntax xxxx

  Explanation:

  An operator entered a modify ENABLE command that did not conform to the proper syntax. The correct syntax is `F servername,DISABLE,nnnnnn`, where nnnnnn is the member name in the CONFIG library.

- PGTS0071I Node xxxx enabled successfully

  Explanation:

  A dynamic enable command entered by the console modify command is successfully processed.

- PGTS0072I Enable for node xxxx failed. Node already active

  Explanation:

  This message is informational only. No action is necessary.

- PGTS0073I Node xxxx not defined in Nodes PDS

  Explanation:

  There was no member xxxx in the CONFIG library.

  Verify that the node is properly defined and that you spelled the member name correctly.

- PGTS0075I Nodes entry for Remote system xxxx was not found

  Explanation:

  Contact TIBCO Support if you receive this message.

- PGTS0076I Nodes entry for Remote system xxxx was found

  Explanation:

  This message is informational only.

- PGTS0077I Select code xxxx invalid for NODEOP

  Explanation:

  Contact TIBCO Support if you receive this message.

- PGTS0085I AUTHKEY file does not contain valid Authentication key: Recreating the key

  Explanation:

  The Platform Server read the data in the AUTHKEY DD statement and determined that it was not a valid authentication key. The Platform Server creates a new authentication key and writes it in encrypted format to the AUTHKEY DD statement.

- PGTS0086I Platform Server STC using Authentication key xxxxxxxxxxxxxxxx: Use this key on Authentication config in remote Systems

  Explanation:

  The Platform Server uses the 16-digit authentication key xxxxxxxxxxxxxxxx when communicating with Platform Server systems. This key must be defined in the Platform Server system when the Platform Server authentication is required. This message is displayed at startup and as a result of the AUTHDISP operator command.

- PGTS0090I Node nnnnnnnn has been reset successfully

  Explanation:

  Node nnnnnnnn was reset by the RESET command. Additionally, any transfer request for this node was reset as well.

- PGTS0091I Node nnnnnnnn not enabled: License Key Max Nodes of xxx exceeded

  Explanation:

  The user attempted to enable node nnnnnnnn either at startup or through the ENABLE operator command but enabling this node exceeds the defined maximum number of nodes. Some companies purchase the Platform Server with a license key that defines the maximum number of node entries that can be enabled.

  If you wish to enable more nodes, contact TIBCO Support.

- PGTS0092I Queue Lookaside Initialization Found Knetwork Fusion Responder Activity xxxx. Entry is purged.

  Explanation:

  A responder entry, xxxx, was found for a Knetwork protocol transfer. These entries are not required and are therefore purged to save space.

- PGTS0093I Queue Lookaside Dataspace Being Built

  Explanation:

  This message is normal and is displayed when the Platform Server is being initialized. It means that the work queue index is built. The index is used to hasten queue searches and to reduce paging.

- PGTS0094I Queue Lookaside Initialization Found Activity xxxx active. Entry is Reset to Inactive.

  Explanation:

  A transfer was in progress when the Platform Server was last shut down. At startup time, the transfer status was reset to inactive so that it can be retried.

- PGTS0095I Queue Lookaside Initialization Found Activity xxxx Marked for purge. Entry is purged.

  Explanation:

  When the server was last shut down, it was in the process of purging a transaction from the work queue. At startup time, the initiation code found an entry that is still on the queue but marked to be removed. The initialization code completes the purge.

- PGTS0096I Queue Lookaside Initialization Found Activity xxxx Has Invalid Status

  Explanation:

  The Platform Server startup routines found an integrity error on the work queue and corrected it.

- PGTS0097I Queue Lookaside Initialization Maximum Slot number is xxxx

  Explanation:

  This message is informational only. The message is normal at startup time.

- PGTS0098I Nodes Lookaside Dataspace Being Built

  Explanation:

  The Platform Server initialization routines are building the index for the nodes topology dataspace. This is a normal message at startup time.

- PGTS0099I Queue Lookaside Initialization Found Activity xxxx Logically purged. Audit record written.

  Explanation:

  This is an information message. It means that the Platform Server initialization routines have to finish purging a work queue entry that is marked for termination but is not yet flushed.

- PGTS0100I Product xxxxxxxx will expire in nn days: Contact TIBCO Technical Support for a new Product License key

  Explanation:

  The product xxxxxxxx license key expires in nn days. This message is displayed once a day until the product license expires.

  Contact TIBCO Support to receive a new product license key.

- PGTS0101I Product xxxxxxxx has expired: Contact TIBCO Technical Support for a new Product License Key

  Explanation:

  The product xxxxxxxx license key has expired. Product xxxxxxxx will continue to run until the started task is brought down. If the product is started with an expired license key, the software will not run.

  Contact TIBCO Support to receive a new product license key.

- PGTS0102I Product xxxxxxxx expires today: Contact TIBCO Technical Support for a new Product License Key

  Explanation:

  The product xxxxxxxx license key expires today. Product xxxxxxxx will continue to run until the started task is brought down. If the product is started with an expired license key, the software will not run.

  Contact TIBCO Support to receive a new product license key.

- PGTS0103I Queue Lookaside Initialization Found Activity tttttttttt SAPI Request Purged: Audit record written

  Explanation:

  The Platform Server was starting up and found a SAPI request in the queue. The Platform Server purges any SAPI request at startup. The Platform Server SAPI interface then will check the JES spool for any requests.

- PGTS0106I Starting TLS Task using IPPORT nnnnn

  Explanation:

  The Platform Server is configured to use TLS/SSL. This message shows the IPPORT that the Platform Server listens on for incoming TLS/SSL requests.

- PGTS0107I Purge SAPI Transaction tttttttttt for Node nnnnnnnn: Node entry not found - Transaction purged

  Explanation:

  The Platform Server has completed a SAPI request and is attempting to find the node definition to notify it that the SAPI request is completed. The Platform Server is unable to find the node definition associated with the request. The transfer request continues, but the node definition is not found. This message is displayed for information purposes only.

- PGTS0108I Purge SAPI Transaction tttttttttt for Node nnnnnnnn: SAPI Request not pending - Transaction purged

  Explanation:

  The Platform Server has completed a SAPI request and is attempting to find the node definition to notify it that the SAPI request is completed. The Platform Server finds the node definition associated with the request, but the node definition does not indicate that a SAPI request is pending. The transfer request continues, but the node definition is not posted. This message is displayed for information purposes only.

- PGTS0109I Starting Platform Server SAPI Interface

  Explanation:

  This message indicates that the Platform Server SAPI interface is starting as a result of the GLOBAL SAPI_INTERFACE parameter being set to YES.

- PGTS0110I Platform Server SAPI Interface Terminating

  Explanation:

  This message indicates that the Platform Server SAPI interface is terminating. Termination is done only when the Platform Server is terminated.

- PGTS0112I Platform Server COLD start: All requests on the WORKQ will be purged

  Explanation:

  The `START=COLD` option is entered on the Platform Server started task EXEC PARM JCL statement. This is an information message that tells the user that all requests on the WORKQ are deleted because of the cold start request.

- PGTS0113I Platform Server COLD start: Activity tttttttttt purged from the Work Queue

  Explanation:

  The `START=COLD` option is entered on the Platform Server started task EXEC PARM JCL statement. This is an information message that tells the user that transaction tttttttttt has been purged from the WORKQ because of the cold start request.

- PGTS0114I COS Display Summary: nn entries displayed

  Explanation:

  The Platform Server COS operator command was entered without any additional values. This command causes a summary of all the enabled COS entries to be displayed. This message is displayed after the last COS entry and shows how many COS entries are enabled.

- PGTS0116I COS Name=cccccccc SBUFSIZE=ssss RBUFSIZE=rrrr

  Explanation:

  This message shows the summary information for COS entry cccccccc. It shows the SBUFSIZE and RBUFSIZE values entered for the COS entry.

- PGTS0117I aa bb cc dd ee ff gg hh

  Explanation:

  The Platform Server COS operator command was entered with a specific COS entry. This command displays the detailed information associated with an enabled COS entry. All of the information available for this COS entry is displayed using this message.

- PGTS0119I ttttt member nnnnnnnn: not enabled due to AUTOENABLE=NO

  Explanation:

  The CONFIG DD in the startup JCL points to member nnnnnnnn in the node configuration library. But member nnnnnnnn is not activated because it is defined with `AUTOENABLE=NO`.

  This message is for information purposes only. ttttt defines the type of member that is not enabled.

- PGTS0122I Hardware Encryption support: mmmmmmmmmmmmmm

  Explanation:

  This message is displayed at startup when the ENCRYPT operator command is executed. It describes the hardware encryption capabilities that are supported. When supported by the hardware, the Platform Server uses hardware encryption when using AES256 and AES128.

- PGTS0123I Queue Lookaside Initialization Found Activity with invalid TransId: Record purged and audit not written

  Explanation:

  During the Platform Server started task initialization, it detects a request in its WORKQ that does not have a valid initiator or responder transaction ID. The request is removed from the WORKQ. Because the request is not formatted properly, a record is not written to the audit log.

- PGTS0125I TLS Interface Terminating

  Explanation:

  This is an information message that is displayed when the TLS interface is terminating.

- PGTS0126I TLS Initialize Successful: Accepting TLS/SSL Requests

  Explanation:

  This is an information message that is displayed when the TLS interface initialization completes successfully and accepts TLS connections.

- PGTS0127I ZLIB/TLS Start Failed: Service already started

  Explanation:

  This is an information message that is displayed when the ZLIB/TLS environment is starting, but the Platform Server code detected that the interface has already started.

- PGTS0129I TLS Interface Shutdown complete

  Explanation:

  This is an information message that is displayed when the TLS Interface has terminated successfully.

- PGTS0131I ZLIB/TLS Shutdown Failed: Environment not started

  Explanation:

  Platform Server attempted to stop the ZLIB/TLS environment, but the shutdown failed because the ZLIB/SSL environment was already stopped.

- PGTS0132I ZLIB Compression/TLS Interface started successfully

  Explanation:

  This is an information message that is displayed when the ZLIB/TLS environment has started successfully.

- PGTS0133I ZLIB Compression/TLS interface starting

  Explanation:

  This is an information message that is displayed when the ZLIB/TLS environment is initializing.

- PGTS0147I Queue is Full, Transfer Request Denied

  Explanation:

  The work queue is full and cannot accept any more requests. The server must be stopped. The work queue VSAM file must be backed up, deleted, and redefined with more space.

- PGTS0148I Activity xxxx Expired and will be deleted from work queue

  Explanation:

  This message indicates that a work queue item has an expiration date that is earlier than the current date. Therefore, the Platform Server dispatcher will purge it from the work queue.

- PGTS0149I Platform Server Initiator Dispatcher Active

  Explanation:

  This is an information message only. The Platform Server has attached a dispatcher task, which continuously scans the work queue looking for activities that are eligible to be initiated. When the dispatcher finds an activity, it attaches transmission subtasks to perform the activity, for example, to transfer a file.

- PGTS0150I Beginning Scan of Work Queue for Initiator Activities

  Explanation:

  The Platform Server dispatcher is beginning to look at the work queue entries for work to initialize.

- PGTS0151I Max Retries Exceeded - Deleting Activity xxxx from work queue

  Explanation:

  An activity has been queued with a non-zero limit specified for the number of retries. This limit is reached so the dispatcher purges the activity from the work queue instead of dispatching it.

- PGTS0152I Initiator Now Waiting after scan of Work Queue

  Explanation:

  The Platform Server dispatcher completes its scan of the work queue and becomes dormant until the new cycle time expires or until new entries are queued.

- PGTS0153I Wake up and scan initiator Work Queue again

  Explanation:

  The new cycle timer has stopped, and the dispatcher resumes looking for work items to dispatch.

- PGTS0155I Platform Server Initiator Dispatcher shutting down normally

  Explanation:

  This message indicates that the Platform Server is being shut down. This is a normal message.

- PGTS0173I PURGE command successful for Activity xxxx

  Explanation:

  The purge command is successfully executed to remove an activity from the work queue.

- PGTS0174I DELETE command successful for Activity xxxx

  Explanation:

  The delete command is successfully executed to remove an activity from the work queue.

- PGTS0175I HOLD command successful for Activity xxxx

  Explanation:

  The console hold command places an activity in Hold status on the work queue.

- PGTS0176I RELEASE command successful for Activity xxxx

  Explanation:

  The console release command moves an activity on hold to release status on the work queue.

- PGTS0177I SUSPEND command successful for Activity xxxx

  Explanation:

  The console suspend command puts an activity to suspend status on the work queue.

- PGTS0178I Activity tttttttttt purged: Platform Server EVERY request has exceeded parameter EVERY_COUNT=ccccc

  Explanation:

  A Platform Server request was queued that used the EVERY parameter and the EVERY_COUNT parameter to limit the number of requests that could be scheduled. This message indicates that the EVERY_COUNT limit is reached. The EVERY request is purged from the queue.

- PGTS0181I Activity xxxx has completed

  Explanation:

  The Platform Server finished processing an activity from the work queue.

- PGTS0187I SECAUDIT command successful

  Explanation:

  The SECAUDIT modify command was issued and processed successfully.

- PGTS0192I Responder Activity xxxx purged from Queue

  Explanation:

  The indicated transaction is deleted from the queue. This is a normal message.

- PGTS0193I Responder Activity xxxx remains in Queue awaiting Checkpoint restart

  Explanation:

  This transaction which was set up using checkpoint restart was interrupted. It starts again from the last checkpoint and puts back on the queue awaiting restart.

- PGTS0199I Activity tttttttttt Transfer Nodeclass (nn) exceeds NODE WINNERS (ww): Request set to error

  Explanation:

  The NODECLASS parameter entered exceeds the NODE WINNERS parameter. The transfer cannot run successfully. The transfer request is set to an error state.

  Either change the transfer NODECLASS to a number less than or equal to the NODE WINNERS parameter, or increase the WINNERS parameter to be as large as the transfer NODECLASS.

- PGTS0205I Platform Server xxxxxxxxxx processing has been stopped

  Explanation:

  xxxxxxxxxx represents either an INITIATORSTOP or RESPONDERSTOP command that the Platform Server received. This message indicates that processing is stopped.

- PGTS0206I Platform Server xxxxxxxxxx processing has been started

  Explanation:

  xxxxxxxxxx represents either an INITIATORSTOP or RESPONDERSTOP command that the Platform Server received. This message indicates that processing is started.

- PGTF0207I MQ Load Error on module xxxxxxxx: MQ SCSQLOAD/SCSQAUTH must be in STEPLIB - MQ processing disabled

  Explanation:

  The Platform Server is attempting to load MQ module xxxxxxxx, but it received a load error. This is typically because the MQ SCSQLOAD and SCSQAUTH libraries are not in the Platform Server STEPLIB.

  This is an information message that indicates that MQ support is disabled. This has to be treated as a problem only if you want the Platform Server to process MQ data. Otherwise this message can be ignored.

- PGTF0208I Load Error on module mmmmmmmm: SYS1.CSSLIB must be in STEPLIB when using UNICODE services: Services disabled

  Explanation:

  Platform Server attempted to load code conversion module mmmmmmmm but the load failed. Any UNICODE code conversion performed by specifying a local conversion table starting with "CC:" fails.

  Make sure that SYS1.CSSLIB is in the STC STEPLIB or in the MVS LNKLST module.

- PGTF0212I tttttttttt Transfer set to Inactive state due to COS cccccccc priority=yy

  Explanation:

  The Platform Server is scanning WORKQ to find transfers to run and finds transfer tttttttttt ready to run. However, when checking its COS entry `cccccccc`, the Platform Server dispatcher finds that the priority for this transfer is 0 or 1. In this case, the Platform Server cannot start the transfer. The transfer is put in an inactive error state so that the transfer is not checked again until the errors are reset.

- PGTF0213I tttttttttt Transfer held due to NODE nnnnnnnn INITHOLD=YES: Use the INITREL command to release the HOLD

  Explanation:

  A transfer is ready to be initiated for node nnnnnnnn. However, the node has been placed in an INITHOLD status, so no transfers can be initiated to this node.

  You can issue the INITREL operator command or the ISPF panels to release the hold and make transfers can be initiated to this node.

  This message is displayed approximately every minute as a reminder that the node is in hold state.

- PGTF0214I INITHOLD complete for Node nnnnnnnn: Initiator requests will be stopped: uuuuuuuu

  Explanation:

  An INITHOLD request was received for node nnnnnnnn. uuuuuuuu defines whether this request is initiated through an operator command or through the ISPF panels. No transfers will be initiated to this node.

  Issue the INITREL operator command or use the ISPF panels to release the hold and transfers can be initiated to this node.

- PGTF0215I INITREL complete for Node nnnnnnnn: Initiator requests will start and the error count has been reset: uuuuuuuu

  Explanation:

  An INITREL request was received for node nnnnnnnn. uuuuuuuu defines whether this request is initiated through an operator command or through the ISPF panels. INITHOLD is cleared and transfers will be initiated to this node.

- PGTF0216I RESPHOLD complete for Node nnnnnnnn: Responder requests will be rejected: nnnnnnnn

  Explanation:

  A RESPHOLD request was received for node nnnnnnnn. uuuuuuuu defines whether this request is initiated through an operator command or through the ISPF panels. No transfers are responded from this node. Responder requests from this node will be rejected with a recoverable network error.

  You can issue the RESPREL operator command or use the ISPF panels to release the hold and make transfers can be accepted from this node.

- PGTF0217I RESPREL complete for Node nnnnnnnn: Responder requests will be accepted: uuuuuuuu

  Explanation:

  A RESPREL has been received for node nnnnnnnn. uuuuuuuu defines whether this request is initiated through an operator command or through the ISPF panels. RESPHOLD is cleared and transfers can be accepted from this node.

- PGTF0218I TLSSTOP Completed

  Explanation:

  The operator executed the TLSSTOP command to stop the TLS services. The TLS service is stopped successfully.

- PGTF0223I MODVER: Module: mmmmmmmm Date: MM/DD/YY Time: HH:MM Level: LLLLLLL

  Explanation:

  The user entered the MODVER operator command for module mmmmmmmm. This message shows the date and time when the module was compiled along with the hotfix level.

- PGTF0228I ZEDCSTAT: ZEDC Interface is mmmmmmmm: TLS Interface is nnnnnnnn

  Explanation:

  The operator entered the ZEDCSTAT command. This message shows the status of the ZEDC interface and the TLS interface. The status is either active or inactive.

- PGTS0234I Message dataset closed

  Explanation:

  This is a normal message that is displayed during shut down of the started task.

- PGTS0235I Audit dataset closed

  Explanation:

  This is a normal message that is displayed during shut down of the started task.

- PGTS0252I User Profile for local user: uuuuuuuu node: nnnnnnnn changed to remote user: rrrrrrrr

  Explanation:

  User uuuuuuuu queues a transfer and specifies that user profiles must be used. The Platform Server started task substitutes user ID rrrrrrrr for the request to node nnnnnnnn. This message is displayed for information reason only.

- PGTS0258I Local user uuuuuuuu pppppppp PROFILE for node: nnnnnnnn remote user: rrrrrrrr successful using AES256

  Explanation:

  The FUSPROF utility successfully processes request type pppppppp for local user uuuuuuu and remote node nnnnnnnn. Remote user rrrrrrrr is substituted when the user performs a request to this node.

- PGTS0259E Local user uuuuuuuu ADD PROFILE for node: nnnnnnnn failed - no slots left on dataspace

  Explanation:

  The FUSPROF utility attempts to add a user profile to the profile dataspace, but no space is left on the user profile dataspace.

  Use the PROFILEQ parameter of the started task PARM statement to add more slots on the dataspace.

- PGTS0260I Local user uuuuuuuu DELETE PROFILE for node: nnnnnnnn successful

  Explanation:

  The FUSPROF utility successfully deleted the user/node combination from the profile dataspace. uuuuuuuu defines the user ID while nnnnnnnn defines the node name.

- PGTS0262I User Profile for Remote user: rrrrrrrr xxxxxx: iiiiiiiiii changed to local user: llllllll

  Explanation:

  A remote user profile was detected for remote user rrrrrrrr. xxxxxx: iiiiiiii shows the node information. The user is changed to user ID llllllll. The file transfer request runs under the authorization of local user ID llllllll. This message is for information purposes only to show that a remote user profile is used.

- PGTS0263I Remote user rrrrrrrr DELETE PROFILE for node: nnnnnnnn successful

  Explanation:

  The FUSPROF utility successfully deleted a profile for remote user rrrrrrrr and node nnnnnnnn. This message is displayed only when `RESPONDER=YES` is entered on the FUSPROF DELETE parameter statements.

- PGTS0269I Activity tttttttttt has been purged by user exit FUSEX06

  Explanation:

  User exit FUSEX06 is invoked and has purged the activity tttttttt. Return code of 8 upon return from the exit indicates that the activity is to be purged.

- PGTS0802I SMF Record Type xxxx written for Activity yyyy

  Explanation:

  This message simply informs you that an SMF record is written for the indicated activity.

- PGTS0818I AUDIT file is now 80 percent full

  Explanation:

  This is an information message which warns that the audit dataset is filled by 80 percent. This message is displayed so that the started task can be stopped and the audit file can be backed up before the audit file wraps to the start of the audit dataset.

- PGTS0819I AUDIT file exceeds max slots of xxxx - wrapping to the start of the AUDIT file

  Explanation:

  The audit dataset is already filled and audit records are now being written to the start of the dataset.

- PGTS0820I Performing LOGSNAP to DD SNAPLOG

  Explanation:

  A snap dump is being taken. It is sent to the dataset that is defined in the SNAPLOG DD statement in the started task PROC.

- PGTS0821I LOGSNAP Dump Complete

  Explanation:

  A snap dump has been taken and is now complete.

- PGTS0823I LOGSNAP Log address range: xxxx Vector address range: yyyy Log STOKEN=zzzz

  Explanation:

  This is an information message used for debugging purposes.

- PGTS0825I Audit File full - Wrapping to record 1

  Explanation:

  The audit file is full and wraps around to record 1 to start overwriting the file.

- PGTS0826I Audit File full - Unable to wrap to record 1 - no additional records will be written

  Explanation:

  The audit file is full and unable to wrap around to overwrite the file. Auditing is stopped.

- PGTS0930I NodeName | LUName/IPAddr/IPName | Mode/Port | ParSess | Winners/Losers | State

  Explanation:

  The node operator command was entered to display summary information about enabled node definitions. This is a heading message and is accompanied by message PGTS0931I to display the summary information about each enabled node.

- PGTS0931I nnnnnnnn | iiiiiiii | mmmmmmmm | ppp | www/lll | sss

  Explanation:

  The node operator command was entered to display summary information about enabled node definitions. This message is displayed for each node that is enabled and shows the summary information about the node.

  Where:

  - nnnnnnnn defines the node name.
  - iiiiiiii defines the LU name, IP name, or IP address.
  - mmmmmmmm defines the SNA mode or IP port.
  - ppp, www, and lll define parallel sessions parameters.
  - sss defines current state of the node.
- PGTS0978I Platform Server dispatcher shutting down

  Explanation:

  This is a normal message that appears during shutdown of the started task.

- PGTS0979I Active transmissions detected during dispatcher shutdown

  Explanation:

  This message is displayed when some transfers are currently active during shutdown of the started task.

- PGTS0980I Max Retries of xxxx Exceeded - Activity yyyy to be Deleted

  Explanation:

  This message indicates that an initiator transfer request was terminated because the max try count of xxxx was exceeded. The transfer is terminated with an error, and a failure audit record is written.

- PGTS0982I Initiator Dispatcher Starting to Scan the Work Queue

  Explanation:

  The Platform Server is initialized and is scanning the work queue to check if there are any activities to process. Transactions set to active are released.

- PGTS0983I Console Display Command to Server xxxx is yyyy (zzzz)

  Explanation:

  This message is displayed after the modify display command is issued correctly.

- PGTS0984I Console Display Command Processor Completed Successfully

  Explanation:

  This message is displayed upon successful completion of the modify command.

- PGTS0986I There are xxxx Activities in the Work Queue for Server yyyy

  Explanation:

  This message is displayed when the modify display command is issued. xxxx is the number (in hex) of activities in the work queue for the Platform Server specified.

- PGTS0987I Process==Activity==Status==Node==UserId==Start Date==Start Time

  Explanation:

  This is a header message with column titles. It is issued along with message PGTS0986I and PGTS0988I.

- PGTS0988I xxxx yyyy zzzz aaaa bbbb

  Explanation:

  This message is issued along with message PGTS0986I and PGTS0987I. It displays specific information about each entry in the work queue.

- PGTS0989I Console Node Query to Server xxxx is yyyy (zzzz)

  Explanation:

  This message is received when a modify query is done on a node.

- PGTS0990I Console Node Query Processor Completed Successfully

  Explanation:

  This message is received when a modify query is done on a node and is completed successfully.

- PGTS0995I Ambiguous command received, please re-enter

  Explanation:

  This command is not acceptable to the remote system. Check with the support staff of that computer to determine a valid command to use.

- PGTS0996I Stop command being processed

  Explanation:

  This is a normal message that is displayed during the shutdown of the started task.

- PGTS0997I Platform Server Suite dataspace initialization complete

  Explanation:

  This is a normal message that is displayed during the startup of the started task.

- PGTS0998I Platform Server Suite Cross Memory Services environment setup successfully completed

  Explanation:

  This is a normal message that is displayed during the startup of the started task.

- PGTS0999I Platform Server Suite deleting dataspaces

  Explanation:

  This is a normal message that is displayed during the shutdown of the started task.

- PGT1002I TLV VARIABLE XXXX NOT FOUND IN TLV TABLE

  Explanation:

  Platform Server was validating incoming control information and found an unexpected parameter. This could be caused by a partner Platform Server running a different release.

  If this affects the execution of a Platform Server transfer, contact TIBCO Support.

- PGTS1047I xxxx key validated - expiration date is YYYYDDD

  Explanation:

  This is a normal message. It is displayed at startup.

- PGTB1099I INVALID/MISSING SERVER PARM DEFAULT USED

  Explanation:

  Check your GLOBAL definitions and correct the error.

- PGTA1101I Transmission subtask terminating due to shutdown

  Explanation:

  If the shutdown command is entered when a transmission is in progress, this message is displayed.

- PGTS1132I xxxx member activated successfully

  Explanation:

  This is an information message that is displayed when a node definition is enabled successfully.

- PGTS1148I xxxx disabled successfully

  Explanation:

  The modify command disables the member specified successfully.

- PGTS1161I LIST xxxx ACTIVATES SUCCESSFULLY WITH yyyy ENTRIES

  Explanation:

  List xxxx is activated successfully. yyyy indicates how many NODE, IPADDR, or IPNAME definitions are associated with the list.

- PGTA1200I Purging Queue Entry xxxx

  Explanation:

  The queue entry xxxx is marked for termination.

- PGTA1201I Activity xxxx not processed

  Explanation:

  The activity xxxx cannot be processed at this time. It is marked inactive and placed back on the work queue.

- PGTA1202I Transmission Subtask Processing Initiator for Transaction xxxx - Remote System yyyy

  Explanation:

  The dispatcher has successfully attached an MVS subtask to initiate the xxxx activity. This is a normal message that is displayed when a file transfer is dispatched.

- PGTS1203I Invalid xxxx:yyyy for Activity: zzzz Purging Queue Entry

  Explanation:

  Contact TIBCO Support if you receive this message.

- PGTA1209I tttttttttt Writing Audit record for Temporary error

  Explanation:

  A file transfer completed with a recoverable error and is retried at a later time. The GLOBAL AUDIT_TEMP_ERRORS is set to YES, so the Platform Server is writing an audit and/or SMF record. This is an information message and is written only to the Platform Server log file.

- PGTA1215I xxxx

  Explanation:

  Contact TIBCO Support if you receive this message.

- PGTA1216I Maximum number of concurrent Activities reached - No blocks available

  Explanation:

  The Platform Server has reached the maximum number of concurrent transactions. Some transactions cannot start until others end.

- PGTA1217I VTAM Control blocks not deleted - address not found

  Explanation:

  An error occurs when trying to delete the VTAM control block.

- PGTA1218I xxxx yyyy zzzz - Activity will be placed on HOLD

  Explanation:

  Transaction xxxx will be placed on hold because action yyyy is in zzzz status.

- PGTS1300I Requested Access function xxxx not supported

  Explanation:

  Contact TIBCO Support if you receive this message.

- PGTS1376I REQUIRE_NODE_DEFINITON set to YES,YES due to License Key Max Node=yyyy

  Explanation:

  The Platform Server automatically set the GLOBAL REQUIRE_NODE_DEFINITION parameter to YES because the license key indicated a limited version of the Platform Server, thus limiting the number of NODE definitions. In this case, the Platform Server requires that NODE definitions are defined for both initiator and responder requests.

  Correct this parameter and restart the Platform Server started task.

- PGTS1377I DEFAULT_COSNAME must be 1 to 8 characters

  Explanation:

  The value entered for the DEFAULT_COSNAME parameter in the GLOBAL member was incorrect. The valid values must be between 1 and 8 characters.

  Correct this parameter and restart the Platform Server started task.

- PGTS1378I PDS_SPACE_RELEASE must be YES or NO

  Explanation:

  The value entered for the PDS_SPACE_RELEASE parameter in the GLOBAL member was incorrect. The valid values are YES and NO.

  Correct this parameter and restart the Platform Server started task.

- PGTS1379I DEFAULT_RECEIVE_DISP must be CREATE, CREATE_REPLACE, CREATE_APPEND, REPLACE, or APPEND

  Explanation:

  The value entered for the DEFAULT_RECEIVE_DISP parameter in the GLOBAL members was incorrect. The valid values are CREATE, CREATE_REPLACE, CREATE_APPEND, REPLACE, and APPEND. Correct this parameter and restart the Platform Server started task.

- PGTS1380I EXTENDED_SECURITY_RESOURCE must be from 1 to 8 characters

  Explanation:

  The value entered for the EXTENDED_SECURITY_RESOURCE parameter in the GLOBAL member is incorrect. The valid values must be between 1-character to 8-character long.

  Correct this parameter and restart the Platform Server started task.

- PGTS1381I EXTENDED_SECURITY_CHECK must be ENFORCE/WARN/NO,ENFORCE/WARN/NO

  Explanation:

  The value entered for the EXTENDED_SECURITY_RESOURCE parameter in the GLOBAL member was incorrect. This parameter has two sub-parameters. The first sub-parameter defines whether to check if the user is authorized to use the Platform Server, while the second parameter determines if the user is authorized to access the node definition or IP address. The valid values for each sub-parameter are ENFORCE, WARN, or NO.

  Correct this parameter and restart the Platform Server started task.

- PGTS1394I MFT Platform Server for zOS running in FIPS140 mode

  Explanation:

  The GLOBAL_ENFORCE_SECURITY_POLICY parameter was set to FIPS140 or TLSFIPS. This message indicates that the necessary cryptographic hardware is installed and FIPS mode is enabled. This message is for information purposes only.

- PGTS1406I XXXXXXXX Marked as Pending Disable: Disable will complete when SAPI request terminates

  Explanation:

  The Platform Server does not disable the node when a SAPI request is pending. When the SAPI request is completed, either successfully or unsuccessfully, the node will be disabled.

- PGTS1530I SSL_MESSAGE_QUEUE_NUMBER is no longer used - Ignored

  Explanation:

  The GLOBAL parameter SSL_MESSAGE_QUEUE_NUMBER is no longer used. This is an information message indicating that the parameter is ignored.

- PGTS5900I xxxx

  Explanation:

  An internal error occurred.

  Contact TIBCO Support.

- PGTT1601I LOGON exit entered for LU xxxx Mode yyyy

  Explanation:

  This is an informational message. It is issued at the start of a LU 6.2 transaction.

- PGTT1602I TPEND exit entered

  Explanation:

  This is an information message.

- PGTT1603I Bind Received for Independent LU=xxxx MODE=yyyy

  Explanation:

  This message is issued when the Platform Server receives a bind from the LU specified in the message.

- PGTT1604I ATTN exit entered TYPE=xxxx LU=yyyy MODE=zzzz

  Explanation:

  The Platform Server VTAM attention exit is driven for attention type xxxx for logical unit yyyy using mode name zzzz.

- PGTT1605I ATTN exit entered for unknown type=xxxx

  Explanation:

  The Platform Server VTAM attention exit is driven for an unknown attention type xxxx.

- PGTT1609I xxxx ACB opened successfully - executing on VxRyMz

  Explanation:

  This is an information message. This indicates that the server is able to open the ACB successfully. This message also gives information about the version of VTAM that the Platform Server is executing on.

- PGTT1612I ACB xxxx closed successfully

  Explanation:

  This is an information message that indicates that the ACB is closed successfully.

- PGTT1624I Non-LU6.2 CINIT Received for LU:xxxx MODE:yyyy - Changing Bind to LU 6.2 - zzzz

  Explanation:

  A CINIT is received from VTAM that is a non-LU 6.2 CINIT. The Platform Server changes the bind to specify LU 6.2.

- PGTT1625I Non LU 6.2 BIND Received for LU:xxxx MODE:yyyy - Terminating Session Request

  Explanation:

  A non-LU 6.2 bind is received. The Platform Server is terminating the session.

- PGTT1632I ACB xxxx Open failed ACBERFLG=yyyy Continuing without VTAM due to Operator request

  Explanation:

  There is a failure opening the ACB for this started task.

  Make sure the ACB listed here is varied active.

- PGTT1633I ACB xxxx Open failed ACBERFLG=yyyy Ending started task due to Operator request

  Explanation:

  There is a failure opening the ACB for this started task.

  Make sure the ACB listed here is varied active.

- PGTT1634I Bind Image Sent: iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii

  Explanation:

  The VTAM LOGON exit is invoked. After scanning the CINIT request, it is detected that the bind image in the CINIT is not an LU6.2 bind. This message indicates that the bind image is overridden and displays the bind image that is sent to the session partner. This message is displayed along with message PGTT1624I.
- PGTT1663I CNOS Winner/Loser/Total sessions defined as xx/xx/xx - negotiated to yy/yy/yy for LU xxxx yyyy'

  Explanation:

  During the session negotiation, the number of contention winners, contention losers, and the total sessions defined in the remote node definition (indicated by xx/xx/xx) are negotiated to yy/yy/yy with the partner LU xxxx and mode name yyyy.

- PGTT1664I tttttttttt SNA COSNAME=cccccccc SendBuffSize=xxxx RecvBuffSize=yyyyy

  Explanation:

  This message is displayed at the start of the Platform Server file transfer when SNA communication detects a COS entry for the file transfer request. It is displayed for information purposes only and displays the size of the SEND and RECEIVE buffers associated with a file transfer request.

- PGTT1665I tttttttttt Send RUSize=xxxxx Receive RUSize=yyyyy mmmmmmmm

  Explanation:

  This message is displayed at the start of the Platform Server file transfer when SNA communication is used. It is displayed for information purposes only and displays SEND and RECEIVE RU Sizes associated with a session. When available, the SNA mode name is also displayed.

- PGTV1697I xxxx

  Explanation:

  Debug message for internal use.

- PGTV1700I Error in FUSVTAM - Transfer Terminating

  Explanation:

  The program FUSVTAM has encountered a problem that causes the transaction to terminate.

- PGTV1701I Contents of FUS_RC_Return Code: xxxx

  Explanation:

  This message is used for debugging purposes.

- PGTV1702I Contents of FVCOMM_Return_Code: xxxx

  Explanation:

  This message is used for debugging purposes.

- PGTV1703I Contents of FUS_RC_Status: xxxx

  Explanation:

  This message is used for debugging purposes.

- PGTV1704I Contents of FUS_RC_VTAM: xxxx

  Explanation:

  This message is used for debugging purposes.

- PGTV1705I Contents of FUS-RC_Storage: xxxx

  Explanation:

  This message is used for debugging purposes.

- PGTV1712I TCP INITAPI successful for TCP STC xxxx - ASID yyyy

  Explanation:

  This is an information message that can also be used for debugging purposes.

- PGTT1717I TCP Responder Terminated for TCP Job xxxx in ASID yyyy

  Explanation:

  This is a normal termination message.

- PGTT1719I TCP ASID xxxx now Listening on Port yyyy to TCP job zzzz

  Explanation:

  This is a normal message that is displayed when the started task is set up to use TCP/IP. It states the started task name, the port it is listening on, and the name of the TCP/IP job running on the system.

- PGTT1721I TCP ASID xxxx NOT Listening on Port yyyy to TCP job zzzz

  Explanation:

  This message is displayed when the started task is not set up to use TCP/IP. It states the started task name, the port, and the name of the TCP/IP job running on the system.

- PGTT1722I IP request received from IP Addr: xxxx

  Explanation:

  A request is received for a transfer using the IP address xxxx.

- PGTS1733I TCP RESPONDER WAITING FOR SUBTASKS TO END BEFORE QUIESCE

  Explanation:

  This message is displayed when there is a request to shut down the Platform Server while transactions using TCP/IP that are still active. When the transactions are completed, the Platform Server shuts down.

- PGTT1731I TCP Responder Program Terminating

  Explanation:

  This is a normal message that is displayed when the started task is brought down.

- PGTT1736I SNMP TRAP errors exceed xxxx: TRAP processing disabled

  Explanation:

  The Platform Server receives an error continuously for 10 times during sending a TRAP. The TRAP feature becomes disabled, and no more TRAPs are sent.

- PGTT1737I TCP IUCV interface used: TCP version V3R1

  Explanation:

  When the Platform Server comes up, it dynamically determines the version of TCP that is running. This is done because the interface changes between TCP version 3.1 and 3.2. This message indicates that the started task has detected that TCP 3.1 is running, and therefore, the IUCV interface is used.

- PGTT1738I TCP HPNS interface used: TCP version V3R2 or greater

  Explanation:

  When the Platform Server comes up, it dynamically determines the version of TCP that is running. This is done because the interface changes between TCP version 3.1 and 3.2. This message indicates that the started task has detected that TCP 3.2 is running, and therefore, the HPNS interface is used.

- PGTT1740I TCPIP STC xxxxxxxx has been restarted: You must enter TERMTCP/STARTTCP commands to activate the TCP interface

  Explanation:

  The started task has determined that the TCP/IP started task xxxxxxxx has been restarted. The TCP interface must be restarted by using the TERMTCP and STARTTCP operator commands or by restarting the started task.

- PGTT1743I tttttttttt TCP COSNAME=cccccccc SendBuffSize=xxxx RecvBuffSize=yyyy

  Explanation:

  This message is displayed at the start of the Platform Server file transfer when TCP communications detects a COS entry for a file transfer request. It is displayed for information purposes only and displays the size of the SEND and RECEIVE buffers associated with the file transfer request.

- PGTT1744I tttttttttt TCP Node=nnnnnnnn Total=xxxx Send=yyyy Recv=zzzz Init=aaaa Resp=bbbb Bytes Per Second(BPS)

  Explanation:

  A Platform Server transfer is being performed for a node. The BPS_xxxx parameters are set within the node definition to throttle the throughput of file transfers. This message displays the different values that are defined to limit throughput. This message is displayed for information purposes only.

- PGTT1745I tttttttttt TCP xxxxxx COSNAME=cccccccc PacketSize=yyyy MAXBPS=mmmm Prty=zz

  Explanation:

  A Platform Server transfer is being performed for a node. The BPS_xxxx parameters were set within the node definition to throttle the throughput of file transfers. This message displays the packet size that is being used and the maximum BPS that is used for this request. If the number of concurrent transfers with a node changes, this message is displayed again, because the MAXBPS value is re-computed when the concurrent number of transfers with a node changes. This message is displayed for information purposes only.

- PGTT1746I Executing the following command to ssssssss the TCP interface: ccccccccccccccc

  Explanation:

  The Platform Server detects that the TCP/IP started task has changed. Most likely, this is because the TCP/IP started task has been brought down and up again. The Platform Server automatically stops and starts its TCP/IP interface by executing a Platform Server operator command. The command that is executed is displayed as ccccccc.

- PGTT1750I TCP TRACE Enabled for: nnnnnnnnnn

  Explanation:

  A TCP trace is enabled for a node, IPv4 address, or IPv6 address.

- PGTT1756I TCPTRAC ALREADY TURNED OFF

  Explanation:

  The `TCPTROFF` command is entered to turn off tracing for a node or IP address. However, tracing is already turned off.

- PGTT1757I TCP TRACE FACILITY CLOSED

  Explanation:

  The trace file is closed as a result of the `TCPTROFF` command.

- PGTT1758I TCP TRACE FACILITY ENABLED

  Explanation:

  TCP tracing is enabled because of the `TCPTRON` command or the TRACE parameter on a batch request.

- PGTT1760I TCPTRAC turned off for: nnnnnnnnnn

  Explanation:

  Because of the execution of the `TCPTROFF` operator command, tracing is turned off for a node or IP address.

- PGTT1761I DNS Name lookup: IP Name=nnnnnnnnn IP Address=iiiiiiiiiii

  Explanation:

  A DNS request is executed for IP name nnnnnnnn. The name is resolved to IP address iiiiiiii. Note that the IP address can be an IPv4 or IPv6 address.

- PGTT1762I DNS Address lookup: IP Address= IPV6 or IPV6 address IP Name=nnnnnnnnnn

  Explanation:

  A DNS request is executed for IP address iiiiiiii. The address is resolved to IP name nnnnnnnn. All responder requests attempt to resolve the IP name from the incoming IP address. This IP name is used to identify the node definition associated with the incoming request.

- PGTE1912I Activity tttttttttt has been updated by user exit FUSEX06

  Explanation:

  The user exit FUSEX06 is invoked, and it updates parameters in the queue entry for the activity tttttttt. The return code 1 upon return from the exit indicates that the activity is updated.

- PGTF2105I Activity xxxx failed due to Unknown error on transfer with remote system: yyyy

  Explanation:

  The activity xxxx fails because of an unknown error with the remote system. yyyy denotes the remote system.

- PGTS2127I Activity xxxx with Node yyyy purged due to Security Error on FMH5

  Explanation:

  The transfer request is purged because of a security error.

  Check the user ID and password used for this transfer.

- PGTF2128I Command Activity xxxx successfully executed on Remote system: yyyy

  Explanation:

  The `xxxx` command is successfully executed on the remote systems denoted by yyyy.

- PGTF2129I Connection terminated with Node xxxx Request purged from queue

  Explanation:

  The transfer request is purged because the connection to the remote system is terminated.

- PGTF2130I Premature Termination with Node xxxx Activity yyyy Purged from Queue

  Explanation:

  The transfer request is purged because the connection to the remote system is terminated.

- PGTF2131I Activity xxxx Fusion connection failure - Attempting connection with KNFusion application

  Explanation:

  If no APPLICATION parameter is stated in the transfer job or the node definition, then Fusion FTMS attempts a connection with the Fusion FTMS protocol. If this fails, then the KNFusion protocol is attempted.

- PGTF2132I Activity xxxx failed with Remote node yyyy record would be truncated

  Explanation:

  The record length of the file is larger than the record length stated in the transfer job. Therefore, if the file is transferred, the records are truncated.

- PGTE2199I xxxx

  Explanation:

  This is a debug message for platform internal use.

- PGTE2212I Activity tttttttttt REXX exec: eeeeeeee RC: nn purged from Queue

  Explanation:

  REXX exec eeeeeeee is run in the Platform Server address space. It is assigned activity number tttttttt and completed with a return code of nn. This is the standard message that is displayed when a REQEUT type of REXX is initiated.

- PGTE2217I FUSION REXX EXEC waiting for prior EXEC to complete

  Explanation:

  Only one REXX exec can run at a time within the Platform Server started task. Because one is currently running, this request has to wait until the active request is completed.

- PGTE2221I Data: dddddddd returned by REXX exec: eeeeeeee

  Explanation:

  The Platform Server executes REXX exec eeeeeeee from within the Platform Server address space. The exec returns data dddddddd to the Platform Server started task.

- PGTE2222I REXX Exec: eeeeeeee completed successfully - no data returned by REXX exec

  Explanation:

  The Platform Server executes REXX exec eeeeeeee from within the Platform Server address space. The exec is completed successfully, but no data is returned by the exec to the Platform Server started task.

- PGTE2223I REXX exec failed with return code xx from IRXEXEC processor

  Explanation:

  The Platform Server tries to run a REXX exec from within the Platform Server address space, but the IRXEXEC program is terminated with return code xx.

  If this problem persists, contact TIBCO Support.

- PGTB2243I User not Authorized to use Platform Server: Request allowed due to WARN mode

  Explanation:

  The Platform Server is defined to restrict its usage to a limited group of users. The user that submitted the file transfer request is not authorized to use the Platform Server. The Platform Server GLOBAL EXTENDED_SECURITY_RESOURCE parameter is set to WARN. Therefore, the file transfer continues after displaying this message.

- PGTB2245I User not Authorized to use Node xxxxxxxx: Request allowed due to WARN mode

  Explanation:

  The Platform Server is defined to restrict the usage of the Platform Server nodes to a limited group of users. The user that submitted the file transfer request is not authorized to use the Platform Server node xxxxxxxx. The second parameter of the Platform Server GLOBAL EXTENDED_SECURITY_RESOURCE parameter is set to WARN. Therefore, the file transfer continues after displaying this message.

- PGTE2298I xxxx

  Explanation:

  Debug message for platform internal use.

- PGTE2299I xxxx

  Explanation:

  Debug message for platform internal use.

- PGTE2310I text message from user exit

  Explanation:

  This message displays the text message returned by the user exit.

- PGTS2404I The Platform Server Node=nnnnnnnn successfully enabled by user=uuuuuuuu

  Explanation:

  A Platform Server Command Center NODE ADD request is received for node nnnnnnnn by user uuuuuuuu. The request is successful, and the node is successfully enabled.

- PGTS2405I The Platform Server Node=nnnnnnnn successfully deleted by user=uuuuuuuu

  Explanation:

  A Platform Server Command Center NODE DELETE request is received for node nnnnnnnn by user uuuuuuuu. The request is successful, and the node is successfully deleted.

- PGTS2420I Node Disable request pending for Node=nnnnnnnn: SAPI Request currently active

  Explanation:

  A Platform Server Command Center NODE DELETE request is received. But NODE nnnnnnnn is currently executing a SAPI request. The node is disabled when the SAPI request is completed.

- PGTS2426I CCC BROWSE request failed - Not Authorized: Access limited to Userid=uuuuuuuu

  Explanation:

  A Command Center user tries to browse the Platform Server AUDIT file. The Platform Server performs the necessary checks, and it finds that the user is not authorized for the CCC_BROWSE_FACILITY or the CCC_ADMIN_FACILITY resource. As a result, the user can only view audit records for his or her own user ID. This is an information message that shows the user is limited to viewing transfers for user uuuuuuuu. To enable the user to view more messages, you must give the user read authorization for the GLOBAL CCC_BROWSE_FACLITY resource.

- PGTS2428I Audit Inquiry from User uuuuuuuu on Node nnnnnnnn: xx Audit records returned

  Explanation:

  The Platform Server Command Center issues a request to extract records from the Platform Server audit file. This is an information message that is written to the audit log, but it is not displayed in the console. It displays the number of records that are returned on this request. It also displays the user that initiated the request along with the node where the request was initiated.

- PGTS2459I FUSPING xxxxxxxx yyyyyyyy

  Explanation:

  The Platform Server CFPING request is executed. This is an information message that displays version information about the Platform Server system.

- PGTS2460I FUSPING Packet nnnn Bytes=xxxx yyyy milliseconds

  Explanation:

  The Platform Server CFPING DATA request is executed. This is an information message that displays the packet number, packet size, and the time taken to get a response from the remote system.

- PGTS2466I rrrrrrrr xxxxxxxx tttttttt by user uuuuuuuu from Command Center Node: nnnnnnnn

  Explanation:

  The Command Center initiated a request to add, update, or delete a PSZ definition. rrrrrrrr defines whether the request is for a NODE, PROFILE, or RPROFILE. xxxxxxxx defines the target node, profile, or rprofile. tttttttt defines whether the request is to add, update, or delete the definition. nnnnnnnn defines the node where the request is initiated.

- PGTS2570I cccccccc MFT Platform Server STC Name: Version: vvv Maint: mmm mmm

  Explanation:

  This message gives the name of the started task, the version, and the maintenance level of the Platform Server. This is the result of the VER modify command (`F servername,VER`).

- PGTS2574I DATASPACE: xxxx HAS AN STOKEN OF yyyy

  Explanation:

  The user entered the `F server_name,STK` command. The output of this command is the STOKEN of the Queue Data In Virtual (DIV) dataspace STOKEN.

- PGTS2575I Modify command received

  Explanation:

  This is a normal message that is displayed after any valid modify command is entered.

- PGTS2576I Command not supported: xxxx

  Explanation:

  This is an information message that is displayed after an unsupported modify command is entered.

- PGTS2579I Modify STOP command received, shutting down server: xxxx

  Explanation:

  This is a normal message that is displayed when the STOP modify command is used to shut down server xxxx.

- PGTS2580I PROCESSING SNAP

  Explanation:

  The Platform Server is processing the snap dump that is taken.

- PGTS2582I Modify RESET command received

  Explanation:

  This is an information message.

- PGTS2583I Modify QUIESCE command received: xxxx

  Explanation:

  This is a normal message that is displayed when the QUIESCE modify command is used to shut down server xxxx.

- PGTE2600I Command cccccccc not supported: Platform Server DNI not activated

  Explanation:

  The Platform Server DNI operator command cccccccc is executed, but DNI is not activated. This is typically because the GLOBAL DNIKEY parameter specified is invalid.

- PGTE2623I DNI member mmmmmmmm ENABLED: DNIENA command successful

  Explanation:

  The DNIENA operator command was entered to enable a DNICFG entry, and the entry was enabled successfully.

- PGTE2643I DNI Updated request with new xxxxxxxx: yyyyyyyy replaces old xxxxxxxx value

  Explanation:

  DNI is processing a dataset that has a %NODE or %IPNAME substitutable parameter in the DSN (or LF/LFILE). xxxxxxxx is either NODE or IPNAME, and yyyyyyyy is the parameter that is substituted for %IPNAME or %NODE.

- PGTE2647I DNI Transid tttttttt Deleted: DNIPURGE command successful

  Explanation:

  The `DNIPURGE` command for DNI transfer ID tttttttt is entered. The command is executed successfully, and the request is purged from the DNIACT queue.

- PGTE2650I DNI TRN=tttttttt DSN=dddddddd

  Explanation:

  This message is displayed as a result of the `DNIDISP` command entered without a transfer ID. It displays a summary list of DNI transfer IDs and the DSN associated with them.

- PGTE2651I DNI xxxxxxxx: yyyyyyyy

  Explanation:

  This message is displayed as the result of the `DNIDISP` command specified with a transfer ID. xxxxxxxx defines the field and yyyyyyyy defines the data associated with the field. This message is displayed multiple times for each detail display: once for each field that is displayed.

- PGTE2652I DNI nn requests found on the DNIACT queue

  Explanation:

  This is a summary message that is displayed as the result of the `DNIDISP` command entered without a transfer ID. It shows the number of messages (nn) that are on the DNIACT queue.

- PGTE2656I DNI Locate for DNICFG=mmmmmmmm DSN=dddddddd exceeds max count of nn entries

  Explanation:

  DNI is processing a catalog locate request for dataset dddddddd. The number of datasets that are returned exceeds the maximum number nn. You must change the wildcard parameter for the DSN (or LF/LFILE) parameter in DNICFG member mmmmmmmm to be more restrictive so that less datasets are returned. DNI processes the first nn datasets that are returned. As DNI continues to process these datasets, the number of datasets returned by the locate request decreases, and eventually falls below nn datasets.

- PGTE2671I DNI Member=mmmmmmmm DSN=ddddddddd

  Explanation:

  This message is displayed when the user enters the DNINODE command without specifying any additional parameters. This message shows the DNI member name and the dataset filter used. This message is displayed once for each enabled DNI definition.

- PGTE2672I DNI xxxxxxxx = yyyyyyyy

  Explanation:

  This message is displayed when the user enters the DNINODE command and specifies the DNI node name. This message shows the detailed information displayed about the DNI node. This message is displayed once for each DNI node field displayed.

- PGTE2674I DNINODE No DNI members are enabled

  Explanation:

  The user enters the DNINODE command without specifying a DNI node name. No DNI nodes are currently enabled.

- PGTE2704I PPASCRPT: Script request scheduled successfully

  Explanation:

  A PPA CALLJCL request was executed for program PPASCRPT. This is an information message that indicates that the script request was submitted successfully to the started task.

- PGTT2803I Activity tttttttttt Job jjjjjjjj iiiiiiii has been dddddddd due to rrrrrrrr

  Explanation:

  This message indicates that request tttttttttt for job jjjjjjjj with job ID iiiiiiii has been completed. This message indicates whether the Sysout file has been kept, deleted, or held, based on the NODE LDISP parameter. It also indicates whether the transfer request was successful or failed with a permanent network error or permanent error.

- PGTT2804I Activity tttttttttt FUSSAPIP Attempting restart, but SAPI DSN changed: Starting from beginning

  Explanation:

  SAPI request tttttttttt was being restarted. Before restarting the request, the Platform Server checks that the JES dataset name matches the dataset name of the original request. If it does not match, this message is displayed, and the request is restarted from the beginning.

- PGTF3100I xxxx Activity yyyy started to Remote System: zzzz [ SNA | TCP ]

  Explanation:

  The server transmission subtask has commenced processing the file transfer named in the message text.

- PGTF3101I Activity xxxx successfully transferred yyyy records with node zzzz

  Explanation:

  This is a normal message that is displayed at the end of a successful transfer. The number of records that were transferred is also reported in this message.

- PGTF3102I Activity xxxx started to Remote Open System: yyyy

  Explanation:

  The activity referenced in the message text has been commenced by the transmission subtask.

- PGTF3103I Activity xxxx successful with node yyyy

  Explanation:

  The activity xxxx requested to the remote system is completed successfully.

- PGTF3104I Activity xxxx successfully received yyyy records from remote system: zzzz

  Explanation:

  The Platform Server has successfully retrieved the target file from the remote computer.

- PGTF3105I Remote system: xxxx sent F-Close-Request prior to F-Read-Request - No records sent for activity yyyy

  Explanation:

  When you receive this message, contact TIBCO Support.

- PGTF3106I Activity xxxx failed with Remote Open System: yyyy

  Explanation:

  Activity failed to the remote system.

  For the possible cause of failure, see previous diagnostic messages.

- PGTF3107I Activity xxxx successfully send yyyy records to remote system: zzzz

  Explanation:

  This is a normal message that is displayed at the end of a successful transfer. The number of records that were transferred are also reported in this message.

- PGTF3108I xxxx RC=yyyy zzzzz Record Count=nnnn

  Explanation:

  This is a variable message that includes the transaction number for the transfer, the return code, the node, the name of the file being transferred, the number of records transferred, the transfer type (send or receive), and a description of the transfer.

- PGTF3110I Activity xxxx Delete Successful to: yyyy of: zzzz

  Explanation:

  The remote file is deleted successfully.

- PGTF3113I Activity xxxx compression type=yyyy compressed bytes=zzzz compression ratio=nnnn:1

  Explanation:

  This message is displayed when compression is used to show the number of bytes that were compressed and the compression ratio.

- PGTF3114I Activity xxxx with Node yyyy suspended - Activity put on hold

  Explanation:

  Transfer xxxx with node yyyy is suspended using the `F server_name,SUSPEND` command.

- PGTF3115I Responder Activity xxxx with Node yyyy suspended - Activity [NOT] purged from queue

  Explanation:

  Activity xxxx with node yyyy is suspended. The transfer was either purged or not purged depending on the checkpoint setting for the transfer.

- PGTF3116I Initiator Submit for activity xxxx successful - job yyyy (zzzz records) submitted to internal reader

  Explanation:

  This message is displayed when a file to job transfer is submitted to the JES internal reader. xxxx is the activity number, yyyy is the job name, and zzzz is the number of records in the job.

- PGTF3117I Initiator Submit for activity xxxx failed - Queue entry purged

  Explanation:

  This message is displayed when a Platform Server file to job transfer is submitted to the JES internal reader and the transfer fails. In this case, activity xxxx is deleted from the queue.

- PGTF3118I Network error on activity xxxx node: yyyy - activity will be retried at next retry interval

  Explanation:

  An error was detected when processing transfer activity xxxxxxxxxx to node yyyy. The activity will be retried at the next retry interval. This is an information message.

- PGTF3119I Network error on activity xxxx node: yyyy - retry count exceeds maximum - activity purged

  Explanation:

  The transfer has exceeded the number of retries as stated in the Try parameter and is now purged.

- PGTF3133I xxxxxxxx Activity tttttttt started to Backup Node aaaaaaa bbbbbbb ccccccc dddddddd eeeeeeee ffffff

  Explanation:

  A file transfer request has failed with a network error. The NODE definition had been defined with one or more BACKUPLUNAME, BACKIPIPNAME, or BACKUPIPADDR parameters. This message indicates that the SEND or RECEIVE request (xxxxxxxx) for activity tttttttttt is retried to back up node aaaaaaaa. It also defines whether the transport is TCP or SNA and the level of encryption configured.

- PGTF3135I rrrrrrrr Activity tttttttttt: Processing TLS ttttt request with node nnnnnnnn

  Explanation:

  This message is for information purposes only. It means that a request requiring TLS authentication is about to be executed. No action is required.

- PGTF3138I SSL Debug aaaaaaaa bbbbbbbb ccccccc dddddddd eeeeeeee

  Explanation:

  A user requested the Platform Server to display DEBUG output when SSL requests are executed. This is only done at the request of TIBCO Support. To turn off the SSL Debug messages, issue the Platform Server `SSLDEBUG=NO` operator command.

- PGTF3139I SSL Debug dddddddd: RC=xx Sense=yy

  Explanation:

  A user requested the Platform Server to display DEBUG output when SSL requests are executed. This is only done at the request of TIBCO Support. To turn off the SSL Debug messages, issue the Platform Server `SSLDEBUG=NO` operator command.

- PGTF3152I Activity tttttttttt Encrypt changed to NONE due to NODE ENCRYPT=NEVER parameter

  Explanation:

  The user submitted a request that utilizes data encryption. However, the NODE definition defined for the request contains the `ENCRYPT=NEVER` parameter. This indicates that encryption should never take place for transfers to this node. This message indicates that the encryption defined is overridden to no encryption. The transfer request continues, and no data encryption takes place.

- PGTF3155I xxxxxxxx error on activity: tttttttt node: nnnnnnnn - Error will be retried in yy seconds

  Explanation:

  The Platform Server detected a temporary file error. The file error try count has not exceeded the GLOBAL FILE_ERROR_TRY_COUNT setting. Therefore, the request will be retried. The GLOBAL FILE_ERROR_TRY_INTERVAL parameter defines the amount of time (yy) that the Platform Server waits before retrying the request.

- PGTF3156I tttttttt CALL to program pppppppp Successful: Return code=nn

  Explanation:

  The Platform Server has received a CALLPROG or CALLJCL request from a remote system. The Platform Server has called program pppppppp. The call was successful, and the program passed a return code of nn (this should be zero) back to the Platform Server. This message indicates that the CALLPROG or CALLJCL request was successful.

- PGTF3183I Activity tttttttttt ENCRYPT changed from xxxxx to yyyyy due to HIPAA Regulations

  Explanation:

  The Platform Server was executing initiator activity tttttttttt and detected that the HIPAA parameter was defined as YES for either the GLOBAL or NODE definition. The Platform Server determined that the encryption level was less than 112 bits. Because of this, the Platform Server changed the encryption type to one that supported at least 112 bits. This is an information message only. No action is required. The transfer continues normally with the new encryption type.

- PGTF3187I tttttttttt CFACCESS changed DSN from dddddddddd to eeeeeeeeee

  Explanation:

  The Platform Server responder transaction tttttttttt was running. The Platform Server CFACCESS processing changed the dataset name from dddddddd to eeeeeeee. The new dataset name is used in all file access by the Platform Server. This message ID is displayed for information purposes only.

- PGTF3190I tttttttttt CFALIAS changed DSN from dddddddddd to eeeeeeeeee

  Explanation:

  The Platform Server responder transaction tttttttttt is running. The Platform Server CFALIAS processing changed the dataset name from dddddddd to eeeeeeee. The new dataset name is used in all file access by the Platform Server. This message ID is displayed for information purposes only.

- PGTE3196I $CFDIR Error loading IGGCSI00: Using DNICSI00 module for LOCATE requests SMS Version: xx

  Explanation:

  The Platform Server requested a dataset catalog or directory list. The Platform Server attempted to load the z/OS catalog list module IGGCSI00 but received an error. When this occurs, the Platform Server uses its own Catalog Directory module called DNICSI00. This message is displayed for information purposes only. The transfer continues running.

- PGTE3202I tttttttttt Failed due to COSNAME=nnnnnnn Priority=xx: Transfer will be retried at next interval

  Explanation:

  The Platform Server was processing transaction tttttttttt using COS name nnnnnnnn. The COS entry defined the priority as xx (either 00 or 01). When a priority of 00 or 01 is received, the Platform Server does not allow that transfer to start. The transfer is terminated, and this message is sent back to the Platform Server system. Because this is a retryable error, the Platform Server will retry the request at a later time, depending on the number of tries defined for the transfer request.

- PGTE3203I tttttttttt COSNAME=cccccccc not found: COS processing will not be performed

  Explanation:

  The Platform Server was processing transaction tttttttttt using COS name nnnnnnnn. The Platform Server looked through the list of enabled COS names, but it could not find name nnnnnnnn. In this case, the transfer continues but no COS processing will be performed.

  Make sure that COS name nnnnnnnn is defined in the CONFIG DD statement and activated at startup or through the Platform Server ENA operator command. To get a list of enabled COS entries, use the Platform Server COS operator command without any additional parameters.

- PGTF3210I tttttttttt Starting xxxx Directory request LF=llllllllllll RF=rrrrrrrrrrrrrr

  Explanation:

  The Platform Server is processing a directory transfer request. This is an information message indicating that the Platform Server is starting a send or receive request (xxxx) and defines the local (LF) and remote (RF) file names associated with the request.

- PGTF3211I tttttttttt Directory transaction uuuuuuuuuu completed with Code=@4

  Explanation:

  The Platform Server processed a directory transfer request. This is an information message that indicates the Platform Server has completed one file transfer request (transaction ID uuuuuuuuuu),and the message defines the return code associated with the request. A return code of 0 indicates that the request was successfully completed, while a non-zero return code indicates that the request failed.

- PGTF3218I tttttttttt Directory Transfer: xxxxxxxx Success=nn Failure=nn

  Explanation:

  The Platform Server has completed processing a directory transfer send or receive (xxxxxxxx) request. How many of the requests were successful and how many failed is displayed.

- PGTF3222I tttttttttt DIRTEST=YES Directory Transfer: xxxxxxxx Files=nn

  Explanation:

  The Platform Server was performing a directory transfer send or receive (xxxxxxxx). The user specified the `DIRTEST=YES`. The number of files that were extracted is displayed. No transfers were actually performed because the `DIRTEST=YES` setting.

- PGTF3223I tttttttttt Checkpoint Restart not supported for DBCS Translation: Checkpoint Restart turned off

  Explanation:

  The Platform Server was performing a file transfer request with DBCS turned on. The user specified that checkpoint restart should be allowed for this file transfer, but checkpoint restart is not supported when DBCS conversion is turned on. Checkpoint restart is turned off for this file transfer request.

- PGTF3227I aaaaaaaaaa: Request sent to RocketStream Server: iiiiiiii: pppp

  Explanation:

  The Platform Server was initiating a request and detected that this request was defined as a RocketStream request. It notifies the user that the request is being processed through the RocketStream accelerator. Where, aaaaaaaa defines the activity associated with the request, and iiiiiiiii:pppp defines the IP address and port of the RocketStream server.

- PGTF3231I aaaaaaaaaa: xxxxxxxx Directory transaction aaaaaaaaaa scheduled with Code=nn

  Explanation:

  A directory transfer request was scheduled. The activity number (aaaaaaaaaa) of the directory transfer, whether the transfer is a send or receive (xxxxxxxx), the activity number of the file transfer request being queued, and the return code of the request being queued are displayed.

- PGTF3232I Activity aaaaaaaaaa ENCRYPT changed to AES due to GLOBAL FIPS140 Setting

  Explanation:

  A request was initiated on the Platform Server for z/OS system. The request must be run as a FIPS 140 request because of the setting of the GLOBAL or NODE ENFORCE_SECURITY_POLICY parameter. The transfer request was not configured with AES encryption. The Platform Server automatically changed the request to use AES encryption to comply with FIPS regulations.

- PGTF3238I tttttttttt ASYNCWAIT transfers exceed max of nn: Subsequent transfers will be executed with WAIT=YES

  Explanation:

  The user executed a directory transfer with `WAIT=ASYNCWAIT`. While executing the directory transfer, the number of transfers exceeded the maximum number of transfers allowed to be executed asynchronously. Transfers scheduled after this message is displayed will be executed with `WAIT=YES`.

- PGTF3239I tttttttttt ASYNCWAIT transfer completed with RC=nn

  Explanation:

  The completion return code for a transfer submitted with `WAIT=ASYNCWAIT` is displayed. This message is not written to the console; it is only written to the OSIMSGS log.

- PGTF3240I tttttttt Transfer terminated: NODE nnnnnnnn has RESPHOLD=YES: Transfer can be retried at a later time

  Explanation:

  A transfer request was received for node nnnnnnnn. However, the node is in a Responder Hold state. The transfer request is terminated with a recoverable network error.

  Issue the RESPREL operator command or use the ISPF panels to release the hold and allow transfers to be accepted from this node.

- PGTF3241I Node nnnnnnnn set to INITHOLD=YES: Remote error exceeded the Node INITIATOR_ERROR_HOLD limit of xxx

  Explanation:

  An initiator transfer request was performed with node nnnnnnnn. The transfer partner reported an unrecoverable error. When this error occurs, a count of consecutive remote errors is incremented. The error count exceeds the NODE INITIATOR_HOLD_ERROR limit of xxx; the node is placed in INITHOLD state, so that no initiator requests can be initiated to this node.

  When the problem causing the remote errors is resolved, issue the INITREL operator command or use the ISPF panels to release the hold and allow transfers to be initiated to this node.

- PGTE3247I tttttttttt: CRC=cccccccc: Partner does not support CRCCHECK

  Explanation:

  Platform Server is configured to perform CRC checking. However, the transfer partner does not support CRC processing so TIBCO MFT Platform Server for z/OS cannot validate the partner's CRC. This message is displayed for information purposes only.

- PGTE3249I ttttttttt: CRC=cc: Local and Partner CRC match

  Explanation:

  Platform Server is configured to perform CRC checking. The CRC computed by the sender matches the CRC computed by the receiver. This message is displayed for information purposes only.

- PGTE3250I ttttttttt: Local CRC=cccccccc

  Explanation:

  Platform Server is configured to perform CRC checking. This message is displayed when Platform Server for z/OS is the sender.

- PGTE3251I tttttttttt: Checkpoint Restart turned off because TRUNCATE=YES was defined

  Explanation:

  A file transfer was performed that had both checkpoint restart and `TRUNCATE=YES` defined. However, a checkpoint restart is not supported when `TRUNCATE=YES` is defined. Checkpoint restart was turned off for this transfer.

- PGTE3252I tttttttttt: TRUNCATE=YES turned off because CCSID translation table defined

  Explanation:

  A file transfer was performed that had both `TRUNCATE=YES` and UNICODE code conversion defined. However, code conversion is not supported when `TRUNCATE=YES` is defined. TRUNCATE was turned off for this transfer.

- PGTE3253I tttttttttt: Checkpoint Restart turned off because multi-byte conversion table was defined

  Explanation:

  A file transfer was performed that had both checkpoint restart and a multi-byte conversion table defined. However, checkpoint restart is not supported when multi-byte translation tables are defined. This is an information message indicating that checkpoint restart was turned off for this transfer.

- PGTE3257I tttttttttt: TRUNCATE=YES not supported for zOS to zOS transfers: Truncate turned off

  Explanation:

  The TRUNCATE=YES parameter was specified for a zOS to zOS file transfer, but truncate is not supported for zOS to zOS transfers. TRUNCATE=YES is turned off, and the transfer continues.

- PGTE3261I tttttttttt: TCP Timeout negotiated to nn minutes

  Explanation:

  Platform Server negotiates the TCP timeout used on TCP send and receive requests to the larger value defined by the initiator or responder. This message indicates that the transfer partner's TCP timeout was larger than the local TCP timeout and that the TCP timeout has been set to nn minutes.

- PGTF3502I SSL Request accepted from node nnnnnnnn by default: No match on SSLAUTH config was found

  Explanation:

  An SSL request was received from node nnnnnnnn. The Platform Server scanned its SSLAUTH file for a match on the components of the certificate distinguished name, but could not find a match. This message indicates that by default, the Platform Server accepts the SSL request. Processing of the request continues.

- PGTF3503I SSL Request accepted from node nnnnnnnn: Match on SSLAUTH entry: eeeeeeee

  Explanation:

  An SSL request was received from node nnnnnnnn. The Platform Server scanned its SSLAUTH file for a match on the components of the certificate distinguished name and found a match. The SSLAUTH entry indicated that the request should be accepted. This message indicates that the Platform Server accepts the SSL request. The SSL entry that detected the match is also displayed as eeeeeeee. Processing of the request continues.

- PGTF3504I SSL Request rejected from node nnnnnnnn: Match on SSLAUTH entry: eeeeeeee

  Explanation:

  An SSL request was received from node nnnnnnnn. The Platform Server scanned its SSLAUTH file for a match on the components of the certificate distinguished name and found a match. The SSLAUTH entry indicated that the request should be rejected. This message indicates that the Platform Server rejects the SSL request. The SSL entry that detects the match is also displayed as eeeeeeee. Processing of the request is terminated.

- PGTS3509I gsk_fips_state_set "ON": SSL/TLS running in FIPS Mode

  Explanation:

  TLS FIPS mode is successfully activated. This message is for information purposes only.

- PGTF3510I tttttttttt: TLS (xxxxxxx) Negotiation complete using Cipher: cccc: (ddddddd)

  Explanation:

  This message is displayed when a successful TLS negotiation is completed for transaction tttttttttt. xxxxxxxx defines the TLS protocol used, cccc defines the 4-digit TLS cipher, and ttttt defines the descriptive name of the TLS cipher. When this message is displayed as the result of a TLS tunnel negotiation, the transaction ID is not displayed.

- PGTE3520I SSLAUTH Processing complete - Good records: xxxx Error records: yyyy

  Explanation:

  The SSLAUTH program completed processing. This is a summary record to display the number of good records and the number of error records. This message is displayed at startup and when the SSLAUTHREFRESH command is executed.

- PGTE3522I SSLAUTH Error: Invalid character following / on Record xxxx - Must be CN L S C OU O SN SDATE STIME EDATE ETIME: Record follows

  Explanation:

  SSL configuration was processing the SSLAUTH file and found a problem with the configuration data. The program was expecting one of the following definitions after detecting a forward slash (/): CN, L, C, OU, O, SN, SDATA, STIME, EDATE, ETIME. The record in error is displayed following this message. This entry in the SSLAUTH file is not enabled.

- PGTE3523I SSLAUTH Error: Expecting = after DN component on Record xxxx: Record follows

  Explanation:

  SSL configuration was processing the SSLAUTH file and found a problem with the configuration data. The program was expecting an equal sign (=) immediately after the: /CN, /L, /C, /OU, /O, /SN, /SDATA, /STIME, /EDATE, /ETIME. The record in error is displayed following this message. This entry in the SSLAUTH file is not enabled.

- PGTE3524I SSLAUTH Error: Received EOF when waiting for continuation on Record xxxx: Record follows

  Explanation:

  SSL configuration was processing the SSLAUTH file and found a problem with the configuration data. The program detected a continuation record, but while attempting to process the continuation record End of File (EOF) was encountered. The record in error is displayed following this message. This entry in the SSLAUTH file is not enabled.

- PGTE3525I SSLAUTH Error: Request type must ACCEPT or REVOKE on Record nnnn: Record follows

  Explanation:

  SSL configuration was processing the SSLAUTH file and found a problem with the configuration data. The first field must be defined as either ACCEPT or REVOKE. In this case, the data was not defined in this manner.

  Insure that the ACCEPT or REVOKE is in uppercase and that the continuation indicators are correct. The record in error is displayed following this message. This entry in the SSLAUTH file is not enabled.

- PGTE3526I SSLAUTH Error: DN exceeds max of 256 bytes on Record xxxx: Record follows

  Explanation:

  SSL configuration was processing the SSLAUTH file and found a problem with the configuration data. The DN (Distinguished Name) length exceeded the maximum length of 256 bytes. The record in error is displayed following this message. This entry in the SSLAUTH file is not enabled.

- PGTE3527I SSLAUTH Error: Invalid xxxxxxxx parameter on record nnnn Must be yyyyyyyy: Record follows

  Explanation:

  SSL configuration was processing the SSLAUTH file and found a problem with the configuration data. Field xxxxxxxx is invalid. This message is displayed when there is a problem validating one of the DATE or TIME fields. The correct format of the field is displayed as yyyyyyyy. The record in error is displayed following this message. This entry in the SSLAUTH file is not enabled.

- PGTE3528I iiiiiiiiiiiiiiiiiiiiiiiiiiiii’

  Explanation:

  SSL configuration was processing the SSLAUTH file and found a problem with the configuration data. This message displays the record in error. It is accompanied by other messages indicating the cause of the error.

- PGTE3529I SSLAUTH Internal error: FINDVECT failed with RC=xx: Contact Platform technical Support

  Explanation:

  The Platform Server was processing the SSLAUTH data and received an internal error.

  Contact TIBCO Support if this error re-occurs.

- PGTE3530I SSLAUTH DD has invalid DCB: Must be RECFM=FB,LRECL=80: SSLAUTH Processing terminated

  Explanation:

  SSL configuration was processing the SSLAUTH file and found a problem with the DCB information of the file. The DCB information must be `RECFM=FB,LRECL=80`. No SSLAUTH records are enabled.

  You must change the SSLAUTH file to match these DCB characteristics.

- PGTE3531I SSLAUTH DD not defined: SSLAUTH processing terminated

  Explanation:

  SSL configuration was processing the SSLAUTH file, but the SSLAUTH DD statement was not defined. No SSLAUTH records are enabled.

  You must add the SSLAUTH DD statement to the Platform Server startup JCL and then stop and start the Platform Server.

- PGTE3532I SSLAUTH DD OPEN failed: SSLAUTH processing terminated

  Explanation:

  SSL configuration was processing the SSLAUTH file, but OPEN of the SSLAUTH DD statement failed. No SSLAUTH records are enabled.

  Review the z/OS console log for more information on the cause of the failure.

- PGTE3800I Activity tttttttttt xxxx_ACTION has submitted jjjjjjjj JCL=ddddddddddd

  Explanation:

  The Platform Server transfer action processing has submitted job number jjjjjjjj for activity tttttttttt. The JCL used to submit this job was defined as dddddddddd.

  This is an information message only. No action is required.

- PGTE3812I Activity tttttttttt ppp RC=rr xxxxxx: cccccccccc

  Explanation:

  The Platform Server was performing a preprocessing action or postprocessing action for activity tttttttttt. xxxxxxxx defines the action that was being performed on ccccccccc. ppp defines whether this was preprocessing or postprocessing. rr defines the return code that was received from the action. This message has no effect on the return code of the file transfer request.

- PGTE 3816I Activity tttttttttt xxxx_ACTION CFACCESS SUBMIT_OPTION=ROOT changed SUBMIT DSN to dddddddddd

  Explanation:

  The Platform Server was executing a PPA (Post Processing Action) SUBMIT request. PPA was checking the CFACCESS configuration file and detected a match. The entry was defined with `SUBMIT_OPTION=ROOT` which means that the transfer file name is actually the member name. The member name was enclosed in parentheses and appended to the SUBMID_HLQ name. The resulting DSN is displayed as dddddddd. This message is displayed for information purposes only.

- PGTE3820I tttttttttt: PreProcessing request returned RC=rr: Transfer terminated

  Explanation:

  A preprocessing request was executed at the start of the transfer. The preprocessing command returned a return code (rr) greater than 4. The transfer is terminated with a permanent error.

- PGTE3821I tttttttttt: PreProcessing request returned RC=rr: Transfer will be retried

  Explanation:

  A preprocessing request was executed at the start of the transfer. The preprocessing command returned a return code (rr), which was greater than 0 and less than 4. The transfer is terminated with a retryable error. If the transfer initiator try count has not reached the maximum tries, the request will be retried at the next transfer interval.

- PGTE3822I tttttttttt: About to issue CALLPGM to module (mmmmmmmm) with %QUEUE PPA override token

  Explanation:

  Transfer tttttttttt specified a preprocessing command. The command was for a CALLPGM and specified the %QUEUE token. This token forces Platform Server to call a user-defined program that can override transfer parameters. This is an information message that is displayed before calling the user-defined module mmmmmmmm.

- PGTE3825I tttttttttt: PreProcessing CALLPGM request overriding Transfer parameters: Changing Return code from 1 to 0

  Explanation:

  Transfer tttttttttt specified the %QUEUE PPA token in a preprocessing call with CALLPGM defined. The user defined preprocessing program set the exit return code to 1. This indicates that the user-defined program overrode some transfer parameters. This message indicates that Platform Server detected that the user-defined program overrode transfer parameters and is resetting the return code to 0 so that processing can continue.

- PGTE3840I FUSUTIL RENAME ddddddd to nnnnnnn

  Explanation:

  The Platform Server was processing the Platform Server for z/OS FUSUTIL utility. The Platform Server displays this message when it is about to rename a dataset. The dataset that is to be renamed is ddddddd. This message is displayed for information purposes only.

- PGTE3850I CFACCESS Processing complete - Good records: nnnn Error records: eeee

  Explanation:

  The Platform Server completed processing the CFACCESS configuration file. This is an information message that shows the number of successful and unsuccessful entries processed.

- PGTE3858I CFACCESS DD not defined: Bypassing CFACCESS processing

  Explanation:

  The Platform Server was attempting to process the CFACCESS DD statement, but detected that the CFACCESS DD statement was not defined. The CFACCESS parameter file is not processed, and as such no CFACCESS checking is performed. This is an information message only.

  Review the accompanying z/OS messages to determine the cause of the failure.

- PGTE3880I CFALIAS Processing complete - Good records: xx Error records: yy

  Explanation:

  The Platform Server had completed processing the CFALIAS configuration file, either at startup or when the Platform Server CFALIASREFRESH operator command was executed. This message is an information message and shows how many good and error records were processed.

- PGTE3888I CFALIAS DD not defined: Bypassing CFALIAS processing

  Explanation:

  The Platform Server was processing the CFALIAS configuration file. The Platform Server detected that the CFALIAS DD statement was not defined in the startup JCL. CFALIAS processing is bypassed. No CFALIAS processing is performed for any transfers.

  To use CFALIAS, you must add the CFALIAS DD statement to the Platform Server started task startup JCL and then bring the Platform Server down and up.

- PGTE3900I SUBJCL Processing complete - Good records: nn Error records: ee

  Explanation:

  The SUBJCL configuration program has completed processing. This information message indicates that nn good records and ee error records have been processed.

- PGTE3908I SUBJCL DD not defined: Bypassing SUBJCL processing

  Explanation:

  The Platform Server SUBJCL configuration program detected that the SUBJCL DD statement was not defined in the Platform Server startup JCL. SUBJCL processing is terminated.

  This message is for information purposes only. If you do not want to use the SUBJCL feature, this message can be ignored.

- PGTE3920I TRCLASS Processing complete - Good records: nn Error records: nn

  Explanation:

  This message is displayed at startup when the TRCLASSREFRESH operator command is executed. It provides a summary of the good TRCLASS and error TRCLASS parameters processed. Details on the errors were displayed in previous messages.

- PGTE3922I TRCLASS DD not defined: Bypassing TRCLASS processing

  Explanation:

  An attempt was made to open the TRCLASS DD statement, but the DD Statement was not defined. In this case, TRCLASS processing is disabled.

  To enable TRCLASS processing, add the DD statement to the MFT started task JCL, and point it to a valid TRCLASS configuration file. The MFT SAMPLIB member TRCLASS shows an example of how the TRCLASS parameters are defined.

- PGTE3928I TRCLASS Num=xx Name=nnnnn MAX=yy Current=zz

  Explanation:

  This message is displayed when the TRCLASSDISP operator command is executed. One message is displayed for each TRCLASS defined. It displays the TRCLASS number, name, maximum number of transfers, and the current number of transfers for each transfer class.

- PGTE3932I tttttttttt TRCLASS "nnnnnnnnnn" changed to TRCLASS NUM xx

  Explanation:

  A transfer that defined a transfer class was submitted. Transfer class nnnnnnnnnn was found in the TRCLASS table and was converted to transfer class xx.

  This is an information message; no action is required.

- PGTE3950I Activity tttttttttt SUBJCL has submitted JOBxxxxx JCL=jjjjjjjj

  Explanation:

  Activity tttttttttt was completed. The SUBJCL processing has submitted JCL jjjjjjjj. Job xxxxx is the job that was submitted into the internal reader. This message is displayed for information purposes only.

- PGTB4119I INVALID/MISSING SERVER PARM - DEFAULT USED

  Explanation:

  The name of the Platform Server used in the EXEC card of the Platform Server batch job is invalid or missing.

  Correct the error and resubmit the transfer.

- PGTB4120I INVALID QUEUE EFFECT FOR ACTIVITY

  Explanation:

  This message is displayed for a RECEIVE operation under any of the following three circumstances:

  - `EFFECT=CREATE` was specified, but the file already exists.
  - `EFFECT=REPLACE` was specified, but the file does not exist.
  - `EFFECT=APPEND` was specified, but the file does not exist.
- PGTB4140I LIST xxxx SUCCESSFULLY QUEUED yyyy ACTIVITIES

  Explanation:

  The LIST parameter was used to distribute the file to several remote locations. This message reflects how many activities were queued based on the LIST parameter that was specified.

- PGTB4142I Schedule Request has completed with return code xxxxxxxx

  Explanation:

  This message is displayed after a request has been scheduled. It shows the return code associated with a schedule request. A return code of zero indicates that the request was scheduled successfully, while a non-zero return code indicates that the schedule request failed. This message is displayed under the following two conditions:

  - When a schedule request fails
  - When a schedule request is successful and the user specified `WAIT=NO`
- PGTB4143I Request has completed with return code xxxxxxxx

  Explanation:

  This message is displayed after a request specified with `WAIT=YES` has been completed. It shows the return code associated with the request. A return code of zero indicates that the request has been completed successfully, while a non-zero return code indicates that the request failed.

  Note: This message is only displayed after a request defined with `WAIT=YES` has been completed.
- PGTB4193I IPADDR and IPNAME parameters ignored for transfer type: SCRIPT

  Explanation:

  The user was queuing a SCRIPT, SUBMIT, or REXX EXEC to the Platform Server started task. The user specified the IPADDOR or IPNAME parameters. This message indicates that these parameters are ignored during this type of transfer.

  This is an information message. No action is required.

- PGTB4194I NODE parameter ignored for SCRIPT Transfers: NODE CONTENTION_WINNERS will be used to throttle transfers

  Explanation:

  The user was queuing a SCRIPT, SUBMIT, or REXX EXEC to the Platform Server started task. The user specified the NODE parameter. This message indicates that the NODE parameter was ignored during this type of transfer, but the NODE CONTENTION_WINNERS parameter will be used to throttle the number of transfers of this type that can be executed simultaneously.

  This is an information message. No action is required.

- PGTE4230I Activity tttttttttt Script execution started: Output will be in ddname dddddddd

  Explanation:

  The Platform Server was running a script. This is an information message that indicates the script execution was started and that any output for this script will be in DD statement dddddddd. The user can browse the output in the Platform Server started task output.

- PGTE4231I Activity tttttttttt Script execution successful: Script output is in ddname dddddddd

  Explanation:

  The Platform Server was running a script. This is an information message that indicates the script execution was successful and that any output for this script is in DD statement dddddddd. The user can browse the output in the Platform Server started task output. The script ended with a return code of 0. The script is purged from the system.

- PGTE4234I Activity tttttttttt Script purged: Script output is in ddname dddddddd

  Explanation:

  The Platform Server was running a script. This is an information message that indicates the script was purged from the system and that any output for this script is in DD statement dddddddd. The user can browse the output in the Platform Server started task output.

- PGTE4235I Activity tttttttttt Script ended with retryable error: Request will be retried at next error interval

  Explanation:

  The Platform Server was running a script. This is an information message which indicates that the script execution was unsuccessful and that any output for this script will be in the DD statement dddddddd. The user can browse the output in the Platform Server started task output. The script ended with non-zero return code yy, but the user specified a try count of more than 1. The script will be tried again at the next error interval.

- PGTE4239I tttttttttt INDIRECT=DELETE specified: DSN=dddddddddd will be deleted

  Explanation:

  The user was executing a script defined with the INDIRECT parameter set to DELETE. This is an information message that indicates the indirect file will be deleted.

- PGTE4240I tttttttttt INDIRECT parameter invalid: Must be YES, NO, or DELETE: Script terminated

  Explanation:

  The user executed a script defined with the INDIRECT parameter. The user specified a value for the INDIRECT parameter other than YES or DELETE. The only valid values for this parameter are YES and DELETE. The script is terminated with errors.

- PGTE4243I tttttttttt Script mmmmmmmmmm found in SCRIPT DD DSN=ddddd

  Explanation:

  The user scheduled a SCRIPT to execute in the started task. The script was defined with only a member name. The STC looked up the member in the SCRIPT DD. The DSN that contained the member name was defined in this message. This message is for information purposes only.

- PGTN4505I Connection Identifier: xxxx Resource Identifier: yyyy - Activity: zzzz Rmt Sys: nnnn

  Explanation:

  This is a normal information message issued by the NPSI GATE drivers. It provides the NPSI resource ID which is useful in interpreting VTAM buffer traces.

- PGTN4506I Called DTE Addr: xxxx Calling DTE Addr: yyyy Facilities: zzzz Activity: aaaa Remote Sys: bbbb

  Explanation:

  This is a normal message issued by the NPSI GATE drivers which provides some information about the contents of an X.25 virtual call.

- PGTX4510I Successful Requests=nn Failed Requests=ff Timeout Requests=tt

  Explanation:

  This message is displayed at the end of the FUSXJOB program. It indicates the number of successful requests (nn), the number of failed requests (ff), and the number of requests that timed out (tt). This message is for information purposes only.

- PGTX4511I FUSXJOB ending with Return code rr

  Explanation:

  This message is displayed at the end of the FUSXJOB program. It indicates the return code (rr) that FUSXJOB returns to the operating system. This message is for information purposes only.

- PGTX4512I Activity tttttttttt Queued to Platform Server started task

  Explanation:

  The user executed the Fusion XCOM interface and specified `TYPE=EXECUTE` or `TYPE=SCHEDULE`. This message shows the activity number (tttttttttt) that was associated with the file transfer request. This message is displayed for information purposes only.

- PGTX4514I PARM pppppppp Ignored within Platform Server

  Explanation:

  The user executed the Platform Server XCOM interface and specified the PARM parameter pppppppp. Parameter pppppppp is ignored within FUSXJOB. This message is displayed for information purposes only.

- PGTX4516I SYSIN01 Parameter pppppppp not supported by Platform Server: Transfer continues

  Explanation:

  The user executed the Platform Server XCOM interface and specified the SYSIN01 parameter pppppppp. Parameter pppppppp is not supported by FUSXJOB. Because this parameter is not critical to the completion of the transfer request, it is ignored. This message is displayed for information purposes only.

- PGTX4517I SYSIN01 Parameter pppppppp Option oooooooo not supported by Platform Server: Transfer continues

  Explanation:

  The user executed the Platform Server XCOM interface and specified the SYSIN01 parameter pppppppp. Some values of parameter pppppppp are supported, but the option specified (oooooooo) is not supported by FUSXJOB. Because this parameter is not critical to the completion of the transfer request, it is ignored. This message is displayed for information purposes only.

- PGTF4685I xxxxxxxx VSAM Invalid Record Length on CLOSE Error processing: Transfer can only be restarted from beginning

  Explanation:

  The Platform Server was processing a file transfer request for a VSAM file. The Platform Server was closing the file, but VSAM returned a code indicating that the record length was too small. This is typically because a network error occurred and only a partial record was written to the VSAM file. In this circumstance, the Platform Server detected that a checkpoint restart was not possible. The Platform Server updated the QUEUE record to indicate that checkpoint restart should not be attempted, and that additional processing for this transfer should start from the beginning of the file.

- PGTF4686I xxxxxxxx VSAM Invalid Record detected during CLOSE Error processing: Error is ignored

  Explanation:

  The Platform Server was processing a file transfer request for a VSAM file. The Platform Server was closing the file, but VSAM returned a code indicating that the record length was too small. This is typically because a network error occurred and only a partial record was written to the VSAM file. In this circumstance, the Platform Server ignores the error because it does not affect any future checkpoint restart processing.

- PGTF4687I tttttttttt VSAM RRDS Record Length=yyyy longer than MAX=zzzz: Transfer Terminated

  Explanation:

  The Platform Server was processing a VSAM RRDS file and received a record longer than the maximum record length allowed. The file transfer request is terminated with errors.

  Insure that the VSAM RRDS file is compatible with the file that you are sending.

- PGTF4707I tttttttt:xxxxxxxx Email notify bypassed because GLOBAL SEND_EMAIL_ON_CANCEL set to No

  Explanation:

  A transfer that specified an email failure notification on either the Transfer or Global was cancelled. The `SEND_EMAIL_ON_CANCEL` parameter was set to `NO` on either the Transfer or Global parameters. This message is written to the OSILOG file and indicates that a transfer notification message was not sent.

- PGTS5200I Platform Server Advanced xxxx initiated for Activity yyyy

  Explanation:

  The Platform Server is initiating the protocol to be used with this transfer.

- PGTS5212I Error in APPC Subtask Allocating Storage for Subtask Control Blocks - increase Region Parm

  Explanation:

  The subtask cannot allocate enough storage to do the transfer.

  Increase the Region parameter in the transfer job.

- PGTS5220I Msg from xxxx: <<Message Text>>

  Explanation:

  A message was received from node xxxx.

- PGTS5221I Job Submitted as xxxx on Remote System yyyy

  Explanation:

  This is an information message stating that the file to job transfer was submitted to the remote system.

- PGTS5310I Network Error Received with Node xxxx Transaction Terminated

  Explanation:

  The session with xxxx has ended abruptly because of a network error.

- PGTS5311I Request xxxx with Node yyyy purged due to Security Error on FMH5

  Explanation:

  Activity xxxx is purged for security reasons.

- PGTS5555I APPC: <<Diagnostic message>>

  Explanation:

  Either debugging and/or tracing is enabled, or an internal error has occurred.

  If debugging or tracing is not enabled, note the full text of the message and contact TIBCO Support.

- PGTS5556I <<Diagnostic message>>

  Explanation:

  Internal diagnostic messages issued during debugging and tracing.

- PGTS5869I |TLV Contents : xxxx

  Explanation:

  Internal debugging message.

- PGTS5870I Contents of FVCOMM Dsect

  Explanation:

  Internal debugging message.

- PGTS5871I +-------------------------------------------------------

  Explanation:

  This message is issued to format a table in the log.

- PGTS5872I | FVCOMM_VTAM_ADDR : xxxx

  Explanation:

  Internal debugging message.

- PGTS5873I | FVCOMM_VTAM_ACBNAME : xxxx

  Explanation:

  Internal debugging message.

- PGTS5874I | FVCOMM_VTAM_LUNAME : xxxx

  Explanation:

  Internal debugging message.

- PGTS5875I | FVCOMM_VTAM_MODENAME : xxxx

  Explanation:

  Internal debugging message.

- PGTS5876I | FVCOMM_USERID : xxxx

  Explanation:

  Internal debugging message.

- PGTS5877I | FVCOMM_PASSWORD : xxxx

  Explanation:

  Internal debugging message.

- PGTS5878I | FVCOMM_TPNAME : xxxx

  Explanation:

  Internal debugging message.

- PGTS5879I | FVCOMM_REQ-Type : xxxx

  Explanation:

  Internal debugging message.

- PGTS5880I | FVCOMM_SEND_DATA_Addr : xxxx

  Explanation:

  Internal debugging message.

- PGTS5881I | FVCOMM_SEND_DATA_Len : xxxx

  Explanation:

  Internal debugging message.

- PGTS5882I | FVCOMM_RECV_DATA_Addr : xxxx

  Explanation:

  Internal debugging message.

- PGTS5883I | FVCOMM_RECV_DATA_Len : xxxx

  Explanation:

  Internal debugging message.

- PGTS5884I | FVCOMM_RETURN_CODE : xxxx

  Explanation:

  Internal debugging message.

- PGTS5885I | FVCOMM_Sense : xxxx

  Explanation:

  Internal debugging message.

- PGTS5886I | FVCOMM_What_Received : xxxx

  Explanation:

  Internal debugging message.

- PGTS5887I | FVCOMM_APPC_FLAG : xxxx

  Explanation:

  Internal debugging message.

- PGTS5888I | FVCOMM_APPC_STATE : xxxx

  Explanation:

  Internal debugging message.

- PGTS5889I | FVCOMM_CNOS_DATA : xxxx

  Explanation:

  Internal debugging message.

- PGTS5890I _____Contents of TLVCOMM DSect_____

  Explanation:

  Internal debugging message.

- PGTS6000I xxxx DATASPACE HAS BEEN CREATED

  Explanation:

  This is an information message that indicates that a dataspace has been successfully created. xxxx is the name of the dataspace that has been created.

- PGTM7000I CPU Serial Number: nnnn Model Number: nnnn

  Explanation:

  information message.

- PGTM7050I Loading xxxx Driver yyyy

  Explanation:

  An error occurred loading the transmission code.

  Contact TIBCO Support for assistance.

- PGTS7100I CDE FOUND WITH CORRESPONDING FLAGS FOR THIS STARTED TASK

  Explanation:

  This is a normal message if the started task has been up and down since the last IPL.

- PGTS7150I NO CDE ANCHOR FOUND, CREATING A NEW CDE ANCHOR

  Explanation:

  This is a normal message at startup if this is the first time that the started task is brought up after the last time there was a system IPL.

- PGTM7202I dataset Dynamically Allocated for the Activity xxxx DDNAME: yyyy

  Explanation:

  A transmission subtask successfully issued SVC 99 to allocate an MVS file for the activity named. This message is for information purposes only.

- PGTM7203I dataset Dynamically Unallocated for Activity xxxx DDNAME: yyyy

  Explanation:

  A transmission subtask successfully issued SVC 99 to free an MVS file for the activity named. This message is for information purposes only.

- PGTM7204I dataset NOT Dynamically Allocated for Activity xxxx DDNAME: yyyy

  Explanation:

  An error occurred when a transmission subtask tried to allocate an MVS file using SVC 99. The file is busy or the dataset name is invalid.

  For more information, see other accompanying messages.

- PGTM7205I dataset Not Dynamically Unallocated for Activity xxxx DDNAME: yyyy

  Explanation:

  A transmission subtask was unable to free an MVS file using SVC 99.

  For more information, see accompanying messages in the OSIMSG log or MVS SYSLOG.

- PGTM7206I Activity xxxx: dataset name not valid: yyyy

  Explanation:

  The local file name (initiator) or the remote file name (responder) was not a valid MVS dataset name.

- PGTM7211I Create not allowed - File already exists for Activity xxxx

  Explanation:

  An attempt to create a file on the local MVS system failed because the file already exists.

- PGTM7212I Send not allowed - File does not exist for Activity xxxx

  Explanation:

  An attempt to send a file on the local MVS system failed because the file did not exist.

- PGTM7213I Append or Replace failed - File does not exist for Activity xxxx

  Explanation:

  An attempt to append or replace a file on the local MVS system failed because the file did not exist.

- PGTM7214I Invalid Queue Effect on File for Activity xxxx

  Explanation:

  An invalid effect on the local MVS file was filled in the queue entry. Valid effects are create, replace, append, create or replace, and create or append.

- PGTM7215I Invalid Space type specified in Global for Activity xxxx

  Explanation:

  An invalid space allocation type was filled in the queue entry. Valid space types are tracks, cylinders, megabytes, and kilobytes.

- PGTM7216I xxxx not allowed - File does not exist for Activity yyyy

  Explanation:

  The specified action failed because the file did not exist on the local MVS system.

- PGTM7217I xxxx not allowed - File already exists for Activity yyyy

  Explanation:

  Requested action is not allowed because the file already exists.

- PGTM7229I Activity xxxx allocating dataset DISP=yyyy

  Explanation:

  The transfer is allocating the dataset with yyyy disposition as specified in the transfer.

- PGTM7230I JOBID=xxxx submitted to JES Internal Reader

  Explanation:

  This is a normal message that is displayed when a Platform Server file to job transfer is submitted.

- PGTM7285I tttttttttt File Deleted due to DISP=DNEW: ddddddddd

  Explanation:

  This message is displayed when a file (defined as ddddd) is deleted by the `LDISP=DNEW` or `RDISP=DNEW` setting. DNEW indicates that if a file exists, it should be deleted and then re-created. If the file does not exist, it is created.

  This is an information message. No action is required.

- PGTM7293I tttttttttt Secondary allocation adjusted: Input Vol count=nn New Sec. Allo.=nn: dddddddddd

  Explanation:

  The Platform Server was sending a dataset and was extracting the space allocation values for the dataset. The Platform Server detected that the input volume was a multi- volume dataset and that the output volume was a single volume dataset. The Platform Server adjusts the secondary allocation for the file by multiplying the secondary allocation by the number of volumes in the input dataset. This is an information message only. The transfer continues, and no action needs to be taken.

- PGTM7297I tttttttttt DNEW request failed: Exclusive ENQ failed for DSN dddddddddd

  Explanation:

  A transfer request was specified with a disposition of DNEW. This means that the file is deleted before the transfer and is reallocated again when the transfer starts. The server determined that the file is in use. The transfer terminates with a recoverable error. If the try count is not exhausted, this transfer is retried at the next dispatch interval.

- PGTM7302I DYREASON xxxx S99ERROR yyyy S99INFO zzzz

  Explanation:

  This is diagnostic information reporting SVC 99 dynamic allocation feedback. This data might be useful in resolving dynamic allocation problems and might be requested by TIBCO Support.

- PGTM7303I Activity tttttttttt File Create transfer failed: DSN xxxxxxxxxxxx deleted

  Explanation:

  The Platform Server received a request to create a dataset. The Platform Server had performed the dynamic allocation functions necessary to create the dataset, but the transfer request failed. This message indicates that the created file is deleted. This message is for information purposes only.

- PGTM7321I tttttttttt Retryable error returned from HSM exit for DSN=dddddddd: Request marked as File error

  Explanation:

  The HSM user exit (turned on by setting the GLOBAL `EXIT03=YES` and `EXIT_MIGRATE_VOLUME` parameters) returned an error indicating that a retryable error occurred processing the recall request. The Platform Server marks the request as a temporary error and retries the request when the GLOBAL FILE_ERROR_RETRY_INTERVAL setting expires.

- PGTM7332I Activity tttttttttt DSN=dddddddddd deleted due to DISP=DELETE on xxxxx

  Explanation:

  dataset ddddddddd was deleted because of the disposition parameter specified on the file transfer request. xxxxxxxx determines whether the dataset is deleted because of success or failure. For an initiator task, this is caused by the LDISP parameter, while for a responder request, this is caused by the RDISP parameter.

- PGTM7335I Activity tttttttttt Checkpoint not supported for VS/VBS/FS/FBS files: Checkpoint turned off for fffffffff

  Explanation:

  The user was attempting to perform a file transfer for a variable spanned or fixed standard file that also specified checkpoint restart. Because the Platform Server does not support checkpoint restart for variable spanned or fixed standard files, the Platform Server turns checkpoint processing off for the transfer request.

  This message is for information purposes only. No action is required.

- PGTM7336I Activity tttttttttt Error on VSAM xxxxxx: Request: R15=rr R0=ss

  Explanation:

  The Platform Server was processing a VSAM file to extract information about the VSAM file to send to the remote end. The Platform Server received an error on a VSAM request defined as xxxxxx. The return and reason codes are displayed as rr and ss.

  If this problem persists, contact TIBCO Support.

- PGTM7337I Activity tttttttttt Error on VSAM xxxxxx: R15=rr ACBERFLG=ss

  Explanation:

  The Platform Server was processing a VSAM file to extract information about the VSAM file to send to the remote end. The Platform Server received an error on VSAM OPEN or CLOSE (xxxxxx). The return codes are displayed as rr and ss. These return codes are defined in the IBM manual OS/390 DFSMS Macro Instructions for datasets.

- PGTM7338I Activity tttttttttt Invalid VSAM file type: DSN=dddddddddddd must be KSDS/ESDS/RRDS

  Explanation:

  The Platform Server was processing a VSAM file to extract information about the VSAM file to send to the remote end. The Platform Server detected that the VSAM file was not a KSDS, ESDS, or RRDS file. Because these are the only types of VSAM files that are supported, the request terminates with an error.

- PGTM7339I Activity tttttttttt RESTART on empty VSAM file: Restart - turned off for this transfer

  Explanation:

  The Platform Server was processing a VSAM file to extract information about the VSAM file to send to the remote end. The Platform Server detected that a restart was requested, but the file was empty. The Platform Server therefore turned off restart for this transfer, and the transfer request is started from the beginning.

- PGTM7340I Activity tttttttttt Cannot create DSN=ddddddddddddd: Unable to create VSAM Variable RRDS file

  Explanation:

  The Platform Server was processing a VSAM file, detected that the file did not exist, and was about to create the file. However, the Platform Server was unable to create a variable length RRDS file. The file transfer request terminates, and this message is sent to the remote end. If you need to transfer a variable length RRDS, the file must exist before it can be processed by the Platform Server.

- PGTM7342I Activity tttttttttt Restart Failed: Will start from beginning because file dddddddd not does not exist

  Explanation:

  The Platform Server for z/OS was responding to a Platform Server request to restart a file transfer request. The Platform Server detected that the file requested dddddddd did not exist and therefore, the Platform Server could not restart the file transfer request. The Platform Server will therefore restart the file transfer from the beginning.

  No user action is required. This is an information message only and tells the user why a checkpoint restart cannot be completed.

- PGTM7348I tttttttttt RECFM=VBS LRECL exceeds 32760 - Changed to 32760 for DSN: dddddddd

  Explanation:

  A transfer request was received for a VBS file, and the LRECL for this file was greater than the maximum LRECL supported by TIBCO MFT Platform Server for z/OS. This is an information message that indicates the LRECL was changed to the maximum LRECL supported (32760). No action is required.

- PGTM7349I Restart on RECFM=VB file detected: Repositioning to next block

  Explanation:

  A restart request was received by TIBCO MFT Platform Server for z/OS. This is an information message that is displayed under the following circumstances:

  - The file transfer was for a file receive (that is to say, TIBCO MFT Platform Server for z/OS was writing data)
  - The RECFM was VB
  - The restart was positioned to the block after the checkpoint was taken

  No action is required by the user when this message is displayed.

- PGTM7356I tttttttttt RESTART not supported on MAINTAINRDW - Restart turned off for file dddddddddd

  Explanation:

  The user specified the MAINTAINBDW or MAINTAINRDW parameter, but the transfer was defined to use checkpoint restart. The transfer will continue without checkpoint restart support.

  Checkpoint restart is not supported when the MAINTAINBDW or MAINTAINRDW parameter is defined.

- PGTM7357I tttttttttt RESTART not supported on TAPE LBI files - Restart turned off for file dddddddddd

  Explanation:

  The user was transferring LBI files and was attempting to use checkpoint restart. Checkpoint restart is not supported when using LBI. The transfer will continue without checkpoint restart support.

- PGTM7363I tttttttttt Unable to send VSAM file properties to the remote system

  Explanation:

  This is an information message indicating that the VSAM properties or a file is not sent to the remote system. This message is typically displayed after message PGTM7337, which describes the reason that a VSAM file cannot be opened. The transfer continues, but the VSAM attributes are not sent to the remote system.

- PGTM7400I Physical Record Larger than Logical Record for Activity xxxx

  Explanation:

  This message is issued when the record being written is larger than the logical record length of the MVS dataset.

  Make sure that the maximum string length is less than or equal to the logical record length.

- PGTM7401I Invalid Record Separator xxxx found for Activity yyyy

  Explanation:

  If you receive this message, contact TIBCO Support for assistance.

- PGTM7402I tttttttttt Invalid $SYSOUT field - must be CLASS/DEST/WRITER/FCB/FORM: xxxxxxxxxxxxxxxxxxxxxx

  Explanation:

  The user was performing a file to file transfer and specified the Platform Server for z/OS file name as $SYSOUT. This indicates to the Platform Server that the request is actually a file to print request. The data following `$SYSOUT` describes the z/OS fields that are passed to the JES. Only the following parameters are supported: CLASS, DEST, WRITER, FCB, and FORM. The user should make sure that the data passed is one of these parameters. The user specified an invalid field that is displayed in this message. The transfer request is terminated with errors.

- PGTM7403I tttttttttt Invalid $SYSOUT field value for parameter: xxxxxxxx

  Explanation:

  The user was performing a file to file transfer and specified the Platform Server for z/OS file name as $SYSOUT. This indicates to the Platform Server that the request is actually a file to print request. The data following `$SYSOUT` describe the z/OS fields that are passed to the JES. The user specified a valid parameter, but the data defined for that parameter was invalid. The user should insure that the data passed for these parameters is valid. The transfer request is terminated with errors.

- PGTM7450I Activity tttttttttt canceled by operator request

  Explanation:

  An operator canceled transfer activity tttttttttt.

- PGTS7500I xxxx WILL USE A SYSTEM LINKAGE INDEX OF xxxx FOR ENHANCED CROSS MEMORY SERVICES

  Explanation:

  This is an information message.

- PGTS7650I CREATING TABLE ENTRY FOR XMS SERVICES

  Explanation:

  This is an information message.

- PGTS7700I CONNECTION TO XMS ENTRY TABLE SUCCESSFUL XMS SERVICES ARE NOW ENABLED

  Explanation:

  This is an information message.

- PGTS8763D REPLY -T- to Terminate not waiting for subtasks to end - otherwise shutdown will wait for them to end

  Explanation:

  Currently, some subtasks are active for this started task. You can choose to end the started task without waiting for the subtasks to end.

- PGTS9001I STOP command being processed

  Explanation:

  This is a normal information message that is displayed when the STOP command is issued to bring the started task down.

- PGTS9100I ALET NUMBER CREATED: xxxx DSPTOKEN yyyy

  Explanation:

  This is an information message which shows the STOKEN that is returned when a dataspace is created.

- PGTS9438I Detaching dispatcher subtask

  Explanation:

  Information message issued at shutdown.

- PGTS9450I SNAP DUMP PROCESSING HAS COMPLETED

  Explanation:

  The snap dump that was taken has finished.

- PGTN9777D xxxx

  Explanation:

  This is a detailed diagnostic message for use by platform field engineering staff only.

- PGTN9998I Detail MSG: xxxx

  Explanation:

  This is a diagnostic message used by platform field engineering staff only. It displays information from the Platform Servers internal control blocks.

Copyright © 2003-2021. TIBCO Software Inc. All Rights Reserved.