TIBCO MFT Platform Server for z/os Message Manual

Transcription

1 TIBCO MFT Platform Server for z/os Message Manual Software Release November 2014 TIBCO provides the two-second advantage

2 Document Information Message Manual for z/os Important Information SOME Platform SOFTWARE EMBEDS OR BUNDLES OTHER Platform SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED Platform SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED Platform SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER Platform SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF Platform SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of Platform Software Inc. TIB, Platform, Platform Adapter, Predictive Business, Information Bus, The Power of Now, Platform ActiveMatrix BusinessWorks, Silver, Managed File Transfer, MFT Command Center, MFT Internet Server, Platform Server, Platform Server Agent, Slingshot, and TIBCO Vault Server are either registered trademarks or trademarks of Platform Software Inc. in the United States and/or other countries. EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. Platform SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright Platform Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information TIBCO welcomes your comments on this publication. Please address your comments to: TIBCO Software Inc. 200 Garden City Plaza Garden City, New York USA Web site: Technical Support support@tibco.com Technical Support Call Centers: North and South America: or ( TACS) EMEA (Europe, Middle East, Africa): +44 (0) Australia: or Asia: When you send information to TIBCO, you grant TIBCO a non-exclusive right to use or distribute the information in any way TIBCO believes appropriate without incurring any obligation to you. ii Copyright TIBCO Software Inc All Rights Reserved.

3 Message Manual for z/os Messages List Table of Contents 1. MESSAGE LIST... 4 Copyright TIBCO Software Inc All Rights Reserved. 3

4 Messages List Message Manual for z/os Preface Intended Audience This publication is intended for those individuals responsible for installing, configuring, managing, and operating the MFT Platform Server for z/os. About This Manual This message manual provides details for the messages associated with the MFT Platform Server for z/os product. Consult your network manager regarding network equipment and procedures at your installation site. 4 Copyright TIBCO Software Inc All Rights Reserved.

5 Message Manual for z/os Messages List 1. Message List This section is a complete listing of all of the messages. PGTCB001I Activity Queued to Server: xxxxxxxxx with the following Transaction ID: tttttttttt This message is displayed in the Batch Interface when a transfer has been queued to the started task. xxxxxxxx defines the STC Name, LU Name or IP Address/IPName of the started task. tttttttttt defined the transaction ID associated with the transfer. This message is for information purposes only and does not require any actions. PGTS000I Platform Server xxxx INITIALIZED The Platform Server signified by the xxxx has started. PGTS0000I Another Server with the name: xxxx is active Another Platform Server with the same name is already active. The second Server will automatically be shut down. PGTS0012I OSIMSGS LOG File Freed This is an informational message that is issued in response to the RELEASE,LOG Platform Server Operator command. PGTS0013E Server: ssssssss not APF authorized - started task terminating The started task (ssssssss) detected that it was not running APF authorized. This is typically caused by a STEPLIB library not being in the z/os APF list. The started task will terminate. Insure that all of the libraries in the STEPLIB are authorized, and restart Platform Server. PGTS0022I CPU Information: Version Code=xxxx Id Number=yyyy Model Number=zzzz WTO to issue CPU information from the Platform Server. PGTS0023E *****LOG DATASET FULL - MESSAGE NOT LOGGED***** The log data set is full and will not record any more messages. PGTS0024I Message xxxx not found If you receive this message, contact TIBCO Technical Support. Supply the message number that you received as indicated by the "xxxx". PGTS0026I Platform Server Suite xxxx initialized The Platform Server started task is starting. PGTS0029I Platform Advanced SNA services being [loaded stopped] Informational message issued at startup and shutdown. Copyright TIBCO Software Inc All Rights Reserved. 5

6 Messages List Message Manual for z/os PGTS0031I Platform Advanced TCP services xxxx This messages states if the TCP services will be loaded or not and the reason. PGTS0032I [ FUSIONSNA FUSIONTCP ] request by xxxx Denied - Application NOT authorized by GLOBAL key 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 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 A Platform Server request has been initiated by NODE yyyyyyyy. The request type is xxxxxxxx. The temporary key that has been assigned has expired. Platform Server will no longer honor any incoming or outgoing requests. Contact Technical support to get a new Platform Server key. PGTS0037I Another Server with the name xxxx is active You attempted to bring up two Platform server started tasks, each with the same name. This is not supported, and so the second server will shut itself down immediately. PGTS0038I Platform Server xxxx Shutting Down The Platform Server started task is in the process of termination. This is a normal message. PGTS0039I RDJFCB failed - Audit DSN not found The Audit data set must be defined before bringing up the Platform Server started task. Use the DEFAUDIT member in the Samplib data set as an example of how to define the Audit data set. PGTS0040I Platform Server xxxxxxxxxxxx processing stopped: Retry later An Initiator or Responder request (xxxxxxxx) was detected by Platform Server, but processing has been quiesced by the INITIATORSTOP or RESPONDERSTOP commands. This message is meant to notifty the user why a file transfer request has not been processed. PGTS0041E Incoming request from partner xxxx denied - yyyy count of zzzz exceeded The transfer request from the partner is denied. Either the MAXINITS, MAXRESP or MAXTOTAL count has been exceeded. These values are set in the GLOBAL member and may be adjusted to control concurrent transfer activity. PGTS0042I Platform Server request from node nnnnnnnn exceeded contention loser max of xx: Try request later A request was received from node nnnnnnnn. Platform Server detected that the number of responder tasks associated with this node exceeded the LOSERS parameter defined in the NODE definition. Platform Server sends this message back to the system that initiated the request. The request is terminated, but can be retried at a later time. PGTS0047I Error opening TCPTRAC - tracing terminated 6 Copyright TIBCO Software Inc All Rights Reserved.

7 Message Manual for z/os Messages List 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 were specified correctly. PGTS0048I TCPTRAC DD statement opened successfully The tracing for TCP/IP was started successfully. PGTS0049I TCPTRAC DD statement closed successfully The tracing for TCP/IP was stopped successfully. PGTS0050I Work Queue Entry for Activity xxxx purged. The work queue contained a transaction request that has been purged. This is a normal message. PGTS0051I Invalid slot number for PURGEQ - xxxx Contact TIBCO Technical Support if you receive this message. PGTS0052I PURGEQ option xxxx not supported Contact TIBCO Technical Support if you receive this message. PGTS0053I Work Queue Entry address for PURGEQ is Invalid -xxxx Contact TIBCO Technical Support if you receive this message. PGTS0054I Activity xxxx for yyyy queued successfully zzzzzzzz Activity for transaction xxxx for IPADDR or NODE yyyy has been successfully queued to the started task. Parameter zzzzzzzz will give additional information about the source of the request. For example, on a request queued as a result of the EVERY command, by EVERY request will be displayed. PGTS0055I Queue Entry for Activity xxxx Already in Purge KILL State - waiting for TASK termination Someone attempted to purge Activity xxxx from the work queue that has already been marked for purge. No further action is necessary. PGTS0056E OSSERVER: SYNTAX ERROR IN PARM FIELD: xxxx During startup of the Platform Server task an error was detected in the PARM field specified on the EXEC statement. Correct the error and restart Platform Server. PGTS0057E OSSERVER: INVALID PARAMETER IN PARM: xxxx An invalid parameter was detected. Correct the PARM field on the EXEC statement and restart Platform Server. PGTS0058E OSSERVER: TOO MANY PARM PARAMETERS Too many parameters were passed to Platform Server, correct the PARM field on the EXEC statement and restart the Platform Server. Copyright TIBCO Software Inc All Rights Reserved. 7

8 Messages List Message Manual for z/os PGTS0059E OSSERVER: INVALID DATA IN PARAMETER: xxxx An invalid operand was passed to a parameter. Correct the PARM field on the EXEC statement and restart the Platform Server. PGTS0060E OSSERVER: Errors in PARM field - Started task terminating An error has been detected parsing the parameters. See previous message for a detailed description of that error. PGTS0061E Error loading U7SVC - Global CA7 interface turned off This message is issued for a CA7 load failure. This would occur only if you specify CA7=YES in the Global parameters and then the CA7 module U7SVC is not found. PGTS0062I Resetting any nodes with errors The RESETINTERVAL has been reached and any nodes that are in error are now reset to allow transfers to retry. Action: None. This is an informational message. PGTS0063I STARTTCP command issued - TCP Already started: You must use TERMTCP command before restarting TCP interface The user issued the STARTTCP operator command, but the TCP interface was not currently stopped. If you wish to refresh the TCP interface, you should issue the TERMTCP command before issuing the STARTTCP command. When this message is issued, no action takes place on the TCP interface. PGTS0064I GLOBALREFRESH command completed {Successfully with errors The operator issued a GLOBALREFRESH command. This message indicates whether the command was processed successfully, or with errors. If the command indicates that there are errors, additional messages will be displayed to indicate the cause of the error. PGTS0065E NODE REFRESH for nnnnnnnn invalid: Only TYPE=NODE allowed The user has entered the REFRESH command, but member nnnnnnnn was not a NODE definition. Only NODE definitions can be refreshed. Check member nnnnnnnn to insure that it is a NODE definition. PGTS0066E Error in REFRESH command syntax The user has entered the REFRESH command, but the syntax is incorrect. The correct syntax is F stcname,ref,nodename. PGTS0067I Detail for xxx node nnnnnnnn The user has entered the NODE operator command and has specified the node name to be displayed as nnnnnnnn. xxxx will indicate if the display is for an SNA or TCP. Message PGTS0068I will follow with detailed information about the node. PGTS0068I iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii The user has entered the NODE operator command. This message is used to display detailed information about the that is being displayed. 8 Copyright TIBCO Software Inc All Rights Reserved.

9 Message Manual for z/os Messages List PGTS0069I Error in DISABLE command syntax xxxx 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 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 A dynamic enable command entered via the console modify command was successfully processed. PGTS0072I Enable for node xxxx failed. Node already active This message is informational only. No action is necessary. PGTS0073I Node xxxx not defined in Nodes PDS There is no member xxx in the CONFIG library. Verify that the node is properly defined and that you spelled the member name correctly. PGTS0074E ERROR DELETING CIB ENTRY The Platform Server was attempting to process an operator MODIFY console command and received an error trying to free the CIB. If the Platform Server does not respond to Operator commands, contact TIBCO Technical Support. Otherwise, this message can be treated as an informational message. PGTS0075I Nodes entry for Remote system xxxx was not found Contact TIBCO Technical Support if you receive this message. PGTS0076I Nodes entry for Remote system xxxx was found This message is informational only. PGTS0077I Select code xxxx invalid for NODEOP Contact TIBCO Technical Support if you receive this message. PGTS0078E ERROR SETTING CIB The Platform Server was attempting to process an operator MODIFY console command and received an error trying to free the CIB. If the Platform Server does not respond to Operator commands, contact TIBCO Technical Support. Otherwise, this message can be treated as an informational message. PGTS0079E ERROR NOT RUNNING AS A STARTED TASK. PLEASE RERUN JOB AS A STARTED TASK The Platform Server started task can not be run as a batch job, it must be run as a started task. Correct the error and bring up the Platform Server as a started task. Copyright TIBCO Software Inc All Rights Reserved. 9

10 Messages List Message Manual for z/os PGTS0080E AUTHKEY DD missing: Required when Global AUTHENTICATE is defined as ALL - STC terminating The Global AUTHENTICATE parameter was defined as ALL for either the Initiator or Responder, but the AUTHKEY DD statement was not defined in the Platform Server startup JCL. The started task will terminate. Insure the AUTHKEY dataset is defined, and that the AUTHKEY DD statement is defined in the Platform Server startup JCL. PGTS0081E Error opening AUTHKEY DD for xxxxx The Platform Server attempted to open the AUTHKEY DD statement for INPUT or OUTPUT, but received an error. The Platform Server will attempt to recover from the error and continue. PGTS0082E Abend xxx opening AUTHKEY DD for xxxxxxxx The Platform Server received an abend opening the AUTHKEY DD statement for INPUT or OUTPUT. The Platform Server will attempt to recover from the error and continue. PGTS0083E Abend nnn on AUTHKEY xxxxxxxx request The Platform Server received an abend on a GET, PUT or CLOSE request to the AUTHKEY file. The Platform Server will attempt to recover from the error and continue. PGTS0084E SYNAD exit entered on AUTHKEY xxxxxxxx request While processing the AUTHKEY DD statement, the SYNAD exit was invoked because of an error on the file. The Platform Server will attempt to recover from the error and continue. PGTS0085I AUTHKEY file does not contain valid Authentication key: Recreating the key The Platform Server read the data in the AUTHKEY DD statement, and determined that it was not a valid Authentication key. The Platform Server will create a new Authentication key and write 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 The Platform Server will use the 16 digit Authentication key xxxxxxxxxxxxxxxx when communicating with Platform Server Server systems. This key should be defined in the Platform Server system when the Platform Server Authentication is required. This message will be displayed at startup, and as the result of the AUTHDISP operator command. PGTS0087E Unable to create Authorization KEY: Global AUTHNTICATE is defined as ALL - STC terminating The Global AUTHENTICATE parameter was defined as ALL for either the Initiator or Responder, but the Platform Server was unable to validate or create an Authentication key. This is normally caused by a problem with the AUTHKEY DD statement. The Platform Server started task will terminate. Typically messages will be displayed prior to this message which documents the errors that occurred. Fix any problems with the AUTHKEY DD statement and restart the Platform Server. PGTS0088E AUTHKEY DD missing: Unable to create Authentication key The AUTHKEY DD statement was not defined. The Global AUTHENTICATE parameter was not defined as ALL for either the Initiator or Responder. Therefore the Platform Server can continue to operate. If Authentication is requested for an Initiator or Responder task, the request will fail. 10 Copyright TIBCO Software Inc All Rights Reserved.

11 Message Manual for z/os Messages List PGTS0089E Refresh failed for node nnnnnnnn: Member not enabled The user has entered the REFRESH command, but member nnnnnnnn is not currently enabled. The REFRESH command requires that the node to be refreshed be currently enabled. If this is the node that you want enabled, use the ENA command to enable the NODE. For a list of enabled nodes, use the NODES operator COMMAND. PGTS0090I Node nnnnnnnn has been reset successfully NODE nnnnnnnn has been reset by the RESET command. Additionally, any transfer request for this node has been reset as well. PGTS0091I Node nnnnnnnn not enabled: License Key Max Nodes of xxx exceeded The user attempted to enable node nnnnnnnn either at startup or through the ENABLE operator command, but enabling this node would have exceeded the maximum number of nodes allowed. Some companies purchase the Platform Server with and are given a license key that defines the maximum number of node entries that can be enabled. If you wish to enable more nodes, contact Platform Corporation Technical Support. PGTS0092I Queue Lookaside Initialization Found Knetwork Fusion Responder Activity xxxx. Entry is purged. 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 This message is normal and appears when the Platform Server is being initialized. It means that the work queue "index" has been 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. There was a transfer in progress when the Platform Server was last shut down. At startup time it's status has been reset to "inactive" so that it can be retried. PGTS0095I Queue Lookaside Initialization Found Activity xxxx Marked for purge. Entry is Purged. 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 was still on the queue but marked to be removed. The initialization code completed the purge. PGTS0096I Queue Lookaside Initialization Found Activity xxxx Has Invalid Status 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 This message is informational only. The message is normal at startup time. PGTS0098I Nodes Lookaside Dataspace Being Built This message indicates that the Platform Server initialization routines are building the index for the Copyright TIBCO Software Inc All Rights Reserved. 11

12 Messages List Message Manual for z/os nodes topology dataspace. This is a normal message at startup time. PGTS0099I Queue Lookaside Initialization Found Activity xxxx Logically purged. Audit record written. This is an informational message. It means that the Platform Server initialization routines had to finish purging a work queue entry that was marked for termination but was not yet flushed. PGTS0100I Product xxxxxxxx will expire in nn days: Contact TIBCO Technical Support for a new Product License key It has been determined that the product xxxxxxxx license key will expire in nn days. This message will be displayed once per day until the product actually expires. You must contact TIBCO Technical Support to receive a new product license key. PGTS0101I Product xxxxxxxx has expired: Contact TIBCO Technical Support for a new Product License Key It has been determined that 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. You must contact TIBCO Technical Support to receive a new product license key. PGTS0102I Product xxxxxxxx expires today: Contact TIBCO Technical Support for a new Product License Key It has been determined that the product xxxxxxxx license key will expire 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. You must contact TIBCO Technical Support to receive a new product license key. PGTS0103I Queue Lookaside Initialization Found Activity tttttttttt SAPI Request Purged: Audit record written 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 will then check the JES spool for any requests. PGTS0104W Server Not authorized to purge MSGQ qqqqqqqq: Purging all records in Queue The Platform Server has been configured to use SSL. Global parameter SSL_MESSAGE_QUEUE_NUMBER defines the message queue number(qqqqqqqq) that is being used. At the start of the Platform Server, the message queue is purged, and then re-created. This message indicated that the Platform Server could not purge the message queue. Instead, the Platform Server will purge each record in the Queue. This can happen because a message queue was created by a different started task. Each started task should use a unique message queue. PGTS0105E Global SSLIPPORT defined but $SSLDB profile not found: SSL Processing disabled The user defined the GLOBAL SSLIPPORT parameter with a non-zero value. That means that the Platform Server should start its SSL subtask. However, the Platform Server scanned its User Profile database, and cole not find the $SSLDB user defined. The $SSLDB user must be defined before the Platform Server can start SSL processing. When using a RACF Key Ring, the remote password should be defined with teh value "NULL". When using a key database, the remote password should be defined with the key of the key database. SSL processing is disabled. You must run the Platform 12 Copyright TIBCO Software Inc All Rights Reserved.

13 Message Manual for z/os Messages List Server user profile utility to add the $SSLDB user profile, and then stop and start the Platform Server started task. PGTS0106I Starting SSL Task using IPPORT ppppp The Platform Server has been configured to use SSL. This message is displayed to show the IPPORT that the Platform Server will listen on for incoming SSL requests. PGTS0107I Purge SAPI Transaction tttttttttt for Node nnnnnnnn: Node entry not found - Transaction purged The Platform Server had completed a SAPI request, and was attempting to POST the node definition to notify it that the SAPI request was completed. The Platform Server was unable to find the NODE definition associated with the request. The transfer request continues, but the NODE definition is not posted. This message is displayed for informational purposes only. PGTS0108I Purge SAPI Transaction tttttttttt for Node nnnnnnnn: SAPI Request not pending - Transaction purged The Platform Server had completed a SAPI request, and was attempting to POST the node definition to notify it that the SAPI request was completed. The Platform Server found the NODE definition associated with the request, but the NODE definition did not indicate that a SAPI request was pending. The transfer request continues, but the NODE definition is not posted. This message is displayed for informational purposes only. PGTS0109I Starting Platform Server SAPI Interface This message indicates that the Platform Server SAPI interface was starting as a result of the GLOBAL SAPI_INTERFACE parameter being set to YES. PGTS0110I Platform Server SAPI Interface Terminating This message indicates that the Platform Server SAPI interface was terminating. Termination is done only when the Platform Server is terminated. PGTS0111E Platform Server SNA and TCP keys not defined: STCssssssss terminating The Platform Server was brought up without a valid SNA or TCP key. Since the Platform Server cannot continue running under this circumstance, the Platform Server started task will be shut down. You must contact TIBCO technical support to get valid license keys. PGTS0112I Platform Server COLD start: All requests on the WORKQ will be purged The user entered the START=COLD option 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 will be deleted because the of the cold start request. PGTS0113I Platform Server COLD start: Activity tttttttttt purged from the Work Queue The user entered the START=COLD option 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 due to the cold start request. Copyright TIBCO Software Inc All Rights Reserved. 13

14 Messages List Message Manual for z/os PGTS0114I COS Display Summary: nn entries displayed The User entered the Platform Server COS operator command 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 message is displayed and shows how many COS entries are enabled. PGTS0115E COS Detailed Inquiry failed: COS cccccccc not currently enabled The User entered the Platform Server COS operator command to display COS entry cccccccc, but this entry is not currently enabled so the COS command fails. Check the spelling of entry cccccccc and fix if necessary. You can use the Platform Server ENA command to enable the COS entries. PGTS0116I COS Name=cccccccc SBUFSIZE=ssss RBUFSIZE=rrrr The User entered the Platform Server COS operator command without any additional values. This command causes a summary of all of the ENABLED COS entries to be displayed. 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 The User entered the Platform Server COS operator command and specified a specific COS entry to display detailed information. 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 Member nnnnnnnn in the node configuration library pointed to by the CONFIG DD in the startup JCL, was not activated because the member was defined with AUTOENABLE=NO. This message is for information purposes only. ttttt defines the type of member that was not enabled. PGTT0120E Node member nnnnnnnn not enabled: LU_NAME/IP_ADDR/IP_NAME parameters not defined Member nnnnnnnn in the node configuration library pointed to by the CONFIG DD in the startup JCL, is not a valid node. Edit the nnnnnnnn member and correct the parameters. Refer to the "Node Definition Parameters" section of the Platform Server for z/os Installation and Operations Guide for more information on node parameters. Once the parameter(s) has been corrected enable the node again. PGTS0120E TCP Initialization failed: Repl E(nd) C(ontinue), R(etry) During the started task TCP initialization, an error was detected. This error message allows the operator the ability to define the action that should be taken: E Terminate the started task C Continue processing; TCP will be disabled. TCP can be enabled through the STARTTCP operator command R Retry the TCP request. While waiting for an operator to respond to this message, the started task will attempt to perform TCP initialization every 30 seconds. If initialization is successful, this message will be deleted and started task initialization will continue normally. PGTS0121E INITAPI Failed: Started Task xxxxxxx Terminating 14 Copyright TIBCO Software Inc All Rights Reserved.

15 Message Manual for z/os Messages List During the started task TCP initialization, an error was detected. Error message PGTS0120E was displayed. The operator replied E to that message. This message indicates that the started task is terminating. PGTS0122I Hardware Encryption support: mmmmmmmmmmmmmm 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, MFT Platform Server for zos will use hardware encryption when using AES256 and AES128. PGTS0123I Queue Lookaside Initialization Found Activity with invalid TransId: Record purged and audit not written During the MFT Started task initialization, MFT detected a request in its WORKQ that did not have a valid Initiator or Responder Transaction Id. The request is removed from the WORKQ. Since the request is not formatted properly, a record is NOT written to the Audit log. PGTS0147I Queue is Full, Transfer Request Denied The work queue is full and can not accept any more requests. The server should be stopped. The work queue VSAM file should be backed up, deleted and redefined with more space. PGTS0148I Activity xxxx Expired and will be deleted from work queue This message indicates that a work queue item had an expiration date that was earlier then the current date. Therefore the Platform server's dispatcher purged it from the work queue. PGTS0149I Platform Server Initiator Dispatcher Active This is an informational message only. The Server has attached a dispatcher task, which will continuously scan the work queue looking for activities that are eligible to be initiated. When the dispatcher finds them it will attach transmission subtasks to actually perform the activity (eg. to transfer the file). PGTS0150I Beginning Scan of Work Queue for Initiator Activities 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 An activity had been queued with a non-zero limit specified for the number of attempts that were allowed. This limit was reached so the dispatcher purged the activity from the work queue rather than dispatch it. PGTS0152I Initiator Now Waiting after scan of Work Queue The Platform Server Dispatcher completed its scan of the work queue and will become dormant until the "New Cycle" time expires or until new entries are queued. PGTS0153I Wake up and scan initiator Work Queue again The New Cycle timer has popped and the dispatcher will resume looking for work items to dispatch. PGTS0155I Platform Server Initiator Dispatcher shutting down normally This message indicates that the Platform Server is being shutdown. This is a normal message. Copyright TIBCO Software Inc All Rights Reserved. 15

16 Messages List Message Manual for z/os PGTS0156E Dispatcher DIV Save Error - See VSAM diagnostic message - Dispatcher Terminating Abnormally This message indicates that the DIV Save macro returned a bad return code. This indicates an exposure that if the Platform Server is shutdown, the in-storage work queue contents could be corrupted! Do not queue new activities until this is resolved; let critical file transfers finish without shutting the Platform Server down, then contact TIBCO Technical Support. PGTS0157E Post Error Routine Driven in Dispatcher Contact TIBCO Technical Support if you receive this message and have the Platform Server log available. PGTS0159E Error in PURGE command syntax xxxx The Console Modify command to purge an item from the work queue was entered but the operand contained an invalid syntax. The proper syntax is "F servername,purge,activity_number". PGTS0160E Error in DELETE command syntax xxxx The Console Modify command to delete an item from the work queue was entered but the operand contained an invalid syntax. The proper syntax is F servername,delete, activity_number ". PGTS0161E Error in HOLD command syntax xxxx The Console Modify command to place an activity into Hold status was entered incorrectly. The correct syntax is "F servername,hold, activity_number ". PGTS0162E Error in RELEASE command syntax xxxx The Console Modify command to place an activity into Release status was entered incorrectly. The correct syntax is "F servername,release, activity_number " PGTS0163E Error in SUSPEND command syntax xxxx The Console Modify command to suspend an activity was entered incorrectly. The correct syntax is "F servername,suspend, activity_number " PGTS0164E Invalid SSLDEBUG parameter xxxxxx: must be YES or NO The use has entered the SSLDEBUG operator command, but entered an invalid value. Valid values are YES or NO. PGTS0165E SSLDEBUG changed to xxxxx The user has entered the SSLDEBUG operator command correctly. The Platform Server has changed the SSL degug value to either YES or NO. PGTS0166E PURGE command failed for Activity xxxx RC=yyyy The Console Modify command to purge an activity from the work queue failed. PGTS0167E DELETE command failed for Activity xxxx RC=yyyy 16 Copyright TIBCO Software Inc All Rights Reserved.

17 Message Manual for z/os Messages List The Console Modify command to delete an activity from the work queue failed. PGTS0168E HOLD command failed for Activity xxxx The Console Modify command to hold an activity from the work queue failed. PGTS0169E RELEASE command failed for Activity xxxx The Console Modify command to release an activity from the work queue failed. PGTS0170E SUSPEND command failed for Activity xxxx [RC=nnnn QUEUE STATUS NOT ACTIVE] The Console Modify command to suspend an activity from the work queue failed. PGTS0171E Invalid ESSDEBUG parameter xxxxxxx: must be WTO/LOG/NO The use has entered the ESSDEBUG operator command, but entered an invalid value. Valid values are WTO, LOG, or NO. PGTS0173I PURGE command successful for Activity xxxx The purge command was successfully executed to remove an activity from the work queue. PGTS0174I DELETE command successful for Activity xxxx The delete command was successfully executed to remove an activity from the work queue. PGTS0175I HOLD command successful for Activity xxxx The Console Hold command caused an activity to be moved to "Hold" status on the work queue. PGTS0176I RELEASE command successful for Activity xxxx The Console Release command caused an activity on Hold to be moved to "Release" status on the work queue. PGTS0177I SUSPEND command successful for Activity xxxx The Console Suspend command caused an activity to be put into "Suspend" status on the work queue. PGTS0178I Activity tttttttttt purged: Platform Server EVERY request has exceeded parameter EVERY_COUNT=ccccc A Platform Server request has been queued that uses the EVERY parameter, and the EVERY_COUNT parameter to limit the number of requests that should be scheduled. This message indicates that the EVERY_COUNT limit has been reached. The EVERY request will be purged from the queue. PGTS0179E Activity tttttttttt Queue ADD failed: Platform Server EVERY request not Queued at this time A Platform Server request has been queued that uses the EVERY parameter. The Platform Server is unable to add the request to the Queue, because the queue is full. The transfer request is NOT queued. It will be retried at the next scheduling interval. To update the number of requests allowed in the queue, use the WORKQ parm of the EXEC PGM=OSSERVER statement. Copyright TIBCO Software Inc All Rights Reserved. 17

18 Messages List Message Manual for z/os PGTS0180E Activity xxxx not found An operator command was entered for the particular activity designated in the message text, but the activity was not found on the work queue. Perhaps the activity number is incorrect, or perhaps the activity has already completed. PGTS0181E Activity xxxx has completed The Platform Server has finished processing an activity from the work queue. PGTS0182E Activity xxxx already in PURGE status Someone attempted to purge an activity from the work queue that has already been marked for purge. No further action is necessary. PGTS0183E Activity xxxx not INACTIVE Contact TIBCO Technical Support if you receive this message. PGTS0184E Activity xxxx not in HELD status Someone attempted to release an activity from the work queue that was not in Held status. PGTS0186E Error in SECAUDIT command syntax xxxx The SECAUDIT modify command was issued incorrectly. The correct format is F server_name,secaudit,yes or F server_name,secaudit,no. PGTS0187I SECAUDIT command successful The SECAUDIT modify command was issued and processed successfully. PGTS0188E Error in SECADMIN command syntax xxxx The SECADMIN modify command was issued incorrectly. The correct format is F server_name,secadmin,tso_id. The tso_id must be 8 characters or less. You can also enter the SECADMIN command without any input which turns off the notification to the Security Administrator. PGTS0189E SECADMIN command successful The SECADMIN modify command was issued and processed successfully. PGTS0190E Error in SECLOGV command syntax xxxx The SECLOGV modify command was issued incorrectly. The correct format is: F server_name,seclogv,option. Option must be YES/NO/LOG/WTO. PGTS0191I SECLOGV command successful The SECLOGV modify command was issued and processed successfully. PGTS0192I Responder Activity xxxx purged from Queue The transaction indicated was deleted from the queue. This is a normal message. 18 Copyright TIBCO Software Inc All Rights Reserved.

19 Message Manual for z/os Messages List PGTS0193I Responder Activity xxxx remains in Queue awaiting Checkpoint restart This transaction was interrupted but was set up using checkpoint restart and will start again from the last checkpoint. The transaction is put back on the queue awaiting restart. PGTS0194E Activity tttttttttt Invalid EVERY type xxxxxxxx: Request put on hold An internal error has occurred processing an EVERY request. The EVERY request is put on HOLD. If you receive this error, contact TIBCO technical support. PGTS0195E Activity tttttttttt Invalid EVERY DDXX (xxxxx) exceeds 31: Request put on hold The user has entered an EVERY=DDXX request. The value represented by xx is > 31. This is invalid and should typically be flagged by the batch or REXX program that initiated the request. The request is put on HOLD.. If you receive this error, contact TIBCO technical support. PGTS0196E Activity tttttttttt Queue ADD failed: LIST not found: Platform Server EVERY Request put on HOLD A Platform Server LIST request has been queued that uses the EVERY parameter. The Platform Server is unable to add the request to the Queue, because the LIST was not found. Check to see that the proper LIST entry was used and that the LIST was enabled at startup through the CONFIG or through the Platform Server ENA command. The transfer request is NOT queued. The Platform Server EVERY request is put on HOLD. PGTS0197E xxxxxxxx Request failed: GLOBAL REQUIRE_NODE_DEFINITION requires NODE to be defined A request was made to add a transfer to the Platform Server Request queue. Request type xxxxxxxx will be either Responder or Initiator. The Global parameter REQUIRE_NODE_DEFINITION defines whether a NODE definition is required for Initiator and Responder tasks. Insure the NODE is defined and enabled to the Platform Server. For Initiator requests, the NODE must be defined at the time the transfer request is queued. For Responder requests, the NODE must be defined at the time the request is received. PGTS0198E Activity tttttttttt Error xx on yyyyyyyy Date Conversion: EVERY request put on hold AN error occurred for activity tttttttttt in the Date conversion routine. The request is put on hold. If this error occurs contact TIBCO Technical Support. PGTS0199I Activity tttttttttt Transfer Nodeclass (nn) exceeds NODE WINNERS (ww): Request set to error The user entered a NODECLASS parameter that exceeded the NODE WINNERS parameter. The transfer will never run successfully. The transfer request will be set to an error state. The user should 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. PGTS0200E Responder services are not configured An incoming transfer or other activity request has come in but the responder services have not been enabled. Contact TIBCO Technical Support. PGTS0201E Continuing with initialization An error was encountered (see previous messages) during the Platform Server initialization but it has Copyright TIBCO Software Inc All Rights Reserved. 19

20 Messages List Message Manual for z/os been bypassed and the Platform Server will continue trying to startup. PGTS0202E QLOOK Insert SLOT#=xxxxxxxx: Slot not initialized to nulls - not inserted A request was added to the Platform Server active queue, but an internal error occurred adding the record to the queue. If this problem persists, stopping and restarting the Platform Server will automatically re-create the QLOOK queue. PGTS0203E QLOOK Insert SLOT#=xxxxxxxx: CS Failed for LOOK Chain: Retrying A request was added to the Platform Server active queue, but an internal error occurred while attempting to insert the request into the chain. The Platform Server will retry this up to times. This message can be ignored unless it is accompanied by message PGTS0204E. PGTS0204E QLOOK Insert SLOT#=xxxxxxxx: CS Failed Times: Request not added to Lookaside A request was added to the Platform Server active queue, but an internal error occurred while attempting to insert the request into the chain. The Platform Server has tried to add the request times, but was unsuccessful. Restarting the Platform Server started task will recreate the QLOOK queue, but the request that received the error will be lost. PGTS0205I Platform Server xxxxxxxxxx processing has been stopped The Platform Server has received either an INITIATORSTOP or RESPONDERSTOP command (xxxxxxxxxx). This message indicates that processing has been stopped. PGTS0206I Platform Server xxxxxxxxxx processing has been started The Platform Server has received either an INITIATORSTART or RESPONDERSTART command (xxxxxxxxxx). This message indicates that processing has been started. PGTF0207I MQ Load Error on module xxxxxxxx: MQ SCSQLOAD/SCSQAUTH must be in STEPLIB - MQ processing disabled The Platform Server was attempting to load MQ module xxxxxxxx, but 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 will be disabled. This should be treated as a problem only if the user wants the Platform Server to process MQ data. Otherwise this message can be ignored. PGTF0210E Load Failed for Token program xxxxxxxx: Not scanning for transfers queued while Platform Server was down The Platform Server was attempting to load the z/os Token program xxxxxxxx, but the load for this module failed. This module is normally loaded from the LPA library. This module is loaded at startup time when the Platform Server is checking if any requests have been scheduled while the Platform Server was inactive. Because Token processing cannot be performed, any transfers that were scheduled while the Platform Server was down will not be performed. PGTF0211E Token tttttttt request failed RC=rr: Not scanning for transfers queued while Platform Server was down The Platform Server was attempting to process z/os Token request xxxxxxxx, but this request failed with return code rr. Because Token processing cannot be performed, any transfers that were scheduled while the Platform Server was down will not be performed. 20 Copyright TIBCO Software Inc All Rights Reserved.

21 Message Manual for z/os Messages List PGTF0212I tttttttttt Transfer set to Inactive state due to COS cccccccc priority=yy The Platform Server was scanning its WORKQ to find transfers to run, and found transfer tttttttttt ready to run. However, while checking its COS entry cccccccc, the Platform Server dispatcher found that the priority for this transfer was with 0 or 1. In this case, the Platform Server will not start the transfer, and will put it in an inactive error state so that the transfer will not be 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 A transfer his 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 allow transfers to be initiated to this node. This message is displayed approximately every minute as a reminder that the node is on hold. PGTF0214I INITHOLD complete for Node nnnnnnnn: Initiator requests will be stopped: uuuuuuuu An INITHOLD request has been received for node nnnnnnnn. uuuuuuuu defines whether this request was initiated through an operator command, or through the ISPF panels. No transfers will initiated to this node. You can issue the INITREL operator command or use the ISPF panels to release the hold and allow transfers to be initiated to this node. PGTF0215I INITREL complete for Node nnnnnnnn: Initiator requests will start and the error count has been reset: uuuuuuuu An INITREL has been received for node nnnnnnnn. uuuuuuuu defines whether this request was initiated through an operator command, or through the ISPF panels. The Initiator node hold is cleared and transfers can now be initiated to this node. PGTF0216 RESPHOLD complete for Node nnnnnnnn: Responder requests will be rejected: nnnnnnnn A RESPHOLD request has been received for node nnnnnnnn. uuuuuuuu defines whether this request was initiated through an operator command, or through the ISPF panels. No transfers will accepted from this node; transfer 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 allow transfers to be accepted from this node. PGTF0217I RESPREL complete for Node nnnnnnnn: Responder requests will be accepted: uuuuuuuu A RESPREL has been received for node nnnnnnnn. uuuuuuuu defines whether this request was initiated through an operator command, or through the ISPF panels. The Responder node hold is cleared and transfers can now be accepted from this node. PGTS0234I Message data set closed This is a normal message that appears during shut down of the started task. PGTS0235I Audit data set closed This is a normal message that appears during shut down of the started task. Copyright TIBCO Software Inc All Rights Reserved. 21

22 Messages List Message Manual for z/os PGTS0250E Error creating PROFILE dataspace: User Profile processing disabled The Platform Server PROFILE dataspace could not be created by the Platform Server started task. The Platform Server will continue running, but the User Profile capabilities will be disabled. Get a copy of the Platform Server JOBLOG and contact TIBCO technical support. PGTS0251E PROFILE DD statement missing - User Profile processing disabled The Platform Server PROFILE DD statement was not defined in the Platform Server JCL. The Platform Server will continue running, but the User Profile capabilities will be disabled. Refer to the Platform Server installation procedures for more information on creating the PROFILE dataset. PGTS0252I User Profile for local user: uuuuuuuu node: nnnnnnnn changed to remote user: rrrrrrrr User uuuuuuuu queued a transfer and specified that User profiles should be used. The Platform Server started task substituted userid rrrrrrrr for the request to node nnnnnnnn. This messsage is displayed for information reqsons only. PGTS0253E User Profile dataspace alet invalid - transfer terminated The Platform Server started task was attempting to process a User Profile request, but the dataspace was not defined. The request will be terminated with an error. Typically, messages will be displayed prior to this which gives a reason that the dataspace was not created. PGTS0254E User Profile scan failed for user uuuuuuuu- remote sys nnnnnnnn - transfer terminated User uuuuuuuu attempted to use the User Profile in a request to node nnnnnnnn, but there was no entry on the User Profile file for that USER/NODE pair. The request will be terminated with an error. Use the FUSPROF utility to see entries that have been defined in the PROFILE file. PGTS0255E Invalid User Profile request type - transfer terminated The FUSPROF utility detected an invalid request type. The only valid entries for the TYPE parameter are: ADD, DELETE or LIST. Fix the parameter, and resubmit the job. PGTS0256E User Profile field xxxxxxxx not entered or contains invalid data The FUSPROF utility detected an invalid field xxxxxxxx. Refer to the Platform Server manual for more information on this utulity. Fix the parameter, and resubmit the job. PGTS0257E User Profile request failed - PROFILE alet nulls The FUSPROF utility was attempting to process a request, but the request failed because the PROFILE dataspace was not created properly. Messages displayed prior to this should give the reason that the dataspace was not created. The problem must be fixed, ad the started task brought down and up before the FUSPROF utility can run successfully. PGTS0258I Local user uuuuuuuu tttttttt PROFILE for node: nnnnnnnn remote user: rrrrrrrr successful The FUSPROF utility successfully processed request type tttttttt for user uuuuuuu to remote node nnnnnnnn. Remote user rrrrrrrr will be substituted when the user performs a request to this node. 22 Copyright TIBCO Software Inc All Rights Reserved.