Information Messages

Explanation:

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

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.

Explanation:

The Platform Server signified by the xxxx has started.

Explanation:

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

Explanation:

WTO to issue CPU information from the Platform Server.

Explanation:

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

Explanation:

The Platform Server started task is starting.

Explanation:

This informational message is issued at startup and shutdown.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

Contact TIBCO technical support to get a new Platform Server key.

Explanation:

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

Explanation:

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

Explanation:

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

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

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 is not processed.

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.

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.

Explanation:

The tracing for TCP/IP is started successfully.

Explanation:

The tracing for TCP/IP is stopped successfully.

Explanation:

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

Explanation:

Contact TIBCO technical support if you receive this message.

Explanation:

Contact TIBCO technical support if you receive this message.

Explanation:

Contact TIBCO technical support if you receive this message.

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.

Explanation:

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

Explanation:

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

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.

Explanation:

The operator issued a GLOBALREFRESH command. This message indicates whether the command was processed successfully or with errors. If the command indicates any errors, additional messages are displayed to indicate the cause of the error.

Explanation:

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

Explanation:

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

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.

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.

Explanation:

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

Explanation:

This message is informational only. No action is necessary.

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.

Explanation:

ContactTIBCO technical support if you receive this message.

Explanation:

This message is informational only.

Explanation:

Contact TIBCO technical support if you receive this message.

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 write it in encrypted format to the AUTHKEY DD statement.

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 the result of the AUTHDISP operator command.

Explanation:

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

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 technical support.

Explanation:

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

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 reduce paging.

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.

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.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

This is an informational 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.

Explanation:

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

Contact TIBCO technical support to receive 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 technical support to receive 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 technical support to receive a new product license key.

Explanation:

The Platform Server is starting up and finds a SAPI request in the queue. The Platform Server purges any SAPI request at startup. The Platform Server SAPI interface then checks the JES spool for any requests.

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.

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 informational purposes only.

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 informational purposes only.

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.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

The Platform Server COS operator command is 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.

Explanation:

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

Explanation:

The Platform Server COS operator command is 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.

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.

Explanation:

This message is displayed at startup and 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.

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.

Explanation:

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

Explanation:

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

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.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

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.

Explanation:

This message indicates that a work queue item has an expiration date that is earlier then the current date. Therefore the Platform Server dispatcher purges it from the work queue.

Explanation:

This is an informational 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 the file.

Explanation:

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

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 rather than dispatch it.

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.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

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.

Explanation:

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

Explanation:

The SECAUDIT modify command was issued and processed successfully.

Explanation:

The SECADMIN modify command was issued and processed successfully.

Explanation:

The SECLOGV modify command was issued and processed successfully.

Explanation:

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

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.

Explanation:

The NODECLASS parameter entered exceeds the NODE WINNERS parameter. The transfer can never 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.

Explanation:

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

Explanation:

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

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 informational 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.

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.

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.

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.

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 can 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.

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 can be initiated to this node.

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 are 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.

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.

Explanation:

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

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.

Explanation:

The operator entered the ZEDCSTAT command. This message shows the status of the ZEDC interface and the TLS interface. Status is either Active or Inactive.

Explanation:

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

Explanation:

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

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.

Explanation:

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

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.

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.

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.

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.

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.

Explanation:

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

Explanation:

This is an informational message that warns the audit data set is filled by 80 percent. This is displayed so 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 data set.

Explanation:

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

Explanation:

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

Explanation:

A snap dump has been taken and is now complete.

Explanation:

This is an informational message used for debugging purposes.

Explanation:

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

Explanation:

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

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.

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.

Explanation:

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

Explanation:

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

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.

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.

Explanation:

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

Explanation:

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

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.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

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.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

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 technical support.

Explanation:

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

Explanation:

Check your GLOBAL definitions and correct the error.

Explanation:

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

Explanation:

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

Explanation:

The modify command disables the member specified successfully.

Explanation:

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

Explanation:

The queue entry xxxx is marked for termination.

Explanation:

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

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.

Explanation:

Contact TIBCO technical support if you receive this message.

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 informational message and is written only to the Platform Server log file.

Explanation:

Contact TIBCO technical support if you receive this message.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

Contact TIBCO technical support if you receive this message.

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.

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.

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.

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.

Explanation:

The value entered for the EXTENDED_SECURITY_RESOURCE parameter in the GLOBAL member is incorrect. The valid values must be between 1 and 8 characters long. Correct this parameter and restart the Platform Server started task.

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.

Explanation:

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

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 is disabled.

Explanation:

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

Explanation:

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

Explanation:

This is an informational message.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

This is an informational message that indicates that the ACB was closed successfully.

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.

Explanation:

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

Explanation:

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

Make sure the ACB listed here is varied active.

Explanation:

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

Make sure the ACB listed here is varied active.

Explanation:

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.

Explanation:

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

Explanation:

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

Explanation:

Debug message for internal use.

Explanation:

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

Explanation:

This message is used for debugging purposes.

Explanation:

This message is used for debugging purposes.

Explanation:

This message is used for debugging purposes.

Explanation:

This message is used for debugging purposes.

Explanation:

This message is used for debugging purposes.

Explanation:

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

Explanation:

This is a normal termination message.

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.

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.

Explanation:

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

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.

Explanation:

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

Explanation:

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

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.

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.

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.

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 informational purposes only and displays the size of the SEND and RECEIVE buffers associated with the file transfer request.

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.

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.

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.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

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.

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.

Explanation:

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

Explanation:

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

Explanation:

The transfer request is purged because of a security error.

Check the user ID and password used for this transfer.

Explanation:

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

Explanation:

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

Explanation:

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

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.

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.

Explanation:

This is a debug message for platform internal use.

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.

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.

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.

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.

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 Technical Support.

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.

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.

Explanation:

Debug message for platform internal use.

Explanation:

Debug message for platform internal use.

Explanation:

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

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.

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.

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 complete.

Explanation:

A Command Center user tries to browse the Platform Server AUDIT file. The Platform Server performs the necessary checks, and 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.

Explanation:

The Platform Server Command Center issues a request to extract records from the Platform Server audit file. This message is an informational 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.

Explanation:

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

Explanation:

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

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).

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) data space STOKEN.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

This is an informational message.

Explanation:

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

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.

Explanation:

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

Explanation:

DNI is processing a data set 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.

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.

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.

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.

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.

Explanation:

DNI is processing a catalog locate request for data set dddddddd. The number of data sets 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 data sets are returned. DNI processes the first nn data sets that are returned. As DNI continues to process these data sets, the number of data sets returned by the locate request decreases, and eventually falls below nn data sets.

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 data set filter used. This message is displayed once for each enabled DNI definition.

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.

Explanation:

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

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.

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.

Explanation:

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

Explanation:

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

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.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

When you receive this message, contact TIBCO technical support.

Explanation:

Activity failed to the remote system.

See previous diagnostic messages for the possible cause of failure.

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.

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.

Explanation:

The remote file is deleted successfully.

Explanation:

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

Explanation:

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

Explanation:

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

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.

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.

Explanation:

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

Explanation:

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

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.

Explanation:

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

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 technical support. To turn off the SSL Debug messages, issue the Platform Server SSLDEBUG=NO operator command.

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 technical support. To turn off the SSL Debug messages, issue the Platform Server SSLDEBUG=NO operator command.

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.

Explanation:

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

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.

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 informational message only. No action is required. The transfer continues normally with the new encryption type.

Explanation:

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

Explanation:

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

Explanation:

The Platform Server requested a data set 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.

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 might retry the request at a later time, depending on the number of tries defined for the transfer request.

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 and no COS processing is 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.

Explanation:

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

Explanation:

The Platform Server was processing a directory transfer request. This is an informational message that indicates the Platform Server 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 successful, while a non-zero return code indicates that the request failed.

Explanation:

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

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.

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.

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 was being processed through the RocketStream accelerator. Where, aaaaaaaa defines the activity associated with the request, while iiiiiiiii:pppp defines the IP address and port of the RocketStream server.

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.

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.

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 is executed with WAIT=YES.

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.

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.

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.

Explanation:

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

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.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

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.

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.

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.

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.

Explanation:

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

Explanation:

This message is displayed when a successful TLS negotiation is completed for transaction tttttttttt. xxxxxxxx defines the TLS protocol used, while 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.

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.

Explanation:

The 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.

Explanation:

The 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 will be displayed following this message. This entry in the SSLAUTH file will not be enabled.

Explanation:

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

Explanation:

The 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 will be displayed following this message. This entry in the SSLAUTH file will not be enabled.

Explanation:

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

Explanation:

The 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 will be displayed following this message. This entry in the SSLAUTH file is not enabled.

Explanation:

The 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.

Explanation:

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

Contact TIBCO technical support if this error re-occurs.

Explanation:

The 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 is enabled. You must change the SSLAUTH file to match these DCB characteristics.

Explanation:

The SSL configuration was processing the SSLAUTH file, but the SSLAUTH DD statement was not defined. No SSLAUTH records is enabled. You must add the SSLAUTH DD statement to the Platform Server startup JCL, and stop and start the Platform Server.

Explanation:

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

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

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 informational message only. No action is required.

Explanation:

The Platform Server was performing a Post Processing Action (PPA) for activity tttttttttt. xxxxxxxx defines the action that was being performed on ccccccccc. 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.

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 informational purposes only.

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 data set. The data set that is to be renamed is ddddddd. This message is displayed for informational purposes only.

Explanation:

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

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 informational message only.

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

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 informational message and shows how many good and error records were processed.

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.

Explanation:

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

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 informational purposes only. If you do not want to use the SUBJCL feature, this message can be ignored.

Explanation:

This message is displayed at startup and 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.

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.

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.

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 informational message; no action is required.

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 informational purposes only.

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 re-submit the transfer.

Explanation:

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.

Explanation:

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.

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 informational message. No action is required.

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 is ignored during this type of transfer, but that the NODE CONTENTION_WINNERS parameter is used to throttle the number of transfers of this type that can be executed simultaneously. This is an informational message. No action is required.

Explanation:

The Platform Server was running a script. This is an informational message that indicates the script execution was started, 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.

Explanation:

The Platform Server was running a script. This is an informational 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.

Explanation:

The Platform Server was running a script. This is an informational 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.

Explanation:

The Platform Server was running a script. This is an informational message that indicates the script execution was unsuccessful and that any output for this script is 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 is tried again at the next error interval.

Explanation:

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

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.

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 is defined in this message. This message is for information purposes only.

Explanation:

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

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.

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 informational purposes only.

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 informational purposes only.

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 informational purposes only.

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 informational purposes only.

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 informational purposes only.

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 informational purposes only.

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.

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.

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.

Explanation:

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

Explanation:

The subtask cannot allocate enough storage to do the transfer.

Increase the Region parameter in the transfer job.

Explanation:

A message was received from node xxxx.

Explanation:

This is an informational message stating that the File to Job transfer was submitted to the remote system.

Explanation:

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

Explanation:

Activity xxxx is purged for security reasons.

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 Technical Support.

Explanation:

Internal diagnostic messages issued during debugging and tracing.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

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

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

Internal debugging message.

Explanation:

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

Explanation:

Informational message.

Explanation:

An error occurred loading the transmission code.

Contact TIBCO Technical Support for assistance.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

See other accompanying messages for more information.

Explanation:

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

See accompanying messages in the OSIMSG log or MVS SYSLOG for more information.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

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

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.

Explanation:

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

Explanation:

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

Explanation:

Requested action was not allowed because the file already exists.

Explanation:

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

Explanation:

This is a normal message that is displayed when a Platform Server File to Job transfer is submitted.

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.

Explanation:

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

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 was not exhausted, this transfer is retried at the next dispatch interval.

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 Technical Support.

Explanation:

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

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.

Explanation:

Data set ddddddddd was deleted because of the disposition parameter specified on the file transfer request. xxxxxxxx determines whether the data set was 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.

Explanation:

The user was attempting to perform a file transfer for a variable spanned or fixed standard file and 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.

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 Technical Support.

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 OPEN or CLOSE (xxxxxx). The return codes are displayed as rr and ss. These return codes are defines in the IBM manual OS/390 DFSMS Macro Instructions for Data Sets.

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.

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 will be started from the beginning.

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.

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 cannot restart the file transfer request. The Platform Server will therefore restart the file transfer from the beginning. No user action is required. This message is an information message only and tells the user why a checkpoint restart cannot be completed.

Explanation:

A transfer request was received for a VBS file and the LRECL for this file was greater than the maximum LRECL supported by MFT. This is an informational message that indicates the LRECL was changed to the maximum LRECL supported (32760). No action is required.

Explanation:

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

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.

Explanation:

The user was transferring an 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.

Explanation:

This message is an information message indicating that the VSAM properties or a file will not be 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.

Explanation:

This message is issued when the record being written is larger than the logical record length of the MVS data set. Make sure that the maximum string length is less than or equal to the logical record length.

Explanation:

Contact TIBCO Technical Support.

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 will be passed to JES. Only the following parameters are supported: CLASS, DEST, WRITER, FCB, and FORM. The user specified an invalid field that is displayed in this message. The user should make sure that the data passed is one of these parameters. The transfer request is terminated with errors.

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 will be passed to 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.

Explanation:

Abort was requested for the specified transfer.

Explanation:

This is an informational message.

Explanation:

This is an informational message.

Explanation:

This is an informational message.

Explanation:

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

Explanation:

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

Explanation:

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

Explanation:

Informational message issued at shutdown.

Explanation:

The snap dump that was taken has finished.

Explanation:

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

Explanation:

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