TIBCO® Managed File Transfer Platform Server
for z/OS
Message Manual
Software Release 8.0
February 2018
Two-Second Advantage®
2
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH
EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR
PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE
EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY
OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO 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 (AND WHICH IS DUPLICATED IN THE LICENSE FILE)
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.
ANY SOFTWARE ITEM IDENTIFIED AS THIRD PARTY LIBRARY IS AVAILABLE UNDER
SEPARATE SOFTWARE LICENSE TERMS AND IS NOT PART OF A TIBCO PRODUCT. AS SUCH,
THESE SOFTWARE ITEMS ARE NOT COVERED BY THE TERMS OF YOUR AGREEMENT WITH
TIBCO, INCLUDING ANY TERMS CONCERNING SUPPORT, MAINTENANCE, WARRANTIES,
AND INDEMNITIES. DOWNLOAD AND USE THESE ITEMS IS SOLELY AT YOUR OWN
DISCRETION AND SUBJECT TO THE LICENSE TERMS APPLICABLE TO THEM. BY PROCEEDING
TO DOWNLOAD, INSTALL OR USE ANY OF THESE ITEMS, YOU ACKNOWLEDGE THE
FOREGOING DISTINCTIONS BETWEEN THESE ITEMS AND TIBCO PRODUCTS.
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 TIBCO Software Inc.
TIBCO, the TIBCO logo, Two-Second Advantage, TIBCO Managed File Transfer Suite, TIBCO Managed
File Transfer Command Center, TIBCO Managed File Transfer Internet Server, TIBCO Managed File
Transfer Platform Server are either registered trademarks or trademarks of TIBCO Software Inc. or its
subsidiaries in the United States and/or other countries.
Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise
Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of
Oracle Corporation 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. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE
VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.
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. TIBCO
SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)
AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
3
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 © 2003-2018 TIBCO Software Inc. All rights reserved.
TIBCO Software Inc. Confidential Information
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
4
Contents
TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Message Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Information Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
5
TIBCO Documentation and Support Services
How to Access TIBCO Documentation
Documentation for TIBCO products is available on the TIBCO Product Documentation website, mainly
in HTML and PDF formats.
The TIBCO Product Documentation website is updated frequently and is more current than any other
documentation included with the product. To access the latest documentation, visit https://
docs.tibco.com.
Documentation for TIBCO® Managed File Transfer Platform Server for z/OS is available on the https://
docs.tibco.com/products/tibco-managed-file-transfer-platform-server-for-z-os page.
Product-Specific Documentation
Documentation for TIBCO products is not bundled with the software. Instead, it is available on the
TIBCO Documentation site at https://docs.tibco.com/products/tibco-managed-file-transfer-platformserver-for-z-os.
The following documents for this product can be found on the TIBCO Documentation site:
●
TIBCO Managed File Transfer Platform Server for z/OS Installation and Operation Guide
●
TIBCO Managed File Transfer Platform Server for z/OS User's Guide
●
TIBCO Managed File Transfer Platform Server for z/OS Message Manual
●
TIBCO Managed File Transfer Platform Server for z/OS Release Notes
How to Contact TIBCO Support
You can contact TIBCO Support in the following ways:
●
For an overview of TIBCO Support, visit http://www.tibco.com/services/support.
●
For accessing the Support Knowledge Base and getting personalized content about products you are
interested in, visit the TIBCO Support portal at https://support.tibco.com.
●
For creating a Support case, you must have a valid maintenance or support contract with TIBCO.
You also need a user name and password to log in to https://support.tibco.com. If you do not have a
user name, you can request one by clicking Register on the website.
How to Join TIBCO Community
TIBCO Community is the official channel for TIBCO customers, partners, and employee subject matter
experts to share and access their collective experience. TIBCO Community offers access to Q&A forums,
product wikis, and best practices. It also offers access to extensions, adapters, solution accelerators, and
tools that extend and enable customers to gain full value from TIBCO products. In addition, users can
submit and vote on feature requests from within the TIBCO Ideas Portal. For a free registration, go to
https://community.tibco.com.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
6
Message Overview
Messages reported when installing, configuring, managing, and operating TIBCO Managed File
Transfer (MFT) Platform Server for z/OS are classified into four types according to event severity.
The severity is an indication of the level of concern for an event. The message type is abbreviated to the
last character in the message identifier. The message type identifiers are: E for error, W for warning, I for
information, and D for debug.
Message Type
Description
Error (E)
An error message typically indicates a failure or critical condition in the execution
of an application or system that requires further action.
For example, PGTS0056E:
Warning (W)
SYNTAX ERROR IN PARM FIELD: xxxx.
A warning message indicates a condition that is not as severe as an error, but
might cause problems in the future. It can also be a condition that requires
additional monitoring or maintenance.
For example, PGTB4195W:
SCRIPT will not be throttled: Use NODE
parameter to throttle execution.
Information (I)
An information message is recorded for audit purposes, usually a user action or a
change of states that are normal operations or conditions.
For example, PGTS0048I:
Debug (D)
TCPTRAC DD statement opened successfully.
A debug message is a diagnostic message displayed in the debug mode.
For example, PGTS8763D:
REPLY -T- to Terminate not waiting for
subtasks to end - otherwise shutdown will wait for them to end.
The debug messages are included in the Information Messages section.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
7
Error Messages
This section is a complete listing of all the error messages.
●
PGTS0013E Server: ssssssss not APF authorized - started task terminating
Explanation:
The started task ssssssss detected that it was not running APF authorized. This error is typically
caused by a STEPLIB library not being in the z/OS APF list. The started task is terminated.
Make sure that all the libraries in the STEPLIB are authorized and restart the Platform Server.
●
PGTS0023E *****LOG DATASET FULL - MESSAGE NOT LOGGED*****
Explanation:
The log data set is full and cannot record any more messages.
●
PGTS0041E Incoming request from partner xxxx denied - yyyy count of zzzz exceeded
Explanation:
The transfer request from the partner was denied. Either the MAXINITS, MAXRESP or MAXTOTAL count
was exceeded. These values are set in the GLOBAL member and can be adjusted to control concurrent
transfer activity.
●
PGTS0056E OSSERVER: SYNTAX ERROR IN PARM FIELD: xxxx
Explanation:
During the startup of the Platform Server task, an error was detected in the PARM field specified on
the EXEC statement.
Correct the error and restart the Platform Server.
●
PGTS0057E OSSERVER: INVALID PARAMETER IN PARM: xxxx
Explanation:
An invalid parameter was detected.
Correct the PARM field on the EXEC statement and restart the Platform Server.
●
PGTS0058E OSSERVER: TOO MANY PARM PARAMETERS
Explanation:
Too many parameters were passed to the Platform Server.
Correct the PARM field on the EXEC statement and restart the Platform Server.
●
PGTS0059E OSSERVER: INVALID DATA IN PARAMETER: xxxx
Explanation:
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
Explanation:
An error was detected parsing the parameters.
See previous message for a detailed description of that error.
●
PGTS0061E Error loading U7SVC - Global CA7 interface turned off
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
8
A CA7 load failure occurred. The error could occur only if CA7=YES was specified in the GLOBAL
parameters and the CA7 module U7SVC was not found.
●
PGTS0065E NODE REFRESH for nnnnnnnn invalid: Only TYPE=NODE allowed
Explanation:
The REFRESH command was issued, but member nnnnnnnn was not a NODE definition. Only NODE
definitions can be refreshed.
Check member nnnnnnnn to make sure that it is a NODE definition.
●
PGTS0066E Error in REFRESH command syntax
Explanation:
The REFRESH command was issued, but the syntax was incorrect. The correct syntax is F
stcname,REF,nodename.
●
PGTS0074E ERROR DELETING CIB ENTRY
Explanation:
The Platform Server attempted to process an operator MODIFY console command and received an
error trying to free the CIB.
If the Platform Server does not respond to the operator commands, contact TIBCO Technical
Support. Otherwise, this message can be treated as an informational message.
●
PGTS0078E ERROR SETTING CIB
Explanation:
The Platform Server attempted to process an operator MODIFY console command and received an
error trying to free the CIB.
If the Platform Server does not respond to the 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
Explanation:
The Platform Server started task could 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.
●
PGTS0080E AUTHKEY DD missing: Required when Global AUTHENTICATE is defined as ALL
- STC terminating
Explanation:
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 is
terminated.
Make sure the AUTHKEY data set is defined and also the AUTHKEY DD statement is defined in the
Platform Server startup JCL.
●
PGTS0081E Error opening AUTHKEY DD for xxxxx
Explanation:
The Platform Server attempted to open the AUTHKEY DD statement for INPUT or OUTPUT but
received an error. The Platform Server attempts to recover from the error and continue.
●
PGTS0082E Abend xxx opening AUTHKEY DD for xxxxxxxx
Explanation:
The Platform Server attempted to open the AUTHKEY DD statement for INPUT or OUTPUT but
received an abend. The Platform Server attempts to recover from the error and continue.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
9
●
PGTS0083E Abend nnn on AUTHKEY xxxxxxxx request
Explanation:
The Platform Server received an abend on a GET, PUT, or CLOSE request to the AUTHKEY file. The
Platform Server attempts to recover from the error and continue.
●
PGTS0084E SYNAD exit entered on AUTHKEY xxxxxxxx request
Explanation:
While processing the AUTHKEY DD statement, the SYNAD exit was invoked because of an error in
the file. The Platform Server attempts to recover from the error and continue.
●
PGTS0087E Unable to create Authorization KEY: Global AUTHNTICATE is defined as
ALL - STC terminating
Explanation:
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 error is typically
caused by a problem with the AUTHKEY DD statement. The Platform Server started task is
terminated. Typically messages displayed before this message document 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
Explanation:
The AUTHKEY DD statement was not defined. The GLOBAL AUTHENTICATE parameter was not
defined as ALL for either the initiator or responder. The Platform Server continues to run without
AUTHKEY support. If authentication is requested for an initiator or responder task, the request
fails.
●
PGTS0089E Refresh failed for node nnnnnnnn: Member not enabled
Explanation:
The REFRESH command was issued, but member nnnnnnnn was not enabled. The REFRESH
command requires that the node to be refreshed must be enabled.
Use the ENA command to enable the node. For a list of enabled nodes, use the nodes operator
command.
●
PGTS0105E Global SSLIPPORT defined but $SSLDB profile not found: SSL Processing
disabled
Explanation:
The GLOBAL SSLIPPORT parameter was defined with a non-zero value. This means that the
Platform Server must start its SSL subtask. However, the Platform Server scanned its user profile
database and could not find the $SSLDB, which was defined. SSL processing is disabled.
Run the Platform Server user profile utility to add the $SSLDB user profile, and then stop and start
the Platform Server started task. The $SSLDB user must be defined before the Platform Server can
start SSL processing. When using a RACF key ring, the remote password must be defined with the
value NULL. When using a key database, the remote password must be defined with the key of the
key database.
●
PGTS0111E Platform Server SNA and TCP keys not defined: STCssssssss terminating
Explanation:
The Platform Server was started without a valid SNA or TCP key. The Platform Server cannot
continue running under this circumstance, and the Platform Server started task is shut down.
Contact TIBCO Technical Support to get valid license keys.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
10
●
PGTS0115E COS Detailed Inquiry failed: COS cccccccc not currently enabled
Explanation:
The Platform Server COS operator command was entered to display COS entry cccccccc. But this
entry is not enabled, so the COS command fails.
Check the spelling of entry cccccccc and fix if necessary. Use the Platform Server ENA command to
enable the COS entries.
●
PGTT0120E Node member nnnnnnnn not enabled: LU_NAME/IP_ADDR/IP_NAME parameters
not defined
Explanation:
The CONFIG DD in the startup JCL pointed to member nnnnnnnn in the node configuration library.
But member nnnnnnnnis not a valid node.
Edit the nnnnnnnn member and correct the parameters. Enable the node after the parameters are
corrected.
For more information on node parameters, see "Node Definition Parameters" section of TIBCO
Managed File Transfer Platform Server for z/OS Installation and Operations Guide.
●
PGTS0120E TCP Initialization failed: Repl E(nd) C(ontinue), R(etry)
Explanation:
During the started task TCP initialization, an error occurred. The message that was displayed
allowed one of the following options to be selected:
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 a response to this message, the started task attempts to perform TCP initialization
every 30 seconds. If initialization is successful, this message is deleted and the started task
initialization continues normally.
●
PGTS0121E INITAPI Failed: Started Task xxxxxxx Terminating
Explanation:
During the started task TCP initialization, an error was detected. Error message PGTS0120E was
displayed. The message option E was selected. This message indicates that the started task is
terminated.
●
PGTS0124E TLS Initialize Failed: ZLIB/TLS Service is not started
Explanation:
Platform Server attempted to initialize the TLS environment, but the initialization failed because the
ZLIB/TLS environment was not started. See the Platform Server log files for more information to
determine why the initialization failed.
●
PGTS0128E ZLIB/TLS Environment Initialization Failed: Review Logs for more
details
Explanation:
The ZLIB/TLS environment initialization failed. Additional messages should be displayed with a
more detailed explanation of why the initialization failed.
●
PGTS0130E ZLIB/TLS Shutdown Failed: Review Logs for more details
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
11
Platform Server attempted to stop the ZLIB/TLS environment, but the shutdown failed. Additional
messages should be displayed with more detailed explanation of why the initialization failed.
●
PGTS0156E Dispatcher DIV Save Error - See VSAM diagnostic message - Dispatcher
Terminating Abnormally
Explanation:
The DIV Save macro returned a bad return code. If the Platform Server was shut down, it indicates
that the in-storage work queue contents might be corrupted.
Do not queue new activities until this error is resolved. Let critical file transfers finish before
shutting down the Platform Server , and then contact TIBCO Technical Support.
●
PGTS0157E Post Error Routine Driven in Dispatcher
Explanation:
Contact TIBCO Technical Support if you receive this error message and have the Platform Server log
available.
●
PGTS0159E Error in PURGE command syntax xxxx
Explanation:
The console modify command was entered to purge an item from the work queue, but the operand
contained an invalid syntax. The correct syntax is F servername,PURGE,activity_number.
●
PGTS0160E Error in DELETE command syntax xxxx
Explanation:
The console modify command was entered to delete an item from the work queue, but the operand
contained an invalid syntax. The correct syntax is F servername,DELETE,activity_number.
●
PGTS0161E Error in HOLD command syntax xxxx
Explanation:
The console modify command was entered to place an activity to hold status, but the operand
contained an invalid syntax. The correct syntax is F servername,HOLD,activity_number.
●
PGTS0162E Error in RELEASE command syntax xxxx
Explanation:
The console modify command was entered to release an activity, but the operand contained an
invalid syntax. The correct syntax is F servername,RELEASE,activity_number.
●
PGTS0163E Error in SUSPEND command syntax xxxx
Explanation:
The console modify command was entered to suspend an activity, but the operand contained an
invalid syntax. The correct syntax is F servername,SUSPEND,activity_number.
●
PGTS0164E Invalid SSLDEBUG parameter xxxxxx: must be YES or NO
Explanation:
The SSLDEBUG operator command was entered with an invalid value. The valid values are YES or NO.
●
PGTS0165E SSLDEBUG changed to xxxxx
Explanation:
The SSLDEBUG operator command was entered correctly. The Platform Server has changed the
SSLDEBUG value to either YES or NO.
●
PGTS0166E PURGE command failed for Activity xxxx RC=yyyy
Explanation:
The console modify command to purge an activity from the work queue failed.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
12
●
PGTS0167E DELETE command failed for Activity xxxx RC=yyyy
Explanation:
The console modify command to delete an activity from the work queue failed.
●
PGTS0168E HOLD command failed for Activity xxxx
Explanation:
The console modify command to hold an activity from the work queue failed.
●
PGTS0169E RELEASE command failed for Activity xxxx
Explanation:
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]
Explanation:
The console modify command to suspend an activity from the work queue failed.
●
PGTS0171E Invalid ESSDEBUG parameter xxxxxxx: must be WTO/LOG/NO
Explanation:
The ESSDEBUG operator command was entered with an invalid value. The valid values are WTO, LOG,
or NO.
●
PGTS0179E Activity tttttttttt Queue ADD failed: Platform Server EVERY request not
Queued at this time
Explanation:
A Platform Server request that used the EVERY parameter was queued. The Platform Server was
unable to add the request to the queue because the queue was full. The transfer request was not
queued. It is retried at the next scheduled interval.
To update the maximum number of requests in the queue, use the WORKQ parm of the EXEC
PGM=OSSERVER statement.
●
PGTS0180E Activity xxxx not found
Explanation:
An operator command was entered for the particular activity designated in the message text, but the
activity was not found in the work queue. The activity number is incorrect, or the activity is already
completed.
●
PGTS0182E Activity xxxx already in PURGE status
Explanation:
An attempt was made to purge an activity from the work queue that is already been marked for
purge. No further action is necessary.
●
PGTS0183E Activity xxxx not INACTIVE
Explanation:
Contact TIBCO Technical Support if you receive this message.
●
PGTS0184E Activity xxxx not in HELD status
Explanation:
An attempt was made to release an activity from the work queue that was not in held status.
●
PGTS0186E Error in SECAUDIT command syntax xxxx
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
13
The SECAUDIT modify command was issued incorrectly. The correct format is F
server_name,SECAUDIT,YES or F server_name,SECAUDIT,NO.
●
PGTS0188E Error in SECADMIN command syntax xxxx
Explanation:
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 to turn off the notification to the
security administrator.
●
PGTS0190E Error in SECLOGV command syntax xxxx
Explanation:
The SECLOGV modify command was issued incorrectly. The correct format is F
option must be one of these valid values: YES, NO, LOG, or WTO.
server_name,SECLOGV,option.
●
PGTS0194E Activity tttttttttt Invalid EVERY type xxxxxxxx: Request put on hold
Explanation:
An internal error occurred while 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
Explanation:
An EVERY=DDXX request was entered. The value represented by xxxxx was greater than 31. The value
is invalid and must 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
Explanation:
A Platform Server LIST request that used the EVERY parameter was queued. Because the list was not
found, the Platform Server was unable to add the request to the queue. The EVERY request is put on
hold and not queued.
Check to see that the proper LIST entry is used and that the LIST is enabled at startup through the
CONFIG or through the Platform Server ENA command.
●
PGTS0197E xxxxxxxx Request failed: GLOBAL REQUIRE_NODE_DEFINITION requires NODE
to be defined
Explanation:
A request was made to add a transfer to the Platform Server request queue. Request type xxxxxxxx
could be either responder or initiator.
The GLOBAL parameter REQUIRE_NODE_DEFINITION defines whether a node definition is required
for initiator and responder transfers. 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.
Make sure the node is defined and enabled for the Platform Server.
●
PGTS0198E Activity tttttttttt Error xx on yyyyyyyy Date Conversion: EVERY request
put on hold
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
14
An error occurred for activity tttttttttt in the date conversion routine. The request is put on hold.
Contact TIBCO Technical Support.
●
PGTS0200E Responder services are not configured
Explanation:
An incoming transfer or other activity request had come in, but the responder services is not
enabled.
Contact TIBCO Technical Support.
●
PGTS0201E Continuing with initialization
Explanation:
An error was encountered (see previous messages) during the Platform Server initialization. But it
was bypassed and the Platform Server continues trying to startup.
●
PGTS0202E QLOOK Insert SLOT#=xxxxxxxx: Slot not initialized to nulls - not
inserted
Explanation:
A request was added to the Platform Server active queue, but an internal error occurred in adding
the record to the queue.
If this problem persists, stop and restart the Platform Server to automatically re-create the QLOOK
queue.
●
PGTS0203E QLOOK Insert SLOT#=xxxxxxxx: CS Failed for LOOK Chain: Retrying
Explanation:
A request was added to the Platform Server active queue, but an internal error occurred when
attempting to insert the request into the chain. The Platform Server attempts to retry this up to 10000
times. This message can be ignored unless it is accompanied by message PGTS0204E.
●
PGTS0204E QLOOK Insert SLOT#=xxxxxxxx: CS Failed 10000 Times: Request not added
to Lookaside
Explanation:
A request was added to the Platform Server active queue, but an internal error occurred when
attempting to insert the request into the chain. The Platform Server retried to add the request 10000
times but was unsuccessful.
Restart the Platform Server started task to re-create the QLOOK queue, but the request that received
the error is lost.
●
PGTF0210E Load Failed for Token program xxxxxxxx: Not scanning for transfers
queued while Platform Server was down
Explanation:
The Platform Server attempted to load the z/OS token program xxxxxxxx, but the load for this
module failed. This module is typically loaded from the LPA library. This module is loaded at
startup time when the Platform Server checks if any requests were scheduled when the Platform
Server was inactive. Because token processing could not be performed, any transfers that were
scheduled when the Platform Server was down are not performed.
●
PGTF0211E Token tttttttt request failed RC=rr: Not scanning for transfers queued
while Platform Server was down
Explanation:
The Platform Server attempted to process z/OS token request xxxxxxxx, but the request failed with
return code rr. Because token processing could not be performed, any transfers that were scheduled
while the Platform Server was down are not performed.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
15
●
PGTF0219E TLSSTOP failed: TLS Interface not started
Explanation:
The TLSSTOP command was issued to stop the TLS services. The request failed because the TLS
interface had not been started.
●
PGTF0220E TLSSTOP failed: TLS Already Stopped
Explanation:
The TLSSTOP command was issued to stop the TLS services. The request failed because TLS was
already stopped on this server.
●
PGTF0221E TLSSTART failed: TLS Never Started
Explanation:
The TLSSTART command was issued to start the TLS services. The request failed because TLS was
not started successfully on this server.
●
PGTF0222E TLSSTART failed: TLS interface is already Active
Explanation:
The TLSSTART command was issued to start the TLS services. The request failed because the TLS
interface was already started.
●
PGTF0224E MODVER: Module: mmmmmmmm - MODVER is not available
Explanation:
The MODVER operator command for module mmmmmmmm was issued. MODVER information was
not available for module mmmmmmmm.
●
PGTF0225E MODVER: Module: mmmmmmmm not found
Explanation:
The MODVER operator command for module mmmmmmmm was issued. MODVER information was
not available for module mmmmmmmm because the module was not found.
●
PGTF0226E MODVER: Module not entered. Correct format is: F MFTSTC,MODVER,modname
Explanation:
The MODVER operator command was issued, but the module name was not provided. The request
was rejected. The correct format of the MODVER parameter is: F MFTSTC,MODVER,modname.
●
PGTF0227E ZEDCSTOP failed: Cannot stop ZEDC interface while TLS Interface is
active
Explanation:
The operator attempted to execute the ZEDCSTOP command but the TLS Interface was active. TLS
must be stopped before you stop the ZEDC interface.
Use the TLSSTOP command to stop the TLS Interface.
●
PGTS0250E Error creating PROFILE dataspace: User Profile processing disabled
Explanation:
The Platform Server PROFILE dataspace could not be created by the Platform Server started task.
The Platform Server continues running, but the user profile capabilities are disabled.
Get a copy of the Platform Server JOBLOG and contact TIBCO Technical Support.
●
PGTS0251E PROFILE DD statement missing - User Profile processing disabled
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
16
The Platform Server PROFILE DD statement was not defined in the Platform Server JCL. The
Platform Server continues running, but the user profile capabilities are disabled.
®
See the Platform Server installation procedures in the TIBCO Managed File Transfer Platform Server
for z/OS Installation and Operation Guide for more information on creating the PROFILE data set.
●
PGTS0253E User Profile dataspace alet invalid - transfer terminated
Explanation:
The Platform Server started task attempted to process a user profile request, but the dataspace was
not defined. The request was terminated with an error. Typically, messages that explain why the
dataspace was not created are displayed before this message.
●
PGTS0254E User Profile scan failed for user uuuuuuuu- remote sys nnnnnnnn transfer terminated
Explanation:
User uuuuuuuu attempted to use the user profile in a request to node nnnnnnnn, but there was no
entry for the USER/NODE pair in the user profile file. The request was terminated with an error.
Use the FUSPROF utility to see entries that were defined in the profile file.
●
PGTS0255E Invalid User Profile request type - transfer terminated
Explanation:
The FUSPROF utility detected an invalid request type. The valid values for the TYPE parameter are
ADD, DELETE or LIST.
Correct the parameter values and resubmit the job.
●
PGTS0256E User Profile field xxxxxxxx not entered or contains invalid data
Explanation:
The FUSPROF utility detected an invalid field xxxxxxxx.
Correct the parameter values, and resubmit the job.
See TIBCO Managed File Transfer Platform Server for z/OS Installation and Operations Guide for more
information on this utility.
●
PGTS0257E User Profile request failed - PROFILE alet nulls
Explanation:
The FUSPROF utility attempted to process a request. The request failed because the PROFILE
dataspace was not created properly. Typically, messages displayed before this message give the
reason the dataspace was not created.
After the error is resolved, restart the started task for the FUSPROF utility to run successfully.
●
PGTS0261E Local user uuuuuuuu DELETE PROFILE for node: nnnnnnnn failed - user/
node not found on PROFILE DSP
Explanation:
The FUSPROF utility attempted to delete an entry for user/node combination uuuuuuuu/nnnnnnn, but
this combination was not found on the PROFILE dataspace.
●
PGTS0264E Remote user rrrrrrrr DELETE PROFILE for node: nnnnnnnn failed - user/
node not found on PROFILE DSP
Explanation:
The user attempted to delete profile for remote user rrrrrrrr and node nnnnnnnn. The deletion failed
because the remote user/node entry was not found on the PROFILE dataspace.
Check the REMOTE_USER and NODE parameters to make sure that they are correct. If necessary, use
to show the user profiles that are enabled for the REMOTE_USER and NODE. Also make
TYPE=LIST
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
17
sure that the RESPONDER parameter matches the RESPONDER parameter that is used to add the record
onto the PROFILE dataspace.
●
PGTS0265E Already Verified User uuuuuuuu for NODE nnnnnnnn denied by xxxxxxxx
definition
Explanation:
A request was detected in which the already verified indicator was turned on. The request was
received on node nnnnnnnn. The request was denied by either the NODE or GLOBAL
ACCEPT_VERIFIED_USER parameter.
If you want to allow already verified users from this node, make sure that an enabled NODE
parameter is defined with ACCEPT_VERIFIED_USER=YES.
●
PGTS0267E Local user uuuuuuuu tttttttt PROFILE for node: nnnnnnnn failed Profile not found
Explanation:
The FUSPROF utility was executed to replace a user profile. TYPE=REPLACE was defined which means
that the request fails unless an entry already exists. An entry was not found, therefore the request
failed with an error and the profile was not replaced.
●
PGTS0268E Local user uuuuuuuu tttttttt PROFILE for node: nnnnnnnn failed Profile already exists
Explanation:
The FUSPROF utility was executed to create a user profile. TYPE=CREATE was defined which means
that the request fails if an entry already exists. An entry was found, therefore the request failed with
an error and the profile was not created.
●
PGTS555E Server Work Queue Dataspace Out of Room RC=19
Explanation:
The WORKQ dataset needs to be expanded.
®
See the section in the TIBCO Managed File Transfer Platform Server for z/OS Installation and Operation
Guide titled “Defining the Work Queue VSAM Data Set” for information on the VSAM allocation
parameters and the WORKQ startup parameter. See the section titled “EXEC PARM Fields used by
MFT” for more information on the WORKQ startup parameter.
●
PGTS0789E LOAD FAILED FOR MODULE xxxx
Explanation:
This message is displayed when the started task is brought up. If you receive this message, contact
TIBCO Technical Support.
●
PGTS0800E Attempt to Process Activity xxxx as Duplicate key on Audit file
Explanation:
If you receive this message, contact TIBCO Technical Support.
●
PGTS0801E Audit Error on Activity: xxxx Process: yyyy User: zzzz Node: nnnn
Explanation:
An error occurred when the server attempted to write to the audit file.
●
PGTS0803E SMF write failed for Record Type xxxx Return Code=yyyy Activity=zzzz
Explanation:
If the Platform Server encountered an error when writing the SMF record for the transaction
indicated in the message.
●
PGTS0804E Logging error detected - taking SNAP dump - logging will be terminated
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
18
Explanation:
An internal error occurred.
Save the dump and contact TIBCO Technical Support for assistance.
●
PGTS0805E GENCB for AUDIT ACB Failed R15=xxxx R0=yyyy
Explanation:
An internal error occurred when the Platform Server was creating ACB for the audit data set.
●
PGTS0806E GENCB for AUDIT RPL Failed R15=xxxx R0=yyyy
Explanation:
An internal error occurred when the Platform Server was creating the RPL for the audit data set.
●
PGTS0807E GENCB for AUDPATH1 ACB Failed R15=xxxx R0=yyyy
Explanation:
An internal error occurred when the Platform Server was creating ACB for the AUDPATH data set.
●
PGTS0808E OPEN for AUDIT ACB Failed R15=xxxx ERFLG=yyyy
Explanation:
OPEN failed for audit data set.
●
PGTS0809E OPEN for AUDPATH1 ACB Failed R15=xxxx ERFLG=yyyy
Explanation:
OPEN failed for AUDPATH data set.
●
PGTS0810E CLOSE for AUDIT ACB Failed R15=xxxx ERFLG=yyyy
Explanation:
CLOSE failed for audit data set.
●
PGTS0811E CLOSE for AUDPATH1 ACB FaileddR15=xxxx ERFLG=yyyy
Explanation:
CLOSE failed for AUDPATH1 data set.
●
PGTS0812E GENCB for AUDPATH2 ACB Failed R15=xxxx R0=yyyy
Explanation:
An internal error occurred when the Platform Server is creating ACB for the AUDPATH2 data set.
●
PGTS0813E OPEN for AUDPATH2 ACB Failed R15=xxxx ERFLG=yyyy
Explanation:
OPEN failed for the AUDPATH2 data set.
●
PGTS0814E GENCB for AUDPATH2 RPL Failed R15=xxxx R0=yyyy
Explanation:
An internal error occurred when the Platform Server was creating RPL for the AUDPATH2 data set.
●
PGTS0815E GET for last record failed R15=xxxx RTNCD=yyyy - AUDIT processing
starting on record 1
Explanation:
The started task was unable to determine the last record of the audit data set and was positioned to
the beginning of the data set. The started task overwrites the old audit data set.
●
PGTS0816I AUDIT processing starting at record xxxx
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
19
This is an informational message. The audit processing continues from the last record found.
●
PGTS0817E CLOSE for AUDPATH2 ACB Failed R15=xxxx ERFLG=yyyy
Explanation:
CLOSE failed for AUDPATH2 data set.
●
PGTS0822E Error opening SNAPLOG DD stmt - LOGSNAP terminated
Explanation:
A snap dump could not be taken because the SNAPLOG DD statement in the started task procedure
was either missing or incorrect.
●
PGTS0824E GET failed for AUDIT record xxxx - R15=yyyy, ERRCD=zzzz bypassing PUT
Explanation:
GET failed for the audit data set.
●
PGTS0827E GENCB for AUDIT RPL xxxx Failed R15=yyyy R0=zzzz
Explanation:
An internal error occurred when the Platform Server was creating RPL for the audit data set.
●
PGTS0828E GENCB for FUSAUDIT RPL Failed R15=xxxx R0=yyyy
Explanation:
An internal error occurs when the Platform Server was creating RPL for the FUSAUDIT data set.
●
PGTS0829E GET for FUSAUDIT File Failed R15=xxxx R0=yyyy
Explanation:
GET failed for FUSAUDIT data set.
●
PGTS0830E Point for FUSAUDIT File Failed R15=xxxx R0=yyyy
Explanation:
Point failed for FUSAUDIT data set.
●
PGTS0831E AUDPATH2 ACB OPEN failed - AUDIT Processing started on Record 1
Explanation:
The started task was unable to determine the last record of the audit data set and was positioned to
the beginning of the data set. The started task overwrites the old audit data set.
●
PGTS0835E Audit File full - Unable to Write Audit record for TRN=tttttttttt
Explanation:
The Platform Server attempted to write an audit record for transaction tttttttttt, but it received an
error indicating that the audit file was full. This record is not logged to the audit file.
The Platform Server administrator must make sure that the audit file is large enough to hold the
number of audit records defined by the GLOBAL MAX_AUDIT_RECORDS parameter.
●
PGTS0985E Console Display Command Processor Unsuccessful
Explanation:
An error occurred while processing the DISP command.
●
PGTS0991E Console Node Query Processor Unsuccessful
Explanation:
An error occurred and a modify query issued on the node was not completed successfully.
●
PGTS0992E Node xxxx is not enabled in current topology
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
20
Explanation:
An error occurred and the modify disable command issued on the remote node was not successfully
completed. This message is also displayed when the node command is entered and the node is not
enabled.
●
PGTS0993E Remote System Name Missing - Reenter Command
Explanation:
An error occurred when a modify query was issued on a remote node and no remote node name
was specified.
●
PGTS0994E Remote Node Name is too Long - Reenter Command
Explanation:
An error occurred when a modify query was issued on a remote node and the remote node name
specified was larger than 8 characters. The remote node name cannot be more than the maximum
length of a MVS member name in a PDS (8 characters).
●
PGT1001E INVALID REQUEST TYPE PASSED TO FUSTLV
Explanation:
Platform Server was validating incoming control information and found an unexpected request.
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.
●
PGTS1001E Error opening DD statement GLOBAL - using default global values
Explanation:
An error occurred while opening the DD statement for the global parameters. In this case, the
default global values are used.
●
PGTS1002E xxxx GLOBAL parameter invalid
Explanation:
The Global parameter specified is invalid.
Check your global definitions and correct the error.
●
PGT1003E TLV VARIABLE XXXX DATA INVALID - NOT Y/N
Explanation:
Platform Server was validating incoming control information and found an unexpected data. 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.
●
PGTS1003E ALLAUTH parameter invalid - must be YES or NO - defaulting to YES
Explanation:
Check your global definitions and correct the error.
●
PGT1004E TLV VARIABLE XXXX - INVALID LENGTH
Explanation:
Platform Server was validating incoming control information and found an unexpected data length.
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.
●
PGTS1004E COSTBYTE parameter invalid - must be numeric value 8 bytes or less
Explanation:
Check your global definitions and correct the error.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
21
●
PGT1005E TLV VARIABLE XXXX KEY CODE NOT MATCHED
Explanation:
Platform Server was validating incoming control information and found an unexpected request.
This could be caused by a partner Platform Server running a different release.
If this error affects the execution of a Platform Server transfer, contact TIBCO Technical Support.
●
PGTS1005E COSTCPU parameter invalid - must be numeric value 8 bytes or less
Explanation:
Check your global definitions and correct the error.
●
PGTS1006E EXPIRE parameter invalid - must be numeric value 3 bytes or less
Explanation:
Check your global definitions and correct the error.
●
PGTS1007E MAXINITS parameter invalid - must be numeric value 5 bytes or less
Explanation:
Check your global definitions and correct the error.
●
PGTS1008E MAXRESP parameter invalid - must be numeric value 5 bytes or less
Explanation:
Check your global definitions and correct the error.
●
PGTS1009E NEWCYCLE parameter invalid - must be numeric value 4 bytes or less
Explanation:
Check your global definitions and correct the error.
●
PGTS1010E SECURE parameter invalid - must be SAF or NO - defaulting to NO
Explanation:
Check your global definitions and correct the error.
●
PGTS1011E SESSION parameter invalid - must be V1 or V2 - defaulting to V2
Explanation:
Check your global definitions and correct the error.
●
PGTS1012E SMF parameter invalid - must be NO, or numeric value between 192 and
255
Explanation:
Check your global definitions and correct the error.
●
PGTS1013E SPACE parameter invalid - valid values are CYL/TRK/BLK/SMS
Explanation:
Check your global definitions and correct the error.
●
PGTS1014E PRIMARY-SPACE parameter invalid - must be numeric value 5 bytes or less
Explanation:
Check your global definitions and correct the error.
●
PGTS1015E SECONDARY-SPACE parameter invalid - must be numeric value 5 bytes or
less
Explanation:
Check your global definitions and correct the error.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
22
●
PGTS1016E ERRDESC parameter invalid - refer to installation manual for correct
format
Explanation:
Check your global definitions and correct the error.
●
PGTS1017E ERRROUTE parameter invalid - refer to in installation manual for
correct format
Explanation:
Check your global definitions and correct the error.
●
PGTS1018E INFODESC parameter invalid - refer to in installation manual for
correct format
Explanation:
Check your global definitions and correct the error.
●
PGTS1019E INFOROUTE parameter invalid - refer to installation manual for correct
format
Explanation:
Check your global definitions and correct the error.
●
PGTS1020E Maximum length exceeded for parameter xxxx
Explanation:
The parameter specified is invalid. Check your global definitions and correct the error.
●
PGTS1021E LOCAL_T_SELECTOR must be an even number of digits - 32 digits or less
Explanation:
Check your global definitions and correct the error.
●
PGTS1022E LOCAL_S_SELECTOR must be an even number of digits - 32 digits or less
Explanation:
Check your global definitions and correct the error.
●
PGTA1023E Error on Dynamic Allocation for Activity xxxx
Explanation:
A bad return code was received after calling SVC99.
See the OSIMSG log or SYSLOG for the exact error message.
●
PGTS1023E LOCAL_P_SELECTOR must be an even number of digits - 32 digits or less
Explanation:
The LOCAL_P_SELECTOR parameter specified is invalid.
Check your global definitions and correct the error.
●
PGTS1024E LOCAL_NSAP must be an even number of digits 40 digits or less
Explanation:
Check your global definitions and correct the error.
●
PGTS1026E DEFAULT_GATELU parameter must be in following format DEFAULT_GATELU=(INIT,RESP,G3,G4,G5,G6)
Explanation:
Check your global definitions and correct the error.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
23
●
PGTS1028E DEFAULT_WINDOW_SIZE must be a numeric value between 1 and 7
Explanation:
Check your global definitions and correct the error.
●
PGTS1029E DEFAULT_PACKET_SIZE must be a numeric value of:
128/256/512/1024/2048/4096
Explanation:
Check your global definitions and correct the error.
●
PGTS1030E LOCAL_ETHERMAC address must be 12 digits long - error
Explanation:
Check your global definitions and correct the error.
●
PGTS1031E RECEIVE_TPDU_BEFORE_ACK must be a numeric value between 1 and 15 error
Explanation:
Check your global definitions and correct the error.
●
PGTS1032E RETRANSMISSION_TRIES must be a numeric value between 1 and 255 - error
Explanation:
Check your global definitions and correct the error.
●
PGTS1033E ACKNOWLEDGE_WAIT_TIME must be a numeric value between 1 and 600 - error
Explanation:
Check your global definitions and correct the error.
●
PGTS1034E GLOBAL_3172_CHANNEL must be 3 hex digit - error
Explanation:
Check your global definitions and correct the error.
●
PGTS1035E 3172_RESPONDER must be YES or NO - error
Explanation:
Check your global definitions and correct the error.
●
PGTS1036E LOCAL_ETHER_ADAPTER must be 0 or 1 - error
Explanation:
Check your global definitions and correct the error.
●
PGTS1037E SAP_INTERVAL must be a numeric value between 1 and 99
Explanation:
Check your global definitions and correct the error.
●
PGTS1038E Error in APPC Applid parameter
Explanation:
Check your global definitions and correct the error.
●
PGTS1042E FTAMKEY must be 16 Hex characters
Explanation:
Check your global definitions and correct the error.
●
PGTS1044E FUSIONKEY must be 24/56 Hex characters
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
24
Explanation:
Check your global definitions and correct the error.
●
PGTS1045E xxxx key invalid - check cover letter - application disabled
Explanation:
The key is invalid. The application does not start.
Check your global definitions and correct the error.
●
PGTS1046E xxxx key invalid - wrong product code specified - application disabled
Explanation:
The key is invalid. The application does not start.
Check your global definitions and correct the error.
●
PGTS1048E MAXTOTAL parameter invalid - must be numeric value 5 bytes or less
Explanation:
Check your global definitions and correct the error.
●
PGTS1049E xxxx failed authorization key validation - date expired - application
not started
Explanation:
Key validation failed. The application does not start.
Check your global definitions and correct the error.
●
PGTS1050E xxxx passed authorization key validation
Explanation:
This message is displayed at startup when the correct authorization key is applied.
●
PGTS1052E Global configuration dataset is empty - no parameters found
Explanation:
Check your global definitions and correct the error.
●
PGTS1057E IO_BUFNO must be a value between 1 and 255
Explanation:
Check your global definitions and correct the error.
●
PGTS1058E CA7 must be YES or NO
Explanation:
Check your global definitions and correct the error.
●
PGTS1059E TCPIPJOBNAME must be from 1 to 8 characters
Explanation:
Check your global definitions and correct the error.
●
PGTS1060E TCPIPPORT must be 2500 or a value from 5000 to 65535
Explanation:
Check your global definitions and correct the error.
●
PGTS1069E RESETINTERVAL must be a numeric value from 1 to 60
Explanation:
Check your global definitions and correct the error.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
25
●
PGTS1070E FUSIONTCPKEY must be 24/56 Hex characters
Explanation:
Check your global definitions and correct the error.
●
PGTS1071E FUSIONSNAKEY must be 24/56 Hex characters
Explanation:
Check your global definitions and correct the error.
●
PGTS1074E MAX_AUDIT_RECORDS must be numeric and greater than 99 - using default
of 25000
Explanation:
Check your global definitions and correct the error.
●
PGTS1075E TRAP_IPADDR PARAMETER IS INVALID
Explanation:
Check your global definitions and correct the error.
●
PGTS1088E Invalid GLOBAL parameter on record NNN: Record follows
Explanation:
The parameter on the indicated record is not valid. Message PGTS1089E displays the record.
●
PGTS1089E GLOBAL DATA: xxxxxxxxxxxxxxxxxxxxxx
Explanation:
This is the invalid record in the global definitions.
Check your global definitions and correct the error.
●
PGTS1095E ROSCOE_JOBNAME MUST BE FROM 1 TO 8 CHARACTERS IN LENGTH
Explanation:
Check your global definitions and correct the error.
●
PGTS1098E application_name KEY INVALID - CPU ID: AAAA DOES NOT MATCH CPU IN KEY:
BBBB
Explanation:
This application must be authorized by applying the correct licensing key for the product in the
member.
GLOBAL
●
PGTS1099E application_name KEY INVALID - CPU TYPE: AAAA DOES NOT MATCH CPU IN
KEY: BBBB
Explanation:
This application key is not authorized.
Apply the correct licensing key for the product in the GLOBAL member.
●
PGTA1100E Requested Driver not Supported for Node xxxx
Explanation:
A queued activity requires a driver that is either not installed or not configured.
Inform your distributor to order additional drivers.
●
PGTS1101E Error opening DD statement CONFIG - unable to read node configuration
file
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
26
Check the CONFIG DD statement in your startup JCL. Correct the error and restart the task.
●
PGTS1102E CONFIG DD statement not defined with RECFM=FB and LRECL=80 - error
Explanation:
Check the CONFIG DD statement in your startup JCL. Correct the error and restart the task.
●
PGTS1103E CONFIG file error - member name exceeds 8 bytes - reading next record
Explanation:
Check your CONFIG member in the CONFIG DD statement library. One of the member names
specified in CONFIG member defines a member to be activated. That member name is more than the
maximum of 8 characters. The current record is bypassed and processing continues to the next
record.
●
PGTS1104E Error reading CONFIG member xxxx - proceeding to the next member
Explanation:
An error occurred when reading member xxxx in the CONFIG library. This member is bypassed and
the next member is read. Other displayed messages gives more information about the cause of the
error.
●
PGTS1105E xxxx data invalid on CONFIG File Member yyyy - bypassing this member
Explanation:
Member yyyy of the CONFIG DD library is defined with an invalid parameter xxxx. Member yyyy
is not enabled.
Fix member yyyy and enable the node through the ENABLE operator command.
●
PGTS1115E PARALLEL parameter must YES or NO
Explanation:
When attempting to enable a node definition, the started task finds that the PARALLEL parameter
was defined incorrectly. The valid values are YES or NO.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1119E Invalid value for APPLICATION parameter xxxx
Explanation:
When attempting to enable a node definition, the APPLICATION parameter was defined incorrectly.
The valid values are APPC, KNFUSION or FUSION.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1120E xxxx APPLICATION not available - contact Technical Support
Explanation:
If you receive this message, contact TIBCO Technical Support for assistance.
●
PGTS1131E xxxx member not activated due to errors
Explanation:
Member xxxx was not activated because of parameter errors. Previously displayed messages show
the exact cause of the error.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1133E Member CONFIG not found in CONFIG library - no remote systems enabled
at startup
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
27
The started task attempted to read the CONFIG member of the CONFIG library, but could not find the
member. No node definitions is enabled.
CONFIG
●
PGTS1134E Maximum length exceeded for parameter xxxx
Explanation:
Parameter xxxx exceeded the maximum length. The node definition is not activated.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1147E xxxx member already enabled
Explanation:
The modify command could not be used to enable this member because the member was already
active.
●
PGTS1149E xxxx member not found on disable
Explanation:
The node specified in the modify command, which was used to disable the member, was not found
in the nodes library.
●
PGTS1150E CONTENTION WINNERS must be between 0 and 256
Explanation:
When attempting to enable a node definition, that the CONTENTION_WINNERS parameter was defined
incorrectly. The valid values are 0 to 256.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1151E CONTENTION LOSERS must be between 0 and 256
Explanation:
When attempting to enable a node definition, the CONTENTION_LOSERS parameter was defined
incorrectly. The valid values are 0 to 256. Correct the error and enable the node through the ENABLE
operator command.
●
PGTS1152E IF PARALLEL SESSIONS=NO, CONTENTION WINNERS MUST = 1
Explanation:
Within a node definition, PARALLEL=NO was specified and the CONTENTION_WINNERS parameters was
set to value other than 1. When PARALLEL=NO is specified, the CONTENTION_WINNERS parameter must
be set to 1.
●
PGTS1153E IF PARALLEL SESSIONS=NO, CONTENTION LOSERS MUST = 0
Explanation:
Within a node definition, PARALLEL=NO is specified and the CONTENTION_LOSERS parameters is set to
value other than 1. When PARALLEL=NO is specified, the CONTENTION_LOSERS parameter must be set
to 1.
●
PGTS1154E Invalid MODENAME parameter
Explanation:
An attempt was made to enable a node definition, but the MODENAME parameter was defined
incorrectly. The valid values must be from 1 to 8 characters.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1155E Invalid LU NAME parameter
Explanation:
An attempt was made to enable a node definition, but the LUNAME parameter was defined
incorrectly. The valid values must be from 1 to 8 characters.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
28
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1156E DISCONNECT must be YES or NO
Explanation:
An attempt was made to enable a node definition, but the DISCONNECT parameter was defined
incorrectly. The valid values are YES or NO.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1157E WAIT_FOR_SESSION must be YES or NO
Explanation:
An attempt was made to enable a node definition, but the WAIT_FOR_SESSIONS parameter was
defined incorrectly. The valid values are YES or NO.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1158E TYPE must be YES or NO
Explanation:
An attempt was made to enable a node definition, but the TYPE parameter was defined incorrectly.
The valid values are NODE, LIST or NTDOMAIN.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1159E NODE must be 8 characters or less
Explanation:
When an attempt was made to enable a node definition, the NODE parameter was defined incorrectly.
The valid values are from 1 to 8 characters.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1160E MAX NODES FOR LIST ENTRY IS 1024
Explanation:
An attempt was made to enable a TYPE=LIST definition, but the number of nodes specified on the
list definition exceeded the maximum value of 1024.
If you require more than 1024 members on a list definition, split the list into two or more list
definitions and queue requests to both list definitions.
●
PGTS1162E Invalid NTDOMAIN parameter
Explanation:
An attempt was made to enable a node definition, but the NTDOMAIN parameter was defined
incorrectly. The valid values are from 1 to 8 characters.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1163E Invalid NTRESOURCE parameter
Explanation:
An attempt was made to enable a NTDOMAIN definition, but the NTDOMAIN parameter was defined
incorrectly. The valid values are from 1 to 15 characters.
Correct the error and enable the NTDOMAIN through the ENABLE operator command.
●
PGTS1164E Invalid NTNODE parameter
Explanation:
An attempt was made to enable a NTDOMAIN definition, but the NTDNODE parameter was defined
incorrectly. The valid values are from 1 to 8 characters. Correct the error and enable the
NTDOMAIN through the ENABLE operator command.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
29
●
PGTS1165E NTDOMAIN xxxx ACTIVATED SUCCESSFULLY
Explanation:
This is an information message that is displayed when a node definition is enabled successfully.
●
PGTS1166E Invalid IPPORT parameter
Explanation:
An attempt was made to enable a node definition, but the IPPORT parameter was defined
incorrectly. The valid values are 1025 to 65535.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1167E Invalid IPADDR parameter
Explanation:
An attempt was made to enable a node definition, but the IPADDR parameter was defined
incorrectly. The valid value is a dotted decimal IP addresses in the format: xxx.xxx.xxx.xxx.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1168E Invalid IPNAME parameter
Explanation:
An attempt was made to enable a node definition, but the IPNAME parameter was defined
incorrectly. The valid value is a name from 1 to 24 characters.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1169E Invalid TPNUSERID parameter
Explanation:
An attempt was made to enable a node definition, but the TPNUSERID parameter was defined
incorrectly. The valid value is a user ID from 1 to 10 characters.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1170E Invalid TPNPASSWORD parameter
Explanation:
An attempt was made to enable a node definition, but the TPNPASSWORD parameter was defined
incorrectly. The valid value is a password from 1 to 10 characters.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1171E Invalid TPNLIBRARY parameter
Explanation:
An attempt was made to enable a node definition, but the TPNLIBRARY parameter was defined
incorrectly. The valid value is a library from 1 to 10 characters.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1173E NTDOMAIN parameter is required when TYPE=NTDOMAIN
Explanation:
A member defined as TYPE=NTDOMAIN was enabled. However, parameter NTDOMAIN was not
specified. NTDOMAIN is required when TYPE=NTDOMAIN is specified.
Correct the error and enable the NTDOMAIN through the ENABLE operator command.
●
PGTS1174E NTRESOURCE parameter is required when TYPE=NTDOMAIN
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
30
A member defined as TYPE=NTDOMAIN was enabled. However, parameter NTRESOURCE was not
specified. NTRESOURCE is required when TYPE=NTDOMAIN is specified.
Correct the error and enable the NTDOMAIN through the ENABLE operator command.
●
PGTS1175E NTNODE parameter is required when TYPE =NTDOMAIN
Explanation:
A memberdefined as TYPE=NTDOMAIN was enabled. However, parameter NTNODE was not specified.
NTNODE is required when TYPE=NTDOMAIN is specified.
Correct the error and enable the NTDOMAIN through the ENABLE operator command.
●
PGTS1176E Invalid TPNSECURITY value - must be SECURE, TRUSTED or NONE
Explanation:
An attempt was made to enable a node definition, but the TPNSECURITY parameter was defined
incorrectly. The valid values are SECURE, TRUSTED or NONE.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1177E TPNSECURITY must be set to SECURE when TPNUSERID is specified
Explanation:
An attempt was made to enable a node definition, but the TPNUSERID parameter was defined, and
the TPNSECURITY parameter was not defined as SECURE. When the TPNUSERID parameter is defined,
TPNSECURITY must be defined as SECURE.
Correct the error and enable the node through the ENABLE operator command.
●
PGTS1178E VAX PARAMETER MUST BE YES OR NO
Explanation:
The VAX parameter in the node definition must be set as YES or NO. The accompanying message
displayed the node that contained the parameter error.
PGTS1131E
Check your node definitions and correct the error, then enable the node using the ENABLE modify
command.
●
PGTS1182E ENCRYPT MUST BE NONE/DES/3DES/BLOWFISH: PASSONLY PARAMETER IS OPTIONAL
Explanation:
The node ENCRYPT parameter was specified with an invalid value. The valid values are: NONE, DES,
3DES, BLOWFISH and BLOWFISH_LONG. The node entry is not enabled.
Correct the parameter and enable the node.
●
PGTS1183E AUTHENTICATION_KEY must be 16 hex digits
Explanation:
The node AUTHENTICATION_KEY parameter was entered incorrectly. It must be entered as 16 hex
digits. The node entry is not enabled.
Correct the parameter and enable the node.
●
PGTS1184E TLS(SSL) PARAMETER MUST BE YES, NO, OR TUNNEL
Explanation:
The Node TLS (or SSL) parameter was specified with invalid data. Valid values are:
The node entry is not enabled.
TUNNEL.
YES, NO,
or
Correct the parameter and enable the node.
●
PGTS1186E INVALID BACKUPLUNAME PARAMETER
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
31
The node BACKUPLUNAME parameter was entered incorrectly. This parameter must be from 1 to 8
alphanumeric characters. The node is not enabled.
Correct the parameter and enable the node.
●
PGTS1187E INVALID BACKUPIPADDR PARAMETER
Explanation:
The node BACKUPIPADDR parameter was entered incorrectly. This parameter must be a valid IP
address in dotted decimal format of XXX.XXX.XXX.XXX. The node is not enabled.
Correct the parameter and enable the node.
●
PGTS1188E INVALID BACKUPIPNAME PARAMETER
Explanation:
The node BACKUPIPNAME parameter was entered incorrectly. This parameter must be from 1 to 24
alphanumeric characters. The node is not enabled.
Correct the parameter and enable the node.
●
PGTS1189E INVALID BACKUPIPPORT PARAMETER
Explanation:
The node BACKUPIPPORT parameter was entered incorrectly. This parameter must be a number
between 2500 and 65535. The node is not enabled.
Correct the parameter and enable the node.
●
PGTS1190E MAXIMUM OF 5 BACKUP HOSTS EXCEEDED
Explanation:
More than 5 BACKUPIPADDR/BACKPIPNAME/BACKUPLUNAME parameters were specified. The
maximum number is 5. The node is not enabled.
Correct the parameter and enable the node.
●
PGTS1191E INVALID BACKUPMODENAME PARAMETER
Explanation:
The node BACKUPMODENAME parameter was entered incorrectly. This parameter must be from 1 to 8
alphanumeric characters. The node is not enabled.
Correct the parameter and enable the node.
●
PGTS1193E INVALID BACKUPNODE PARAMETER
Explanation:
The node BACKUPNODE parameter was entered incorrectly. This parameter must be a valid node
name from 1 to 8 characters. The node is not enabled.
Correct the parameter and enable the node using the ENABLE operator command.
●
PGTS1194E HASHKEY must be 16 HEX bytes or NO
Explanation:
The node HASHKEY parameter was entered incorrectly. This parameter must be 16 hex digits (from
0-9, A-F). The node is not enabled.
Correct the parameter and enable the node using the ENABLE operator command.
●
PGTA1196E Error xxxx Obtaining Checkpoint Canceling Activity yyyy
Explanation:
An error occurred when obtaining the checkpoint for a transfer using checkpoint restart. Because no
checkpoint was found, the transfer was canceled.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
32
●
PGTA1197E xxxx is a RESTART of yyyy, xxxx will be purged.
Explanation:
When using checkpoint restart, the started task tried to restart the same activity. In this case, the
duplicate activity is purged.
●
PGTS1197E RESPONDER_PROFILE must be YES or NO
Explanation:
The node RESPONDER_PROFILE parameter was entered incorrectly. The valid values are YES or NO.
The node is not enabled.
Correct the parameter and enable the node using the ENABLE operator command.
●
PGTA1198E Restart NOT supported by xxxx, yyyy continuing from beginning of file
Explanation:
Checkpoint restart was not supported by xxxx. If the transfer failed before completion, the transfer
starts from the beginning of the file.
●
PGTS1198E ACCEPT_VERIFIED_USER must be YES or NO
Explanation:
The node ACCEPT_VERIFIED_USER parameter was defined incorrectly. The valid values are YES or
The node is not enabled.
NO.
Correct the parameter and enable the node using the ENABLE operator command.
●
PGTA1199E CheckPoint NOT supported by xxxx, yyyy continuing transfer
Explanation:
Checkpoint restart was not supported by xxxx. If the transfer fails before completion, the transfer
starts from the beginning of the file.
●
PGTS1199E SAPI_CLASS must be 1 to 8 Characters
Explanation:
The value entered for the NODE SAPI_CLASS parameter was invalid. The valid values are 1 to 8
characters. The node is not enabled.
Correct the parameter and enable the node using the ENABLE operator command.
●
PGTA1211E sssssssss: nnnnnnnnn
Explanation:
Platform Server statistics were written to the log file when the CFSTATS operator command was
issued and when the Platform Server was shut down.
●
PGTA1212E Error validating GLOBAL xxx_USERID uuuuuuuu: xxx Interface Disabled:
Error message follows
Explanation:
Either the GLOBAL DNI_USERID or SAPI_USERID parameter was entered, but the user could not log
with the user ID uuuuuuuu. XXX defined either DNI or SAPI. Message PGTA1213E gives a detailed
reason for the login failure.
●
PGTA1213E ttttttttttttttttttttttttttttttttttttttttttttt
Explanation:
A user attempted to log in for either the DNI or SAPI tasks, but the login failed. This message gives
detailed information about the login failure.
●
PGTA1219E tttttttttt Call to U7SVC abended with code=nnn
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
33
Explanation:
The U7SVC program was called at the end of a transfer, but the call abends with code nnn. The
Platform Server recovered from the error, and the transfer was not affected.
●
PGTA1220E tttttttttt Call to U7SVC terminated with code=nn
Explanation:
The U7SVC program was called at the end of a transfer, but the call was terminated with non-zero
return code nn, which typically indicates that the request failed. The file transfer was not affected.
●
PGTS1234E [ OSIWMSGS | OSILOGDS ] DATASPACE CREATE FAILED
Explanation:
An attempt was made to create either the OSIWMSGS or OSILOGDS dataspace. But an error
occurred. Contact TIBCO Technical Support for assistance.
●
PGTS1235E LOAD OF MESSAGES MODULE FAILED
Explanation:
An attempt was made to load module OSIMSGS but failed. The failure could be caused by an
incorrect STEPLIB or because not enough region was allocated to this job.
●
PGTN1305E Invalid Session Specified:xxxx for Call Clear to be issued for Activity
yyyy
Explanation:
Contact TIBCO Technical Support if you receive this message.
●
PGTS1306E xxxxxxxxxx MUST BE 24 HEX CHARACTERS
Explanation:
The global key parameter xxxxxxxxxxwas specified, but it did not contain 24 hex characters. Key
xxxxxxxxxx requires 24 hex characters. The product is not installed because the key is invalid.
●
PGTS1307E xxxxxxxxxxxxxxx must be from 1 to 16 characters in length
Explanation:
The global xxxxxxxxxxx parameter was defined with an invalid value. Either the parameter was not
entered or it had more than 16 characters. Valid values must contain between 1 and 16 characters.
Correct the parameter and restart the Platform Server.
●
PGTS1308E TCPIP_INTERFACE must be IUCV or HPNS
Explanation:
The GLOBAL TCPIP_INTERFACE parameter was defined with an invalid value. Valid values are
IUCV or HPNS.
Correct the parameter and restart the Platform Server.
●
PGTS1309E ENCRYPT must be NONE/DES/3DES/BLOWFISH: PASSONLY parameter is optional
Explanation:
The GLOBAL ENCRYPT parameter was defined with an invalid value. Valid values are: NONE, DES,
and BLOWFISH_LONG.
3DES, BLOWFISH
Correct the parameter and restart the Platform Server.
●
PGTS1310E DNIKEY MUST BE 24 HEX CHARACTERS
Explanation:
The GLOBAL DNIKEY parameter was defined with an invalid value. DNI is not started. The valid
value must be a key of 24 hex characters.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
34
Correct the parameter and restart the Platform Server.
●
PGTS1311E DNI_INTERVAL must be a number between 1 and 1440
Explanation:
The GLOBAL DNI_INTERVAL parameter was specified incorrectly. The valid value must be a number
between 1 and 1440.
Correct the parameter and restart the Platform Server.
●
PGTS1312E SMTP_JOBNAME must be less than 8 characters
Explanation:
The GLOBAL SMTP_JOBNAME parameter was entered incorrectly. Valid values contain 1 to 8
characters.
Correct the parameter and restart the Platform Server.
●
PGTS1313E SMTP_LOCALCLASS must be a single alphabetic character
Explanation:
The GLOBAL SMTP_LOCALCLASS parameter was entered incorrectly. The valid value is a single
alphabetic character.
Correct the parameter and restart the Platform Server.
●
PGTS1314E SMTP_SENDER_HOSTNAME must be 40 characters or less
Explanation:
The GLOBAL SMTP_SENDER_HOSTNAME parameter was entered incorrectly. Valid values contain 1 to
40 characters.
Correct the parameter and restart the Platform Server.
●
PGTS1315E AUTHENTICATE must be in format: AUTHENTICATE=(xxx,yyy)
Explanation:
The GLOBAL AUTHENTICATE parameter was entered incorrectly. Valid values for xxx and yyy are:
NO, YES, or ALL.
Correct the parameter and restart the Platform Server.
●
PGTS1316E SSLIPPORT must be a value from 1025 to 65535
Explanation:
The GLOBAL SSLIPORT parameter was defined incorrectly. The valid value must be a number
between 1025 and 65535. The default value 0 is used and IPv4 is not be enabled for incoming SSL
requests.
●
PGTS1317E SSL_REQUEST must be a YES/NO/OUTSIDE_NETWORK
Explanation:
The GLOBAL SSL_REQUEST parameter was defined incorrectly. Valid values are: YES, NO, and
OUTSIDE_NETWORK. The default value NO is used.
Correct the parameter error and restart the started task.
●
PGTS1318E SSL_NETWORK_XXXXXX must be a valid IP Address or Subnet
Explanation:
The GLOBAL SSL_NETWORK_IPADDR or SSL_NETWORK_SUBNET parameter is defined incorrectly. The
valid value must be a valid dotted decimal IP address. Correct the parameter and restart the started
task.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
35
●
PGTS1319E SSL_NETWORK_SUBNET required when SSL_REQUEST=OUTSIDE_NETWORK: Defaults
to 255.255.255.0
Explanation:
The GLOBAL SSL_REQEUST parameter is defined as OUTSIDE_NETWORK, but the
SSL_NETWORK_SUBNET parameter was not defined. SSL_NETWORK_SUBNET must be defined when
OUTSIDE_NETWORK is defined.
Correct the parameter and restart the started task.
●
PGTS1324E HASHKEY MUST BE 16 HEX CHARACTERS
Explanation:
The GLOBAL HASHKEY parameter was defined incorrectly. Valid values must be 16 hex digits ( 0-9,
A-F). The default value is used for this parameter.
Correct the parameter, and restart the started task or use the GLOBALREFRESH operator command.
●
PGTS1332E SSL_MESSAGE_QUEUE_NUMBER must be between 1 and 1 and 999999999
Explanation:
The GLOBAL SSL_MESSAGE_QUEUE_NUMBER parameter was defined incorrectly. Valid values must be
between 1 and 999,999,999. The default value 46464 is used.
●
PGTS1333E SSL_KEY_DBNAME/SSL_KEY_DBSTASH/SSL_KEY_DNLABEL required when SSLIPPORT
defined
Explanation:
Platform Server was configured to use SSL by using the SSLIPPORT parameter. When SSLIPPORT is
defined, the following global parameters are also required:
SSL_KEY_DBNAME
SSL_KEY_DBSTASH
SSL_KEY_DBLABEL
Make sure that these parameters are defined in the GLOBAL member.
●
PGTS1334E SSLENCRYPT must be DES/3DES/BF/BFL/RIJNDAEL:Defaulting to BF(Blowfish)
Explanation:
The GLOBAL SSLENCRYPT parameter was defined incorrectly. Valid values are: DES, 3DES, BF, BFL,
or RIJNDAEL. The default value BF (Blowfish) is used.
●
PGTS1337E START/CONFIG must be from 1 to 8 characters
Explanation:
The GLOBAL CONFIG parameter was defined incorrectly. Valid values must contain 1 to 8 characters
and point to a member of the CONFIG DD statement. The default value CONFIG is used.
●
PGTS1338E xxxADAPTER_IPADDR must be a valid IP Address
Explanation:
The TCPADAPTER_IPADDR parameter or the SSLADAPTER_IPADDR parameter was defined incorrectly.
The valid value must be a valid dotted decimal IP address.
●
PGTS1339E REQUIRE_NODE_DEFINITION must be defined as (YES|NO,YES|NO)
Explanation:
The GLOBAL REQUIRE_NODE_DEFINITION parameter was defined incorrectly. This parameter
contains two subparameters for initiator and responder respectively. The valid values for both the
initiator and responder are YES or NO.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
36
Correct the global definition and restart the Platform Server for the changes to take place.
●
PGTS1340E HSM_MIGRATE_VOLUME MUST be a 6 character VOLUME name
Explanation:
The GLOBAL HSM_MIGRATE_VOLUME parameter was defined incorrectly. The valid value must be a 6character volume name. The volume name must match the volume name used by HSM. The default
HSM volume name of MIGRAT is used.
Correct the global definition and restart the Platform Server for the changes to take place.
●
PGTS1341E EXIT_MIGRATE_VOLUME MUST be a 6 character VOLUME name
Explanation:
The GLOBAL EXIT_MIGRATE_VOLUME parameter was defined incorrectly. The valid value must be a
6-character volume name. The volume name must match the volume name used by the storage
manager used by the installation. This parameter has no default value.
Correct the global definition and restart the Platform Server for the changes to take place.
●
PGTS1342E FILE_ERROR_TRY_COUNT must be a number from 1 to 9999
Explanation:
The GLOBAL FILE_ERROR_TRY_COUNT parameter was defined incorrectly. The valid value must be
between 1 and 9999. The default value 5 is used.
Correct the global definition and restart the Platform Server for the changes to take place.
●
PGTS1343E DEFAULT_TRY_COUNT must be a number from 1 to 9999
Explanation:
The GLOBALDEFAULT_TRY_COUNT parameter was defined incorrectly. The valid values must be
between 1 and 9999. The default value 7 is used.
Correct the global definition and restart the Platform Server for the changes to take place.
●
PGTS1344E FILE_ERROR_TRY_INTERVAL must be a number from 10 to 9999
Explanation:
The GLOBAL FILE_ERROR_TRY_INTERVAL parameter was defined incorrectly. The valid values must
be between 10 and 9999 seconds. The default value 60 seconds is used.
Correct the global definition and restart the Platform Server for the changes to take place.
●
PGTS1345E EXIT_MIGRATE_WAIT_TIME must be a number from 20 to 9999
Explanation:
The GLOBAL EXIT_MIGRATE_WAIT_TIME parameter was defined incorrectly. The valid values must
be between 20 and 9999 seconds. The default value 300 seconds is used.
Correct the global definition and restart the Platform Server for the changes to take place.
●
PGTS1346E JOB_SUBMIT_DSN must be a dataset name from 1 to 44 characters
Explanation:
The GLOBAL JOB_SUBMIT_DSN parameter was defined incorrectly. The valid value must be a data
set name from 1 to 44 characters. The data set name must contain the JCL members that you want to
submit using TRANS_TYPE=COMMAND and SUBMIT=membername batch interface parameters.
The member names cannot be included in this parameter. This parameter has no default value.
Correct the global definition and restart the Platform Server for the changes to take place.
●
PGTS1347E RESPONDER_PROFILE must be YES or NO
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
37
The GLOBAL RESPONDER_PROFILE parameter was defined incorrectly. The valid values are Yes or
NO. The default value NO is used.
Correct the global definition and restart the Platform Server for the changes to take place.
●
PGTS1348E ACCEPT_VERIFIED_USER must be YES or NO
Explanation:
The GLOBAL ACCEPT_VERIFIED_USER parameter was defined incorrectly. The valid values are Yes
or NO. The default value NO is used.
Correct the global definition and restart the Platform Server for the changes to take place.
●
PGTS1349E SAPI_INTERFACE must be YES or NO
Explanation:
The GLOBAL SAPI_INTERFACE parameter was defined incorrectly. The valid values are Yes or NO.
Correct the parameter and restart the started task.
●
PGTS1350E SAPI_SUBSYSTEM must be 1 to 4 characters
Explanation:
The GLOBAL SAPI_SUBSYSTEM parameter is defined incorrectly. The valid values are from 1 to 4
characters. Typically, you do not have to use this parameter unless the JES subsystem name is
different than the primary JES subsystem name.
Correct the parameter and restart the started task.
●
PGTS1351E SSL_CLIENT_DNLABEL must be 64 characters or less
Explanation:
The SSL_CLIENT_DNLABEL parameter was defined incorrectly.
Make sure that the data entered for this parameter is less than 64 characters.
●
PGTS1353E HOLD_TEMPORARY_FILE_ERRORS must be YES or NO
Explanation:
The GLOBAL HOLD_TEMPORARY_FILE_ERRORS parameter was entered incorrectly. The valid values
are YES or NO. The default value NO is used.
Correct this parameter, and restart the Platform Server.
●
PGTS1354E HOLD_TEMPORARY_NETWORK_ERRORS must be YES or NO: Second parm must be
RELEASE/NORELEASE
Explanation:
The GLOBALHOLD_NETWORK_FILE_ERRORS parameter was entered incorrectly. The valid values are
or NO. The default value NO is used. You can define a second parameter for this parameter. The
valid values for the second parameter are RELEASE or NORELEASE.
YES
Correct the parameter, and restart the Platform Server.
●
PGTS1355E TCPCONNECT_ADAPTER_IPADDR must be a valid IP address
Explanation:
The GLOBAL TCPCONNECT_ADAPTER_IPADDR parameter was entered incorrectly. You must enter
either a valid dotted decimal IP address, or the value ALL. If no value is specified, the default value
ALL is used. The IP address entered must match an interface address or virtual IP address (VIPA) in
the TCP system.
●
PGTS1356E PDS_WRITE_DISP must be OLD or SHR
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
38
An invalid value was entered for the GLOBAL PDS_WRITE_DISP parameter. Valid values are OLD or
SHR. The default value OLD is used.
If you want to specify SHR, correct the parameter and refresh the started task.
●
PGTS1357E HIPAA must be YES or NO
Explanation:
An invalid value was entered for the GLOBAL HIPAA parameter. Valid values are YES or NO. The
default value NO is used.
If you want to specify YES, you must correct the parameter and refresh the started task.
●
PGTS1358E AUDIT_TEMP_ERRORS must be YES/BOTH/AUDIT/SMF/NO
Explanation:
An invalid value was entered for the GLOBAL AUDIT_TEMP_ERRORS parameter. The valid values are
YES, BOTH, AUDIT, SMF and NO. The default value NO is used in this case.
If you want to specify any other value, correct the parameter and refresh the started task.
●
PGTS1359E CFWEB_SUPPORT must be ALTER/VIEW/NO
Explanation:
An invalid value was entered for the GLOBAL CFWEB_SUPPORT parameter. The valid values are VIEW
or NO. The default value VIEW is used in this case.
Correct the parameter and refresh the started task.
●
PGTS1360E CCC_ALTER_FACILITY must be 32 characters or less
Explanation:
The value entered for the GLOBAL CCC_ALTER_FACILITY parameter was greater than 32 characters.
The valid values are between 1 and 32 characters.
Correct this parameter, and refresh the started task.
●
PGTS1361E CCC_BROWSE_FACILITY must be 32 characters or less
Explanation:
The value entered for the GLOBAL CCC_BROWSE_FACILITY parameter was greater than 32
characters. The valid values are between 1 and 32 characters.
Correct this parameter, and refresh the started task.
●
PGTS1362E DNI_USERID must be 8 characers or less
Explanation:
An invalid value was entered for the GLOBAL DNI_USERID parameter. The valid value must be a
valid user ID no longer than 8 characters. This parameter has no default value, which means that the
DNI task runs under the authorization of the Platform Server started task.
You must correct the parameter and refresh the started task.
●
PGTS1363E SAPI_USERID must be 8 characers or less
Explanation:
An invalid value was entered for the GLOBAL SAPI_USERID parameter. The valid value must be a
valid user ID no longer than 8 characters. This parameter has no default value, which means that the
SAPI task runs under the authorization of the Platform Server started task.
You must correct the parameter and refresh the started task.
●
PGTS1364E MQ_GOOD must be 64 characters or less and must start with $MQ:
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
39
An invalid value was entered for the GLOBAL MQ_GOOD parameter. The valid value must be a valid
MQ message queue, 64 characters or less, and must start with the value $MQ. This parameter has no
default value, which means that the GLOBAL MQ notifications are disabled for successful transfers.
You must correct the parameter and refresh the started task.
●
PGTS1365E MQ_FAIL must be 64 characters or less and must start with $MQ:
Explanation:
An invalid value was entered for the GLOBAL MQ_FAIL parameter. The valid value must be a valid
MQ message queue, 64 characters or less, and must start with the value $MQ. This parameter has no
default value, which means that the GLOBAL MQ notifications are disabled for unsuccessful
transfers.
Correct the parameter and refresh the started task.
●
PGTS1366E EMAIL_GOOD must be 64 characters or less
Explanation:
An invalid value was entered for the GLOBAL EMAIL_GOOD parameter. The valid value must be a
valid email address, 64 characters or less. This parameter has no default value, which means that the
GLOBAL email notifications are disabled for successful transfers.
Correct the parameter and refresh the started task.
●
PGTS1367E EMAIL_FAIL must be 64 characters or less
Explanation:
An invalid value was entered for the GLOBAL EMAIL_FAIL parameter. The valid value must be a
valid email address, 64 characters or less. This parameter has no default value, which means that the
GLOBAL email notifications are disabled for unsuccessful transfers.
Correct the parameter and refresh the started task.
●
PGTS1368E MQ_NOTIFY must be INITIATOR/RESPONDER/BOTH/NONE
Explanation:
An invalid value was entered for the GLOBAL MQ_NOTIFY parameter. The valid values are
INITIATOR, RESPONDER, BOTH and NONE. The default value NONE are used in this case, which means
that GLOBAL MQ notifications are disabled.
If you want to specify any other value, correct the parameter and refresh the started task.
●
PGTS1369E EMAIL_NOTIFY must be INITIATOR/RESPONDER/BOTH/NONE
Explanation:
An invalid value was entered for the GLOBAL EMAIL_NOTIFY parameter. The valid values are
INITIATOR, RESPONDER, BOTH and NONE. The default value NONE is used in this case, which means
that GLOBAL email notifications are disabled.
If you want to specify any other value, correct the parameter and refresh the started task.
●
PGTS1370E APPC_GENERIC_NAME must be 1 to 8 characters
Explanation:
An invalid value was entered for the GLOBAL APPC_GENERIC_NAME parameter. The valid value
must be between 1 and 8 characters. In this case, VTAM generic processing is disabled.
If you want to enable VTAM generic processing, correct the parameter and refresh the started task.
●
PGTS1371E xxxxxxxxx Invalid CRC check on License Key validation
Explanation:
The license key entered in the GLOBAL configuration member was invalid.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
40
Check if the key entered in the GLOBAL configuration member matches the key provided by
TIBCO Technical Support. If the key does match, contact TIBCO Technical Support.
●
PGTS1372E xxxxxxxxx Invalid Expiration Date on License Key validation
Explanation:
The expiration date entered for the license key in the GLOBAL configuration member was invalid.
Contact TIBCO Technical Support.
●
PGTS1373E xxxxxxxxx Invalid Platform on License Key validation
Explanation:
The platform entered for the license key in the GLOBAL configuration member was invalid. The key
can only run on the platform for which it is generated.
Contact TIBCO Technical Support.
●
PGTS1374E xxxxxxxxx Invalid Product on License Key validation
Explanation:
The product entered for the license key in the GLOBAL configuration member was invalid.
Contact TIBCO Technical Support.
●
PGTS1375E TCP_TIMEOUT must be a number between 0 and 1440
Explanation:
The value entered for the GLOBAL TCP_TIMEOUT parameter was incorrect. The valid values are
between 0 and 1440. if you specify 0, no TCP timeout processing are performed.
Correct this parameter and restart the Platform Server started task.
●
PGTS1382E xxxxxxxxxxxxx must be YES or NO
Explanation:
The value entered for the GLOBAL INITIATORSTOP or RESPONDERSTOP parameter (xxxxxxxxxx) was
incorrect. The valid values are YES or NO. In this case, the default value NO is used. Correct this
parameter and restart the Platform Server started task.
●
PGTS1383E AUTOENABLE must be YES or NO
Explanation:
The value entered for GLOBAL AUTOENABLE parameter was invalid. The valid values are YES or NO.
Correct this parameter and restart the Platform Server started task.
●
PGTS1384E SSL_VERSION must be OS390 or z/OS
Explanation:
The value entered for GLOBAL SSL_VERSION parameter was invalid. The valid values are OS390
and z/OS. If this parameter is not defined, or is defined incorrectly, the Platform Server
automatically determines the correct version of the SSL program to execute.
If you want to override the value that the Platform Server detects, correct the SSL_VERSION
parameter and restart the Platform Server started task.
●
PGTS1385E CCC_ADMIN_FACILITY must be 32 characters or less
Explanation:
The value entered for the GLOBAL CCC_ADMIN_FACILITY parameter was invalid. The valid values
must be between 1 and 32 characters.
Correct this parameter and restart the Platform Server started task.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
41
●
PGTS1386E CCC_TRANSFER_FACILITY must be 32 characters or less
Explanation:
The value entered for the GLOBAL CCC_TRANSFER_FACILITY parameter was invalid. The valid
values must be between 1 and 32 characters.
Correct this parameter and restart the Platform Server started task.
●
PGTS1388E RSHOST must be 64 characters or less
Explanation:
The value entered for the GLOBAL RSHOST parameter was invalid. The valid values must be from 1
to 64 characters without any embedded spaces.
Correct this parameter and restart the Platform Server started task.
●
PGTS1389E RSPORT must be a number from 1024 to 65535
Explanation:
The GLOBAL RSPORT parameter was defined incorrectly. The valid values must be a number
between 1024 and 65535. In this case, the RSPORT parameter is ignored.
●
PGTS1390E ENFORCE_SECURITY_POLICY must be HIPAA, FIPS140, TLSFIPS or NONE
Explanation:
The GLOBAL ENFORCE_SECURITY_POLICY parameter was defined incorrectly. The valid values are
In this case, the ENFORCE_SECURITY_POLICY parameter is ignored.
HIPAA, FIPS140, TLSFIPSor NONE.
●
PGTS1391E FIPS140 not supported on this processor: FIPS140 requires crypto coprocessor with AES256 and SHA1 support
Explanation:
The GLOBAL ENFORCE_SECURITY_POLICY parameter was set to FIPS140. However based on the
hardware, FIPS 140 cannot be supported on this processor.
To run in FIPS 140 mode, intsall a hardware cryptographic processor that supports 256 bit AES
encryption and SHA-1 message digests.
●
PGTS1392E Started task terminating due to FIPS140 error
Explanation:
The GLOBAL ENFORCE_SECURITY_POLICY parameter was set to FIPS140. The Platform Server could
not run in FIPS140 mode because of hardware incompatibilities or license key issues. The Platform
Server started task is terminated.
Either resolve the problem with FIPS140 support, or set the GLOBAL ENFORCE_SECURITY_POLICY
parameter to HIPAA or NONE.
●
PGTS1393E GLOBAL ENFORCE_SECURITY_POLICY set to FIPS140: License Key does not
support FIPS140
Explanation:
The GLOBAL ENFORCE_SECURITY_POLICY parameter was set to FIPS140. However based on the
license key, FIPS140 is not supported.
Contact TIBCO Technical Support if you must get a license key that supports FIPS140.
●
PGTS1395E TRANSFER_INTERFACE_PROTOCOL must be ALL, NONE, TCP, SNA: Defaulting to
ALL
Explanation:
The GLOBAL TRANSFER_INTERFACE_PROTOCOL parameter was defined incorrectly. The valid values
are ALL, NONE, TCP, and SNA. In this case, the default value ALL is used.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
42
●
PGTS1396E MANAGE_INTERFACE_PROTOCOL must be ALL, NONE, TCP, SNA: Defaulting to
ALL
Explanation:
The GLOBAL MANAGE_INTERFACE_PROTOCOL parameter was defined incorrectly. The valid values
are ALL, NONE, TCP, and SNA. In this case, the default value ALL is used.
●
PGTS1397E RESPONDER_PROFILE_LPASS must be YES or NO: Defaulting to NO
Explanation:
The GLOBAL RESPONDER_PROFILE_LPASS parameter was defined incorrectly. The valid values are
and NO. In this case, the default value NO is used.
Yes
●
PGTS1398E SMTP_DEST must be 8 characters or less
Explanation:
The value entered for the GLOBAL SMTP_DEST parameter was invalid. The valid values are from 1
to 8 characters. In this case, this parameter is ignored.
●
PGTS1399E TEXTEOFTERM must be YES or NO
Explanation:
The GLOBAL TEXTEOFTERM parameter was defined incorrectly. The valid values are Yes and NO. In
this case, this parameter is ignored and the default value NO is used.
●
PGTS1400E SAPI_DEST must be 1 to 8 Characters
Explanation:
The value entered for the node SAPI_DEST parameter was invalid. The valid values are from 1 to 8
characters. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1401E SAPI_WRITER must be 1 to 8 Characters
Explanation:
The value entered for the node SAPI_WRITER parameter was invalid. The valid values are from 1 to 8
characters. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1402E SAPI_FORM must be 1 to 8 Characters
Explanation:
The value entered for the node SAPI_FORM parameter was invalid. The valid values are from 1 to 4
characters. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1403E SAPI_DISP must be DELETE/HOLD/KEEP for Normal,NetworkError,Error
parameters
Explanation:
The value entered for the node SAPI_DISP parameter was invalid. The valid values are KEEP, HOLD
or DELETE. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1404E DEFAULT_USERID must be 1 to 20 characters
Explanation:
The value entered for the node DEFAULT_USERID parameter was invalid. The valid values are from 1
to 20 characters. The node entry is not enabled.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
43
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1405E DEFAULT_PASSWORD must be 1 to 20 characters
Explanation:
The value entered for the node DEFAULT_PASSWORD parameter was invalid. The valid values are
from 1 to 20 characters. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1407E SAPI_REMOTE_FILE must be 1 to 64 characters
Explanation:
The value entered for the node SAPI_REMOTE_FILE parameter was invalid. The valid values are
from 1 to 64 characters. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1408E SAPI_TRY must be a number from 0 to 9999
Explanation:
The value entered for the node SAPI_TRY parameter was invalid. The valid values are between 1 and
The node entry is not enabled. Correct the node definition, and enable the node using the
Platform Server ENA operator command.
9999.
●
PGTS1409E COMPRESS must be LZ/RLE/YES/NO
Explanation:
The value entered for the node COMPRESS parameter was invalid. The valid values are LZ, RLE, YES,
or NO. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1410E CHECKPOINT must be a number from 1 to 999
Explanation:
The value entered for the node CHECKPOINT parameter was invalid. The valid values are any number
between 1 and 999, YES, or NO. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1411E SAPI_REMOTE_PRINTER must be 1 to 64 characters
Explanation:
The value entered for the node SAPI_REMOTE_PRINTER parameter was invalid. The valid values are
from 1 to 64 characters. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1412E DEFAULT_LOGON_DOMAIN must be 1 to 16 characters
Explanation:
The value entered for the node DEFAULT_LOGON_DOMAIN parameter was invalid. The valid values are
from 1 to 16 characters. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1413E DEFAULT_NODECLASS must be a number between 0 and 255
Explanation:
The value entered for the node DEFAULT_NODECLASS parameter is invalid. The valid values are
between 0 and 255. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
44
●
PGTS1414E DEFAULT_NODECLASS must be less than or equal to WINNERS parameter
Explanation:
The value entered for the node DEFAULT_NODECLASS parameter was invalid. The value for this
parameter must be less than or equal to the node WINNERS parameter.
●
PGTS1415E HIPAA must be YES or NO
Explanation:
The value entered for the node HIPAA parameter was invalid. The valid values are YES and NO. The
node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1416E CFWEB_SUPPORT must be ALTER/VIEW/NO
Explanation:
The value entered for the node CFWEB_SUPPORT parameter was invalid. The valid values are
ALTER,VIEW, and NO. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1417E DEFAULT_TYPE must be TEXT/BINARY/DATA
Explanation:
The value entered for the node DEFAULT_TYPE parameter was invalid. The valid values are
TEXT,BINARY, and DATA. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1418E DEFAULT_CRLF must be CRLF/LF/NONE
Explanation:
The value entered for the node DEFAULT_CRLF parameter was invalid. The valid values are CRLF,LF,
and NONE. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1419E TRAP_TRANSFER_REQUESTS must be YES/NO/ERRORS
Explanation:
The value entered for the node TRAP_TRANSFER_REQUESTS parameter was invalid. The valid values
are YES,NO, and ERRORS. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1420E xxxxxxxxx parameter invalid value: Must be Numeric and less than
999,999,999 (last Byte can be M or K)
Explanation:
The value entered for the node BPS_xxxxxxxx parameter was invalid. The valid values are between
1490 and 999,999,999. The last byte can be M to indicate Megabytes or K to indicate Kilobytes. The
node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1421E DEFAULT_COSNAME must be 1 to 16 characters
Explanation:
The value entered for the node DEFAULT_COSNAME parameter was invalid. The valid values are
between 1 and 8 characters. The last byte can be M to indicate Megabytes or K to indicate Kilobytes.
The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
45
●
PGTS1422E XBUFSIZE must be a number between 1490 and 99999999
Explanation:
The value entered for the COS xBUFSIZE parameter was invalid. The valid values are between 1490
and 999,999,999. The COS definition is not enabled.
Correct the COS definition, and enable the COS using the Platform Server ENA operator command.
●
PGTS1423E DAYS must be 7 characters of Y or N
Explanation:
The value entered for the COS DAYS parameter was invalid. The valid values must be 7 characters,
and each character must be Y or N. The characters represent the days of the week starting with
Sunday. The COS definition is not enabled.
Correct the COS definition, and enable the COS using the Platform Server ENA operator command.
●
PGTS1424E XTIME must be a 4 digits of HHMM, between 0000 and 2400: ETIME must be
Greater than STIME
Explanation:
The value entered for the COS STIME or ETIME parameter was invalid. The valid values are between
0000 and 2400. The ETIME value must be greater than STIME. The COS definition is not enabled.
Correct the COS definition, and enable the COS using the Platform Server ENA operator command.
●
PGTS1425E xxxxxxxx parameter missing: Must follow yyyyyyyy
Explanation:
The COS entry defined was incorrect. The order of parameters is specific and all parameters must be
entered. This message indicates that parameter xxxxxxxx must immediately follow parameter
yyyyyyyy. The COS definition is not enabled.
Correct the COS definition, and enable the COS using the Platform Server ENA operator command.
●
PGTS1426E COS DAYS parmaeter exceeds maximum allowed of 9 per COS entry
Explanation:
The COS entry defined was incorrect. 0 to 9 DAYS parameters can be defined for a single COS entry.
This message indicates more than 9 DAYS parameters are defined for a single COS entry. The COS
definition is not enabled.
Correct the COS definition, and enable the COS using the Platform Server ENA operator command.
●
PGTS1427E PRIORITY must be a 1 digit number between 0 and 9
Explanation:
The COS entry defined was incorrect. The PRIORITY field must be a number between 0 and 9. The
COS definition is not enabled.
Correct the COS definition, and enable the COS using the Platform Server ENA operator command.
●
PGTS1428E DEFAULT_LOCALCTFILE must be between 1 and 16 characters
Explanation:
The value entered for the node DEFAULT_LOCALCTFILE parameter was invalid. The valid values
must be between 1 and 16 characters long. The node entry is not enabled. Correct the node
definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1429E DEFAULT_REMOTECTFILE must be between 1 and 16 characters
Explanation:
The value entered for the node DEFAULT_REMOTECTFILE parameter was invalid. The valid values
must be between 1 and 16 characters long. The node entry is not enabled.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
46
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1430E CONVTBL(XLATE) error: Each line must contain 32 hexadecimal characters
(0-F)
Explanation:
The XLATE (Translate Table entry) entered was incorrect. An entry in the XLATE table does not
have 32 hexadecimal characters defined. Each line in the XLATE table must consist of 32
hexadecimal characters (0-9,A,B,C,D,E,F). The XLATE definition is not enabled.
Correct the XLATE definition, and enable the node using the Platform Server ENA operator
command.
●
PGTS1431E CONVTBL(XLATE) error: There must be exactly 32 lines of conversion
table data
Explanation:
The XLATE (Translate Table entry) entered was incorrect. An entry in the XLATE table does not
have 32 hexadecimal characters defined. There must be exactly 32 lines of XLATE data defined for
each XLATE table entry. The XLATE definition is not enabled.
Correct the XLATE definition, and enable the node using the Platform Server ENA operator
command.
●
PGTS1432E xxxxxxxx Disable failed: CONVTBL(XLATE) entries cannot be disabled
(they can be REFreshed)
Explanation:
XLATE table entries cannot be disabled after they are enabled. They can be refreshed by using the
Platform Server operator commandREF. The XLATE entry remains enabled.
●
PGTS1449E AUTOENABLE must be YES or NO
Explanation:
The value entered for the node AUTOENABLE parameter was invalid. The valid values are YES or NO.
The node entry is not enabled. Correct the node definition, and enable the node using the Platform
Server ENA operator command.
●
PGTS1450E COMMAND_CENTER_SUPPORT parameters allowed are: ALL|NONE|
NODE,PROFILE,TRANSFER,AUDIT,ALTER,PING
Explanation:
The value entered for the node COMMAND_CENTER_SUPPORT parameter was invalid. The valid values
are ALL, NONE, NODE, PROFILE, AUDIT, PING, ALTER, or TRANSFER. If more than one value is defined,
the values must be separated by commas. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1452E ENFORCE_SECURITY_POLICY must be HIPAA, FIPS, or NONE
Explanation:
The value entered for the node ENFORCE_SECURITY_POLICY parameter was invalid. The valid values
are HIPAA, FIPS140, or NONE. The ENFORCE_SECURITY_POLICY parameter is ignored and the node
entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1453E ENFORCE_SECURITY_POLICY=FIPS140 not allowed when FIPS is not set in
GLOBAL
Explanation:
The node ENFORCE_SECURITY_POLICY parameter was set to FIPS140. However, the GLOBAL
parameter was not set to FIPS140. The node
ENFORCE_SECURITY_POLICY
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
47
parameter cannot be set to use FIPS140 unless the GLOBAL
parameter is also set to FIPS140. The node ENFORCE_SECURITY_POLICY
parameter is ignored and the node is not activated.
ENFORCE_SECURITY_POLICY
ENFORCE_SECURITY_POLICY
Change either the global or the node ENFORCE_SECURITY_POLICY parameter.
●
PGTS1454E ENFORCE_SECURITY_POLICY=FIPS140 not allowed for SNA nodes
Explanation:
The node ENFORCE_SECURITY_POLICY parameter was set to FIPS140. However, this node is defined
as an SNA node and FIPS140 cannot be used for SNA nodes. The node ENFORCE_SECURITY_POLICY
parameter is ignored and the node is not activated.
Change the ENFORCE_SECURITY_POLICY parameter to HIPAA or NONE.
●
PGTS1455E NODE ENFORCE_SECURITY_POLICY=FIPS140 requires TLS=YES or TLS=TUNNEL
Explanation:
The node ENFORCE_SECURITY_POLICY parameter was set to FIPS140. The FIPS 140 mode requires
the node to be defined as a TLS/ SSL node; however, this node is not defined as a TLS/SSL node.
The ENFORCE_SECURITY_POLICY parameter is ignored and the node is not activated.
●
Either define the node as a TLS/SSL node; or change the ENFORCE_SECURITY_POLICY to HIPAA or
NONE.
●
PGTS1456E GLOBAL ENFORCE_SECURITY_POLICY=FIPS140 requires TLS=YES or TLS=TUNNEL
Explanation:
The node was defined using the GLOBAL default ENFORCE_SECURITY_POLICY parameter, which
was set to FIPS140. FIPS 140 mode requires the node to be defined as a TLS/SSL node; however,
this node is not defined as a TLS/SSL node. The ENFORCE_SECURITY_POLICY parameter is ignored
and the node is not activated.
●
Either define the node as a TLS/SSL node; or change the ENFORCE_SECURITY_POLICY to HIPAA or
NONE.
●
PGTS1457E MQ_GOOD must be from 1 to 64 characters and must start with $MQ:
Explanation:
The value entered for the node MQ_GOOD parameter was invalid. The valid values must be a valid
MQ Message Queue, 64 characters or less, and start with the value $MQ. The node entry is not
enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1458E MQ_FAIL must be from 1 to 64 characters and must start with $MQ:
Explanation:
The value entered for the node MQ_FAIL parameter was invalid. The valid values must be a valid
MQ Message Queue, 64 characters or less, and start with the value $MQ. The node entry is not
enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1459E EMAIL_GOOD must be from 1 to 64 characters
Explanation:
The value entered for the node EMAIL_GOOD parameter was invalid. The valid values must be a valid
email address, 64 characters or less. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1460E EMAIL_FAIL must be from 1 to 64 characters
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
48
The value entered for the node EMAIL_FAIL parameter was invalid. The valid values must be a valid
email address, 64 characters or less. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1461E MQ_NOTIFY must be INITIATOR/RESPONDER/BOTH/NONE
Explanation:
The value entered for the node MQ_NOTIFY parameter was invalid. The valid values are INITIATOR,
RESPONDER, BOTH, or NONE. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1462E EMAIL_NOTIFY must be INITIATOR/RESPONDER/BOTH/NONE
Explanation:
The value entered for the node EMAIL_NOTIFY parameter was invalid. The valid values are
or NONE. The node entry is not enabled.
INITIATOR, RESPONDER, BOTH,
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1463E NODENAME must be from 1 to 32 characters
Explanation:
The value entered for the node NODENAME parameter was invalid. The valid values must be from 1 to
32 characters without any embedded spaces. The node entry is not enabled.
Correct the node definition, and enable the node using the Platform Server ENA operator command.
●
PGTS1464E Duplicate NODENAME on REFRESH, ENABLE or during Initialization:
xxxxxxxx
Explanation:
When enabling a node definition, a duplicate node name or node member name was detected.
Before enabling a member, the node name or node member name is checked to make sure that it is
unique within the system. If not, the node is not enabled and this error message is displayed.
Nodes can be enabled in one of the following ways:
At startup time
Through the operator ENA or REF command
Through Command Center
●
PGTS1465E ALLOW_TRANSFER_REQUESTS must be YES, NO or LOGON
Explanation:
The node ALLOW_TRANSFER_REQUESTS parameter was defined incorrectly. The valid values are: YES,
NO, and LOGON. The node is not enabled.
Correct the parameter and then enable the node manually using the ENABLE modify command.
●
PGTS1466E ALLOW_MANAGE_REQUESTS must be YES, NO or LOGON
Explanation:
The node ALLOW_MANAGE_REQUESTS parameter was defined incorrectly. The valid values are: YES, NO,
and LOGON. The node is not enabled.
Correct the parameter and then enable the node manually using the ENABLE modify command.
●
PGTS1467E TCPCONNECT_ADAPTER_IPADDR_IPV4 must be valid IPV4 Address
Explanation:
The value entered for the node TCPCONNECT_ADAPTER_IPADDR_IPV4 parameter was invalid. The
node is not enabled.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
49
Correct the parameter and then enable the node manually using the ENABLE modify command.
●
PGTS1468E TCPCONNECT_ADAPTER_IPADDR_IPV6 must be valid IPV6 Address
Explanation:
The value entered for the node TCPCONNECT_ADAPTER_IPADDR_IPV6 parameter was invalid. The
node is not enabled.
Correct the parameter and then enable the node manually using the ENABLE modify command.
●
PGTS1469E TCPCONNECT_ADAPTER_IPADDR defined for Node that is not TCP
Explanation:
The TCPCONNECT_ADAPTER_IPADDR_IPV4 or TCPCONNECT_ADAPTER_IPADDR_IPV6 parameter was
entered for a node that is not a TCP node. These parameters are only supported when the node is a
TCP node. The node is not enabled.
Correct the parameter and then enable the node manually using the ENABLE modify command.
●
PGTS1470E TCPCONNECT_ADAPTER_IPADDR_IPV6 defined for an IPV4 node
Explanation:
The TCPCONNECT_ADAPTER_IPADDR_IPV6 parameter was entered for a node that is defined with an
IPv4 address. This parameter is only supported when the node is defined with an IPv6 address. The
node is not enabled.
Correct the parameter and then enable the node manually using the ENABLE modify command.
●
PGTS1471E TCPCONNECT_ADAPTER_IPADDR_IPV4 defined for an IPV6 node
Explanation:
The TCPCONNECT_ADAPTER_IPADDR_IPV4 parameter was entered for a node that is defined with an
IPv6 address. This parameter is only supported when the node is defined with an IPv4 address. The
node is not enabled.
Correct the parameter and then enable the node manually using the ENABLE modify command.
●
PGTS1472E INITIATOR_ERROR_HOLD must be a number from 0 to 9999
Explanation:
The value entered for the node INITIATOR_ERROR_HOLD parameter was incorrect. The valid values
are from 0 to 9999. The node is not enabled.
Correct the value and then enable the node using the ENA operator command.
●
PGTS1473E INITHOLD must be YES or NO
Explanation:
The value entered for the node INITHOLD parameter was incorrect. The valid values are YES or NO.
The node is not enabled.
Correct the value and enable the node using the ENA operator command.
●
PGTS1474E RESPHOLD must be YES or NO
Explanation:
The value entered for the node RESPHOLD parameter was incorrect. The valid values are YES or NO.
The node is not enabled.
Correct the value and enable the node using the ENA operator command.
●
PGTS1475E CRCCHECK must be YES or NO
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
50
The NODE
enabled.
CRCCHECK
parameter was entered incorrectly. Valid values are YES and NO. The node is not
Correct the value and enable the node through the ENA operator command.
●
PGTS1500E DATACLASS_DEFAULT_VOLCT must be a number from 0 to 255
Explanation:
The value entered for the GLOBAL DATACLASS_DEFAULT_VOLCT parameter was invalid. The valid
values are between 0 and 255. The Platform Server administrator must correct the parameter and
restart the started task.
●
PGTS1501E MAXSCRIPTS must be a number from 1 to 999
Explanation:
The value entered for the GLOBAL MAXSCRIPT parameter was incorrect. The valid values are from 1
to 999. The default value 50 is used.
●
PGTS1502E MAXSCRIPTS must <= MAXINIT: Changing MAXSCRIPT to nnn
Explanation:
The value entered for the GLOBAL MAXSCRIPT parameter was greater than the MAXINITS parameter.
The MAXSCRIPTS parameter must be less than or equal to the MAXINITS parameter. The MAXSCRIPTS
value is changed to the value defined for the MAXINITS parameter.
●
PGTS1503E MIXED_CASE_PASSWORDS must be YES or NO
Explanation:
The value entered for the GLOBAL MIXED_CASE_PASSWORDS parameter was incorrect. The valid
values are YES or NO. The default value NO is used and the startup continues.
●
PGTS1504E EMAILSUBGOOD must be 58 characters or less
Explanation:
The value entered for the GLOBAL EMAILSUBGOOD parameter was incorrect. The valid values must
be from 1 to 58 characters. The default value is used and the startup continues.
●
PGTS1505E EMAILSUBFAIL must be 58 characters or less
Explanation:
The value entered for the GLOBAL EMAILSUBFAIL parameter was incorrect. The valid values must
be from 1 to 58 characters. The default value is used and the startup continues.
●
PGTS1506E TCP_CONNECT_TIMEOUT must be a number between 10 and 180
Explanation:
The value entered for the GLOBAL TCP_CONNECT_TIMEOUT parameter was incorrect. The valid
values must be a number between 10 and 180 seconds. No TCP timeout is used. The started task
waits for TCP to timeout the connection requests.
●
PGTS1508E TCPIPPORT_IPV6 must be a value from 1025 to 65535
Explanation:
The value entered for the GLOBAL TCPIPORT_IPV6 parameter was incorrect. The valid values must
be a number between 1025 and 65535. The default value 0 is used and IPv6 is not enabled for
incoming non-SSL requests.
●
PGTS1509E SSLIPPORT_IPV6 must be a value from 1025 to 65535
Explanation:
The value entered for the GLOBAL SSLIPORT_IPV6 parameter was incorrect. The valid values must
be a number between 1025 and 65535. The default value 0 is used and IPv6 is not enabled for
incoming SSL requests.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
51
●
PGTS1510E TCPLISTEN_ADAPTER_IPADDR_IPV6 not a valid IPV6 Address
Explanation:
The value entered for the TCPLISTEN_ADAPTER_IPADDR_IPV6 parameter was incorrect. The valid
values must be a valid colon delimited IPv6 address.
●
PGTS1511E SSLLISTEN_ADAPTER_IPADDR_IPV6 not a valid IPV6 Address
Explanation:
The value entered for the SSLLISTEN_ADAPTER_IPADDR_IPV6 parameter was incorrect. The valid
values must be a valid colon delimited IPv6 address.
●
PGTS1512E TCPCONNECT_ADAPTER_IPADDR_IPV6 not a valid IPV6 Address
Explanation:
The value entered for the TCPCONNECT_ADAPTER_IPADDR_IPV6 parameter was incorrect. The valid
values must be a valid colon delimited IPv6 address.
●
PGTS1513E ALLOW_TRANSFER_REQUESTS must be YES, NO or NODE
Explanation:
The value entered for the GLOBAL ALLOW_TRANSFER_REQUESTS parameter was incorrect. The valid
values are: YES, NO, or NODE. The default value YES is used.
Correct the parameter and restart the started task.
●
PGTS1514E ALLOW_MANAGE_REQUESTS must be YES, NO or NODE
Explanation:
The value entered for the GLOBAL ALLOW_MANAGE_REQUESTS parameter was incorrect. The valid
values are: YES, NO, or NODE. The default value YES is used.
Correct the parameter and restart the started task.
●
PGTS1515E SSL_REQUEST_IPV6 must be YES/NO/OUTSIDE_NETWORK
Explanation:
The value entered for the GLOBAL SSL_REQUEST_IPV6 parameter was incorrect. The valid values
are: YES, NO, or OUTSIDE_NETWORK. The default value NO is used.
Correct the parameter and restart the started task.
●
PGTS1516E SSL_NETWORK_IPADDR_IPV6 must be a valid IPV6 Address
Explanation:
The value entered for the GLOBAL SSL_NETWORK_IPADDR_IPV6 parameter was incorrect. The valid
values must be a valid colon delimited IPv6 address.
Correct the parameter and restart the started task.
●
PGTS1517E SSL_SUBNET_IPV6 must be a number between 0 and 128 and a multiple of 8
Explanation:
The value entered for the SSL_SUBNET_IPV6 parameter was incorrect. The valid values must be a
number between 0 and 128, and it must be a multiple of 8.
Correct the parameter and restart the started task.
●
PGTS1518E SSL_NETWORK_SUBNET_IPV6 required when SSL_REQUEST_IPV6=OUTSIDE_NETWORK:
Defaults to 0
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
52
The GLOBAL SSL_REQEUST_IPV6 parameter was defined as OUTSIDE_NETWORK but the
parameter was not defined. SSL_NETWORK_SUBNET_IPV6 must be
defined when OUTSIDE_NETWORK is defined.
SSL_NETWORK_SUBNET_IPV6
Correct the error and restart the started task.
●
PGTS1519E IGNORE_EBCDIC_LF must be YES or NO
Explanation:
The value entered for the GLOBAL IGNORE_EBCDIC_LF parameter was incorrect. The valid values
are YES or NO. The default value NO is used.
Correct the parameter and restart the started task.
●
PGTS1520E ENQ_ENTIRE_TRANSFER must be YES or NO
Explanation:
The GLOBAL ENQ_ENTIRE_TRANSFER parameter was defined incorrectly. The values supported are
and NO. The default value is NO.
YES
Correct the parameter and restart the started task.
●
PGTS1521E FIND_NODE_COMPATIBILITY must be Yes or No
Explanation:
The GLOBAL FIND_NODE_COMPATIBILITY parameter was defined incorrectly. The values supported
are YES and NO. The default value is NO.
Correct the parameter and restart the started task.
●
PGTS1522E TLSENABLEDPROTOCOLS MUST BE ALL OR TLSV1,TLSV2,TLSV3 WITH NO SPACES
Explanation:
The GLOBAL TLSENABLEDPROTOCOLS parameter was defined incorrectly. The values supported are
or TLSV1,TLSV2,TLSV3; no spaces are allowed in this parameter. The default value is ALL.
ALL
Correct the parameter and restart the started task.
●
PGTS1523E CRCCHECK must be YES or NO
Explanation:
The GLOBAL CRCCHECK parameter was defined incorrectly. The values supported are YES and NO.
The default value is NO.
Correct the parameter and restart the started task.
●
PGTS1524E UNEXPIRED_DISK_FILE_DELETE must be YES or NO
Explanation:
The GLOBAL UNEXPIRED_DISK_FILE_DELETE parameter was defined incorrectly. The values
supported are YES and NO. The default value is NO.
Correct the parameter and restart the started task.
●
PGTS1525E UNEXPIRED_DISK_FILE_UPDATE must be YES or NO
Explanation:
The GLOBAL UNEXPIRED_DISK_FILE_UPDATE parameter is defined incorrectly. The values
supported are YES and NO. The default value is NO. Correct the parameter and restart the started
task.
●
PGTS1526E TLSTUNNELIPPORT must be a value from 1025 to 65535
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
53
The GLOBAL TLSTUNNELIPPORT parameter was defined incorrectly. The value defined must be a
number between 1025 and 65535. The default value of 0 is used and TLS tunneling for IPV4 is not
enabled for incoming TLS tunnel requests.
●
PGTS1527E TLSTUNNELIPPORT_IPV6 must be a value from 1025 to 65535
Explanation:
The GLOBAL TLSTUNNELIPPORT_IPV6 parameter was defined incorrectly. The value defined must
be a number between 1025 and 65535. The default value of 0 is used and TLS tunneling for IPV6 is
not enabled for incoming TLS tunnel requests.
●
PGTS1528E Up to 64 TLSCIPHERS may be defined: Each cipher must be 4 hex digits(0F)
Explanation:
The GLOBAL TLSCIPHERS parameter was defined incorrectly. The number must be 4 hex digits
from 0-F. A maximum of 64 TLS ciphers may be defined. We suggest selecting ciphers from the list
of TLS ciphers defined in the default SAMPLIB GLOBAL member.
●
PGTT1606E xxxx error received R15=yyyy R0=zzzz
Explanation:
An error occurred during the creation or modification of VTAM control blocks. xxxx is the action
and the control block, and yyyy and zzzz are the return codes in R15 and R0 respectively.
Save this information and contact TIBCO Technical Support.
●
PGTS1529E ZEDCCOMPRESSION must be YES or NO
Explanation:
The GLOBAL parameter ZEDCCOMPRESSION was defined incorrectly. The only two values allowed
are YES and NO.
Fix the GLOBAL ZEDCCOMPRESSION parameter and restart the MFT Server.
●
PGTT1607E ACB address not available - possibly ACB NOT OPENED successfully
Explanation:
An error occurred when trying to open the ACB.
Check that the ACB is defined properly to VTAM.
●
PGTS1608E OPEN ERROR xxxx FOR ACB yyyy REPLY E(ND), C(ONTINUE), R(ETRY)
Explanation:
An error occurred when trying to open the ACB.
Check that the ACB is defined properly to VTAM.
●
PGTT1608E ACB open error R15=xxxx ACBERFLG=yyyy for ACB zzzz
Explanation:
Most probable cause is that the ACB was specified incorrectly.
Check to see that you specified the correct ACB name in the global parameters.
●
PGTT1610E Set logon failed RTNCD=xxxx FDBK2=yyyy
Explanation:
A failure occurred during log in. This message will most likely be issued along with the message
PGTT1607 or PGTT1608.
●
PGTT1611E ACB CLOSE error R15=xxxx ACBERFLG=yyyy
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
54
An error occurred when attempting to close the ACB.
●
PGTT1613E ACB CLOSE requested - ACB address not available
Explanation:
The address of the ACB was invalid.
If you receive this message, contact TIBCO Technical Support.
●
PGTT1614E Invalid LU6.2 GDS received for LU xxxx - GDS=yyyy
Explanation:
An internal error occurred for LU xxxx. An invalid GDS yyyy was received.
Recreate the problem with Platform Server tracing activated (F
TIBCO Technical Support.
●
servername,TRON),
and contact
PGTT1615E LU xxxx - received data length yyyy longer than maximum requested zzzz
concatlen nnnn
Explanation:
An internal error occurred for LU xxxx. A record of length yyyy was received which exceeded zzzz
or nnnn.
Recreate the problem with Platform Server tracing activated (F
TIBCO Technical Support.
●
servername,TRON),
and contact
PGTT1616E VTAM ERROR code on xxxx macro R15=yyyy R0=zzzz RTNCD=aaaa RCFDBK2=bbbb
Explanation:
An error occurred using the xxxx VTAM macro. Registers 15 and 0 are yyyy and zzzz respectively,
and the VTAM return code and feedback information are aaaa and bbbb.
See the appropriate VTAM manual. If the problem persists, contact .
●
PGTT1617E Error on xxxx APPC Request - ACB not defined as APPC=YES
Explanation:
In the APPL definition for VTAM, the parameter APPC=YES was not specified. This is a requirement
of the Platform Server when using SNA.
Specify it and then restart the server.
●
PGTT1618E FMH7 received in response to xxxx command - SENSE=yyyy Message follows
Explanation:
An error response was received to VTAM command xxxx. The sense returned was yyyy.
see the appropriate VTAM manual for information regarding this sense code.
●
PGTT1619E APPC Error received on xxxx request - PRI=yyyy SEC=zzzz for LU=nnnn
Explanation:
An error was received while processing the specified request type. The LU name along with
primary and secondary return codes were also provided.
See the IBM VTAM documentation for the cause of this error.
●
PGTT1620E Error opening VTAMTRAC DD - Tracing Disabled
Explanation:
The Platform Server encounters an error trying to open up the file specified in the VTAM trace DD
statement. This DD statement is specified in the Platform Server startup PROC. Check the contents of
the DD statement to verify that they are specified correctly.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
55
●
PGTT1621E Invalid Platform Server request type xxxx received
Explanation:
Transfer type is usually Send or Receive.
●
PGTT1623E ATTACH for Module: FUSASNAR Failed - xxxx
Explanation:
The module was not attached.
Contact TIBCO Technical Support.
●
PGTT1626E Unable to override CINIT for LU:xxxx MODE:yyyy - Check VTAM APAR
OY63512 PTF UY94805
Explanation:
The Platform Server attempted to override the information in CINIT. This might be caused by a
known problem with VTAM.
●
PGTT1627E Zero length LU62 GDS received for LU xxxx - GDS=yyyy
Explanation:
GDS yyyy was received for LU xxxx with a zero length. This is an internal error.
Recreate the problem with the Platform Server tracing activated (F
TIBCO Technical Support.
●
servername,TRON),
and contact
PGTT1628E Error Data GDS (12F4) received for LU xxxx - Errordata=yyyy
Explanation:
An error data GDS was received from LU xxxx. The error data returned was yyyy.
Recreate the problem with the Platform Server tracing activated (F
TIBCO Technical Support.
●
servername,TRON),
and contact
PGTT1630E Validation Failed on FMH5 Access Security Fields 080F6051 sense
returned - Message follows:
Explanation:
A security check failed. This message is Issued along with PGTT1631E.
See PGTT1631E for the text of the security system message.
●
PGTT1631E << Text of RACROUTE failure message >>
Explanation:
A RACROUTE request failed.
See the appropriate security packages documentation for the reason for the failure.
●
PGTT1650E Allocation Failure Retry Error for LU:xxxx on APPC-CMD=yyyy RCPRI=zzzz
MODENAME=nnnn
Explanation:
Connection to the remote side was not made because of an error in the LU name or mode name.
Make sure they are defined correctly. Also check the VTAM return code as given by the RCPRI
value.
●
PGTT1651E Partner Transaction program NOT Available Error for LU=xxxx on
APPCCMD=yyyy RCPRI=zzzz MODENAME=nnnn
Explanation:
The transaction program on the remote side iwas not started.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
56
Make sure the LU name and mode name are correct.
●
PGTT1652E Dealloc Requested error for LU=xxxx on APPCCMD=yyyy RCPRI=zzzz
MODENAME=nnnn
Explanation:
Deallocation error because of an error in the LU name or mode name.
Make sure they are defined correctly. Also check the VTAM return code as given by the RCPRI value.
●
PGTT1653E Invalid Mode error for LU=xxxx on APPCCMD=yyyy RCPRI=zzzz MODENAME=nnnn
Explanation:
Connection to the remote side was not made because of an error in the mode name.
Make sure it is defined correctly. Also check the VTAM return code as given by the RCPRI value.
●
PGTT1654E Invalid Conversion error for LU=xxxx on APPCCMD=yyyy RCPRI=zzzz
MODENAME=nnnn
Explanation:
Connection to the remote side was not made because of an error.
Make sure the LU name and the mode name are defined correctly. Also check the VTAM return
code as given by the RCPRI value.
●
PGTT1655E Invalid LU error for LU=xxxx on APPCCMD=yyyy RCPRI=zzzz MODENAME=nnnn
Explanation:
Connection to the remote side was not made because of an error in the LU name.
Make sure it was defined correctly. Also check the VTAM return code as given by the RCPRI value.
●
PGTT1656E Resource Failure, No Retry for LU=xxxx on APPCCMD=yyyy RCPRI=zzzz
MODENAME=nnnn
Explanation:
Connection to the remote side was not made because of a resource failure and will not be retried.
Check the LU name and mode name. Make sure they are defined correctly. Also check the VTAM
return code as given by the RCPRI value.
●
PGTT1657E State Error for LU=llllllll on APPCCMD=cccccccc RCPRI=rrrrrrrr
SENSE=ssssssss MODENAME=mmmmmmmm
Explanation:
The Platform Server issued a VTAM request cccccccc. VTAM returned an error indicating that there
was a STATE error during the conversation. The conversation will be terminated. This error can
sometimes occur during the cleanup of a previous error.
If this error occurs during a normal file transfer, then take a the Platform Server trace (F
and send the trace to TIBCO Technical Support.
CFUSION,TRON),
●
PGTT1658E VTAM INACTIVE for ACB for LU=xxxx on APPCCMD=yyyy RCPRI=nnnn
MODENAME=xxxx
Explanation:
Make sure the ACB for the started task is active.
●
PGTT1659E Deallocate Normal error for LU=xxxx on APPCCMD=yyyy RCPRI=zzzz
MODENAME=nnnn
Explanation:
Deallocation error occurred because of an error in the LU name or mode name.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
57
Make sure they are defined correctly. Also check the VTAM return code as given by the RCPRI value.
●
PGTT1660E Unsuccessful, Session Not Available for LU=xxxx on APPCCMD=yyyy
RCPRI=nnnn MODENAME=xxxx
Explanation:
No more sessions were available to make a connection with the remote system.
●
PGTT1661E Invalid LU Name LU=xxxx APPCCMD=yyyy RCPRI=zzzz MODENAME=nnnn
Explanation:
Connection to the remote side was not made because of an error in the LU name.
Make sure the LU name is defined correctly. Also check the VTIs AM return code as given by the
value.
RCPRI
●
PGTT1662E Partner LU rejected Security information passed in APPC FMH5
Explanation:
The remote user ID and/or password might be invalid.
●
PGTV1710E TCPERR xxxx on yyyy req ip=zzzz: nnnn
Explanation:
A TCP/IP error occurred. TCP return code was xxxx. yyyy was the type of TCP/IP request. zzzz was
the IP address. nnnn was the meaning of the return code if known.
●
PGTV1711E TCP Address Zero - possibly TCP connection not started
Explanation:
Bad configuration or TCP/IP was not started. A possible cause is that the TCP/IP jobname was
specified incorrectly in the global parameters.
●
PGTV1713E TCP INITAPI FAILED FOR TCP STC xxxx - ASID yyyy - TCP processing
terminated
Explanation:
The TCP/IP INITAPI request failed for TCP/IP job xxxx in ASID yyyy.
Make sure that TCP/IP is active. If the problem persists, enable the Platform Server TCP/IP tracing
(F servername,TCPTRON) and contact TIBCO Technical Support.
●
PGTT1714E IP nnn.nnn.nnn.nnn - received invalid data xxxx on yyyy request
Explanation:
A request was received from IP node nnn.nnn.nnn.nnn. The Platform Server issued a request
denoted by yyyy. The data that was received (xxxx)was not the data that was expected. For example,
a RCVFMH5 request was executed, but a DEALLOC request was received instead of an FMH5. Because
the Platform Server uses both TCP and SNA interchangeably, SNA terms such as FMH5 are also
used when communicating under TCP.
If the problem persists, enable the Platform Server TCP/IP tracing (F
contact TIBCO Technical Support.
●
servername,TCPTRON)
and
PGTT1715E IP nnn.nnn.nnn.nnn - received data length xxxx longer than Max Req.
yyyy ConcatLen zzzz
Explanation:
An internal error occurred for IP address nnn.nnn.nnn.nnn. A record of length xxxx was received
which exceeded yyyy or zzzz.
If the problem persists, enable the Platform Server TCP/IP tracing (F
contact TIBCO Technical Support.
servername,TCPTRON)
and
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
58
●
PGTT1716E Invalid LU6.2 GDS received for IP nnn.nnn.nnn.nnn - GDS=xxxx
Explanation:
An internal error occurred for IP address nnn.nnn.nnn.nnn. An invalid GDS xxxx was received. This
might be the result of improper RocketStream protocol setting.
Check the transfer settings and try again. If the problem persists, enable the Platform Server TCP/IP
tracing (F servername,TCPTRON) and TIBCO Technical Support.
●
PGTT1718E FMH7 received in response to xxxx command - SENSE=yyyy Message follows
Explanation:
An error occurred. An additional message is displayed with details of the error.
●
PGTT1720E error opening TCPTRAC DD - TCP tracing Disabled
Explanation:
The Platform Server encountered an error when trying to open the file specified in the TCPTRAC
DD statement in the startup PROC.
Check the contents of the DD statement to verify if they are specified correctly.
●
PGTT1727E Zero length LU62 GDS received for IP nnn.nnn.nnn.nnn - GDS=xxxx
Explanation:
GDS xxxx was received for IP address nnn.nnn.nnn.nnn with a zero length. This is an internal error.
Recreate the problem with the Platform Server TCP/IP tracing activated (F
and contact TIBCO Technical Support.
●
servername,TCPTRON)
PGTT1728E Error Data GDS (12F4) received for IP nnn.nnn.nnn.nnn - Errordata=xxxx
Explanation:
An error data GDS was received from IP address nnn.nnn.nnn.nnn. The error data returned was
xxxx.
Recreate the problem with the Platform Server TCP/IP tracing activated (F
and contact TIBCO Technical Support.
●
servername,TCPTRON)
PGTT1729E Invalid TCP GDS received for IP nnn.nnn.nnn.nnn
Explanation:
An invalid GDS was received from IP address nnn.nnn.nnn.nnn.
Recreate the problem with the Platform Server TCP/IP tracing activated (F
and contact TIBCO Technical Support.
●
servername,TCPTRON)
PGTT1730E Invalid IP Dotted Decimal address: nnn.nnn.nnn.nnn
Explanation:
The IP address specified in the IPADDR parameter was not in the proper format nnn.nnn.nnn.nnn or
is not defined to your system.
●
PGTT1732E Invalid Knet Header received for IP nnn.nnn.nnn.nnn - header=xxxx
Explanation:
An invalid header xxxx was received from IP address nnn.nnn.nnn.nnn.
Recreate the problem with the Platform Server TCP/IP tracing activated (F
and contact TIBCO Technical Support.
●
servername,TCPTRON)
PGTT1733E Invalid IPV6 Address: mmmmmmmmmmmmmmmmmm
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
59
An invalid IPv6 address was entered. The reason that the address was invalid is displayed in this
message.
●
PGTT1734E Error INITALIZING SNMP TRAP feature - TRAP processing disabled
Explanation:
An error occurred when trying to perform the initialization that is required to send SMMP TRAPs.
TRAP processing will be disabled.
Review the preceding messages to determine the cause of the error. Message PGTV1710E will show
the error codes associated with this request.
●
PGTT1735E Error SENDING SNMP TRAP PDU - TRAP not sent
Explanation:
An error occurred when trying to send an SNMP TRAP. This SNMP TRAP was not sent. The
Platform Server will continue to send TRAP until 10 errors are received. At this point, no further
TRAP will be sent until the started task is restarted.
Review the preceding messages to determine the cause of the error. Message PGTV1710E will show
the error codes associated with this request.
●
PGTT1741E RADIUS DD not defined: Terminating RADIUS Server
Explanation:
You have configured the GLOBAL RADIUSIPPORT parameter, but not defined the RADIUS DD
statement. The RADIUS DD statement contains the Radius configuration parameters. Because this
file was not be found, the RADIUS server will be terminated.
●
PGTT1753E Node nnnnnnnn not found for TCPTRON command: Trace not activated
Explanation:
The TCPTRON command was entered to enable tracing for a particular node, but the node entered
was not enabled. Tracing will not be turned on for that node.
●
PGTT1754E Maximum number of Trace Entries(10) exceeded: Us e TCPTRDISP command to
view entries being traced
Explanation:
The TCPTRON operator command was entered to start a TCP trace for a particular node, IPv4 or IPv6
address. The maximum number of trace entries for a node or IP address is 10 and this maximum
was reached. Tracing is not turned on for this node or IP address.
●
PGTT1755E TCP Trace entry not found for: nnnnnnnnnn
Explanation:
The TCPTROFF command is entered to turn off tracing for a node or IP address. However tracing is
not turned on for that node or IP address. To turn tracing off for all IP addresses and nodes, enter
the TCPTROFF parameter without any sub-parameters.
●
PGTT1759E TCPTRAC DD MISSING: TRACE NOT ENABLED
Explanation:
When trying to turn on tracing through the TCPTRON operator command or through the TRACE batch
parameter, the TCPTRAC DD statement was not defined. Tracing is not enabled.
●
PGTT1764E TLS Hello Received for IP: nn.nn.nn.nn: TLS Tunnel request cannot
connect to non-Tunnel port
Explanation:
A TLS "Hello" request was detected on a non-TLS tunnel port. This message is displayed and the
connection request is terminated. The partner may receive a TLS connection failure message.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
60
●
PGTV1765E TLS TCP Error nn on rrrrrrr req: mmmmmmmmmmmmmm
Explanation:
A TLS error was detected while communicating with a transfer partner. nn defined the error code,
while rrrrrrrr defined the request that caused the error. The message text was displayed at the end of
this message.
●
PGTF2106E Command xxxx invalid or not supported - Command rejected
Explanation:
The command xxxx was incorrect and therefore not executed.
●
PGTF2107E KNETWORK Fusion Protocol Violation - command rejected
Explanation:
The command that was entered is incorrect and therefore not executed.
●
PGTF2108E KNETWORK Fusion Unable to process xxxx command - Queue slot not
available
Explanation:
The Fusion FTMS did not process command xxxx because no free slots were available on the work
queue.
If the problem persists, increase the WORKQ parameter in the FUSION procedure.
●
PGTF2109E KNETWORK Fusion File Open failed code=xxxx
Explanation:
The file failed to open. The return code xxxx indicated the system abend that occurred.
Check the log for error messages preceding this error and check the abend code in the IBM System
Codes manual.
●
PGTF2110E KNETWORK Fusion Record length xxxx exceeds maximum length of 32760
Explanation:
The record length of file xxxx exceeded a maximum length of 32760 that was set on the system.
●
PGTF2111E KNETWORK Fusion Invalid Record Blocking on receive data
Explanation:
This was an internal error. An invalid data block was received.
Recreate the problem with Fusion FTMS tracing activated (F
Technical Support.
●
servername,TRON)
and contact TIBCO
PGTF2112E KNETWORK Record length less than minimum allowed
Explanation:
The record length of the file was less than the minimum record length.
●
PGTF2113E KNETWORK Premature Deallocate received from partner xxxx
Explanation:
A request to deallocate a file was received prematurely from the partner xxxx.
Check the log on the partner for possible causes.
●
PGTF2114E KNETWORK Invalid response received from partner xxxx on yyyy packet
Explanation:
An invalid response was received from the partner xxxx to command yyyy.
Check the log on the partner for possible causes.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
61
●
PGTF2115E KNETWORK Unexpected Response packet received from node xxxx on Activity
yyyy
Explanation:
An invalid packet was received from node xxxx for activity yyyyy.
Check the logs on both systems. If the problem persists, recreate the problem with Fusion FTMS
tracing activated (F servername,TRON) and contact TIBCO Technical Support.
●
PGTF2116E KNETWORK Invalid AS400 file name xxxx on Activity yyyy
Explanation:
The file sent or received from AS/400 did not have a valid AS/400 file name.
●
PGTF2117E Activity xxxx Remote system yyyy exceeded retry limit - Request Purged
Explanation:
The transfer exceeded the number specified in the retry parameter and will now be purged.
●
PGTF2118E KNETWORK Fusion Record length xxxx exceeds maximum partner buffer size
of yyyy
Explanation:
The record length of the file was too large for the buffer.
●
PGTF2121E KN Fusion Response packet received - Code=xxxx Node yyyy - Error Data
Follows:
Explanation:
Error code xxxxxxxx occurred with node yyyy.
See the subsequent message for further details.
●
PGTF2122E KN Fusion Response packet received - Code=xxxx Node yyyy - Text
Follows:
Explanation:
An error was received from partner.
See message PGTF2123E for details.
●
PGTF2123E << error data received from partner >>
Explanation:
An error was received from partner.
●
PGTF2124E KN Fusion Response packet received - Code=xxxx Node yyyy - Message
Follows:
Explanation:
An error was received from partner. See message PGTF2123E for details.
●
PGTF2125E KN Fusion Response packet received - Code=xxxx Node yyyy - AS400 Data
Follows:
Explanation:
An error was received from partner. See message PGTF2123E for details.
●
PGTF2126E KN Fusion Response packet received - Code=xxxx Node yyyy - History Data
Follows:
Explanation:
An error was received from partner. See message PGTF2123E for details.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
62
●
PGTF2133E KNETWORK Fusion Record length xxxx exceeds AS400 fixed record size of
yyyy
Explanation:
The record length exceeded a maximum length that was set on the AS/400 system.
●
PGTF2134E Activity xxxx for Node yyyy restarting transfer on record zzzz
Explanation:
Activity xxxx for node yyyy was restarting with record zzzz.
●
PGTF2135E KNETWORK Fusion File Close failed code=xxxx
Explanation:
An error occurs when closing the file.
●
PGTF2136E FUSNETCR xxxx Error - yyyy
Explanation:
This is usually an error with the password. These errors might occur: invalid parameter passed,
invalid password crc found, null password not encrypted, null user ID found on request, null salt
found, or password not encrypted.
●
PGTF2137E Activity xxxx for Node yyyy purged due to Kill request
Explanation:
Activity xxxx for node yyyy will be deleted. No further action is required.
●
PGTF2138E Activity xxxx for Node yyyy Suspended due to operator request
Explanation:
Activity xxxx using node yyyy was suspended.
●
PGTF2139E Knetwork Fusion LZ78 Compressed data exceeds 64K bytes
Explanation:
Compression algorithm LZ78 was used with this transfer and the compressed data exceeded 64 KB.
●
PGTF2140E Knetwork Fusion LZ78 Decompressed data length exceeds Max Buffer size
of xxxx
Explanation:
Compression algorithm LZ78 was used with this transfer and the decompressed data exceeded the
buffer size of xxxx.
●
PGTF2141E Activity tttttttttt Remote node nnnnnnnn does not support data
encryption: Request terminated
Explanation:
A request was scheduled to node nnnnnnnn with data encryption specified. The remote node
nnnnnnnn did not support data encryption. As a result, the Platform Server terminates activity
tttttttttt. You can have the following two options:
●
●
Specify ENCRYPT=NO on the request to schedule the request without encryption.
●
Upgrade the remote node to a version that supports encryption.
PGTF2143E The Platform Server Manage request disallowed on xxx protocol for Node:
nnnnnnnn
Explanation:
This message indicates that protocol xxx was used when trying to initiate a transfer request. The
GLOBAL TRANSFER_INTERFACE_PROTOCOL parameter defines the protocols that are accepted when
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
63
initiating a transfer request. Supported protocols are TCP and SNA. By default, transfers can be
initiated by both TCP and SNA. This message is displayed when a request was initiated through a
protocol that was not supported by the global parameter.
●
PGTF2144EThe Platform Server Transfer request disallowed on xxx protocol for
Node: nnnnnnnn
Explanation:
Protocol xxx was used when trying to manage a transfer request. The GLOBAL
MANAGE_INTERFACE_PROTOCOL parameter defines the protocols that are accepted when managing a
transfer request. The supported protocols are TCP and SNA. By default, transfers can be managed
by both TCP and SNA. This message is displayed when a request was managed through a protocol
that was not supported by the global parameter.
●
PGTF2145E Transfer request rejected by GLOBAL ALLOW_TRANSFER_REQUESTS=NO:
nnnnnnnn
Explanation:
Protocol TCP or SNA was used to schedule a transfer request to the started task. The GLOBAL
ALLOW_TRANSFER_REQUESTS parameter was set to NO. This means that TCP and SNA transfer
schedule requests will not be supported. The transfer schedule request failed. For the transfer
schedule operation to succeed, you must do one of the following two options:
●
●
Schedule the transfer request using the SERVER parameter (cross memory).
●
Configure the GLOBAL and NODE GLOBAL ALLOW_TRANSFER_REQUESTS parameters to
support the transfer schedule request.
PGTF2146E Transfer request rejected by GLOBAL ALLOW_TRANSFER_REQUESTS Node not
found: nnnnnnn
Explanation:
Protocol TCP or SNA was used to schedule a transfer request to the started task. The GLOBAL
ALLOW_TRANSFER_REQUESTS parameter was set to NODE. This means that TCP and SNA transfer
schedule requests is supported only if the node was configured to accept it. However, the node was
not found for the incoming SNA or TCP request. The transfer schedule request failed.
For the transfer schedule operation to succeed, do one of the following options:
●
●
Schedule the transfer request using the SERVER parameter (cross memory).
●
Configure a node definition that matches the incoming transfer schedule request.
PGTF2147E Transfer request rejected by NODE ALLOW_TRANSFER_REQUESTS=NO: nnnnnnnn
Explanation:
Protocol TCP or SNA was used to schedule a transfer request to the started task. The GLOBAL
parameter was set to NODE. This means that TCP and SNA transfer
schedule requests will be accepted only if the node was configured to support it. The node defined
for the incoming SNA or TCP request denied the request. The transfer schedule request failed. For
the transfer schedule operation to succeed, you must do one of the following options:
ALLOW_TRANSFER_REQUESTS
●
●
Schedule the transfer request using the SERVER parameter (cross memory).
●
Configure a node definition to support transfer schedule requests.
PGTF2148E Transfer request rejected by NODE ALLOW_TRANSFER_REQUESTS - Credentials
required: nnnnnnnn
Explanation:
Protocol TCP or SNA was used to schedule a transfer request to the started task. The GLOBAL
ALLOW_TRANSFER_REQUESTS parameter is set to NODE. This means that TCP and SNA transfer
schedule requests is accepted only if the node was configured to support it. The node defined for the
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
64
incoming SNA or TCP request requires credentials, but the transfer request did not provide local
credentials. The transfer schedule request failed.
For the transfer schedule operation to succeed, do one of the following options:
●
●
Schedule the transfer request using the SERVER parameter (cross memory).
●
Configure a node definition to support transfer schedule requests without requiring credentials.
●
Include local credentials in the transfer schedule request.
PGTF2149E Manage request rejected by GLOBAL ALLOW_MANAGE_REQUESTS=NO: nnnnnnnn
Explanation:
Protocol TCP or SNA was used to manage transfers. The GLOBAL ALLOW_MANAGE_REQUESTS
parameter was set to NO. This means that TCP and SNA manage requests will not be accepted. The
manage request failed. For the manage operation to succeed, you must do one of the following
options:
●
●
Manage the request using the SERVER parameter (cross memory).
●
Configure the GLOBAL and NODE GLOBAL ALLOW_MANAGE_REQUESTS parameters to support
the manage request.
PGTF2150E Manage request rejected by GLOBAL ALLOW_MANAGE_REQUESTS Node not found:
nnnnnnnn
Explanation:
Protocol TCP or SNA was used to manage transfers. The GLOBAL ALLOW_MANAGE_REQUESTS
parameter was set to NODE. This means that TCP and SNA manage requests will be accepted only if
the node was configured to accept it. However, the node was not found for the incoming SNA or
TCP request. The manage request failed.
For the manage operation to succeed, do one of the following options:
●
●
Manage the transfer using the SERVER parameter (cross memory).
●
Configure a node definition that matches the incoming manage request.
PGTF2151E Manage request rejected by NODE ALLOW_MANAGE_REQUESTS=NO: nnnnnnnn
Explanation:
Protocol TCP or SNA was used to manage transfers. The GLOBAL ALLOW_MANAGE_REQUESTS
parameter was set to NODE. This means that TCP and SNA manage requests will be accepted only if
the node was configured to support it. However, the node defined for the incoming SNA or TCP
request denied the request. The manage request failed. For the manage operation to succeed, you
must do one of the following options:
●
●
Manage the transfer using the SERVER parameter (cross memory).
●
Configure a node definition to support manage schedule requests.
PGTF2152E Manage request rejected by NODE ALLOW_MANAGE_REQUESTS - Credentials
required: nnnnnnnn
Explanation:
Protocol TCP or SNA was used to manage transfers. The GLOBAL ALLOW_MANAGE_REQUESTS
parameter was set to NODE. This means that TCP and SNA manage requests will be accepted only if
the node was configured to support it. The node defined for the incoming SNA or TCP request
required credentials, but the manage request did not provide local credentials. The manage request
failed.
For the manage operation to succeed, do one of the following options:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
65
●
●
Manage the transfer using the SERVER parameter (cross memory).
●
Configure a node definition to support manage schedule requests without requiring credentials.
PGTF2153E Transfer request received from Node nnnnnnnn: Transfer User tttttttt
does not match RACF Token user
Explanation:
A transfer request was received from node nnnnnnnn. The token was validated, but the user on the
RACF token did not match the user defined for the transfer. The transfer request was terminated
with an error and was not logged to the audit file.
●
PGTF2154E Error received on RACF TOKENMAP: SAF RC =xx RETCODE=yy REASON=zz
Explanation:
A transfer request was received from node nnnnnnnn. While validating the token, a RACF error was
detected on the RACF TOKENMAP request. This message displayed the SAF return code, the RACF
return code and reason code. The transfer request was terminated with an error and was not logged
to the audit file.
●
PGTE2200E ISPF function failed due to Network error
Explanation:
The Platform Server ISPF interface received a network error when it attempted to communicate with
the Platform Server started task. Message 1710(for TCP) or message 1619(VTAM) will provide an
explanation of the error.
●
PGTE2201E ISPF function failed due to PCCALL error
Explanation:
The Platform Server ISPF interface received an error while performing a cross memory request to
the Platform Server started task. The ISPF request was terminated.
●
PGTE2202E Network error received - Error code=xxxx
Explanation:
The Platform Server ISPF interface received a network error when trying to communicate with the
Platform Server started task. Message 1710(for TCP) or message 1619(VTAM) will provide an
explanation of the error.
●
PGTE2203E Token create failed with return code xx - MWAIT - option ignored
Explanation:
The Platform Server REXX interface tried to create a token using the z/OS token services, but failed
with the return code xx.
Contact TIBCO Technical Support for assistance if this problem persists.
●
PGTE2204E TRANSNUM count is zero on FUSWAIT - Wait terminated
Explanation:
The FUSWAIT command was issued by a REXX user, but no requests were in the wait queue for this
address space. The wait command was terminated and control was passed back to the REXX exec.
●
PGTE2205E No transfers Queued with MWAIT option since the step started - MWAIT
terminated
Explanation:
The FUSWAIT command was issued by a REXX user, but no requests were put in the wait queue
since this address space was started. The wait command was terminated and control was passed
back to the REXX exec.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
66
●
PGTE2206E FUSWCLR failed - no transfers have been queued with MWAIT since the
step started
Explanation:
The FUSWCLR command was issued by a REXX user to clear the request queue, but no requests were
put on the wait queue since this address space was started. The command was terminated and
control was passed back to the REXX exec.
●
PGTE2207E FUSWCLR Delete failed with return code xx
Explanation:
The FUSWCLR command was issued by a REXX user to clear the request queue, but the token
DELETE failed with a return code of xx. The command was terminated and control was passed back
to the REXX exec.
●
PGTE2208E Platform Server WAIT received return code xx from Platform Server
started task
Explanation:
The WAIT command was specified by a REXX exec on a fusion transfer request. The WAIT command
was completed, and the REXX exec received return code xx from the started task.
●
PGTE2209E Error loading Token Service module IEANTxx - MWAIT not supported
Explanation:
The Platform Server REXX interface tried to load the Token Services module, but received an error.
The MWAIT request was ignored. This can be caused by an old release of MVS, or by the Token
Services modules not being located in the LINKLST.
●
PGTE2210E Platform Server MWAIT count exceeds maximum wait count of 40 - MWAIT
ignored
Explanation:
The Platform Server REXX MWAIT parameter accepteda maximum of 40 requests to be queued before
the FUSWAIT exec was executed. In this case 40 requests were queued, and another request was
initiated before the FUSWAIT exec was executed.
●
PGTE2211E DYNALLOC FREE failed for ddname dddddddd R15=xx ERROR=yy INFO=zz
Explanation:
The Platform Server REXX exec tried to free ddname dddddddd, but received an error. The errors are
documented in the z/OS Authorized Assembler Service Reference manual.
●
PGTE2213E Invalid REXX command: xxxxxxxxxx Command must be between 1 and 8 bytes
Explanation:
The Platform Server started task was trying to execute a REXX exec from within the Platform Server
address space, and the REXX command name was not between 1 and 8 characters.
Review the REXX command specified and make sure that it is between 1 and 8 characters long.
●
PGTE2214E Error loading module IRXEXEC - command execution terminated
Explanation:
A LOAD request was issued from the started task for the IRXEXEC REXX interface module, but the
module did not load successfully. MVS messages will accompany this message to indicate a reason
for the load failure.
●
PGTE2215E DD SYSEXEC required but not found - command execution terminated
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
67
The SYSEXEC DD statement was required to run a REXX exec from within the Platform Server
address space, but it was not entered.
Add SYSEXEC to the Platform Server JCL. Additionally, make sure that the SYSEXEC DD statement
contains all of the execs that will be run by the Platform Server started task.
●
PGTE2216E DD SYSTSPRT required but not found - command execution terminated
Explanation:
The SYSPRINT DD statement was required to run a REXX exec from within the Platform Server
address space, but it was not entered.
Add SYSPRINT to the Platform Server JCL.
●
PGTE2218E RACROUTE ACEE Create failed - SAF code: xx Return: yy Reason: zz
Explanation:
The Platform Server tried to create an ACEE so that the REXX exec could run with the proper
security authorization, but the request failed with the return codes listed. Contact TIBCO Technical
Support if this problem reoccurs.
●
PGTE2219E Userid uuuuuuuu not defined to SAF: REXX EXEC terminated
Explanation:
The Platform Server tried to run a REXX exec from within the Platform Server address space, and
attempted to create an ACEE for user ID uuuuuuuu, but the user was not defined to the security
system. The request was terminated with an error.
●
PGTE2220E Userid invalid or not defined: REXX EXEC terminated
Explanation:
The Platform Server tried to run a REXX exec from within the Platform Server address space and
attempted to create an ACEE for the user ID, but the user was not defined (such as spaces or nulls)
or not defined to the security system. The request was terminated with an error.
●
PGTE2224E Open for DD SYSEXEC failed - REXX exec terminated
Explanation:
The Platform Server tried to run a REXX exec from within the Platform Server address space but
was unable to open the SYSEXEC DD statement.
Make sure that the SYSEXEC DD statement is defined in the MFT started task JCL and that the MFT
started task is authorized to read this dataset.
●
PGTE2225E Config member FUSCFG not found in SYSEXEC - REXX exec terminated
Explanation:
The Platform Server REXX interface tries to schedule a request, but the configuration member
is not found in the SYSLIB. The Platform Server requires this member to define the criteria
used to communicate with the Platform Server started task.
FUSCFG
●
PGTE2226E Invalid data found reading FUSCFG record nnn Data: dddddddddddd
Explanation:
An error was detected by the REXX interface program on record nnn of the FUSCFG member. The
invalid data (dddddddddddd) was displayed in this message.
Correct the error and retry the REXX exec.
●
PGTE2227E Config cccccccc not found in FUSCFG member: REXX exec terminated
Explanation:
A REXX interface was executed and the CFG parameter (or defaulted it to DEFAULT) was specified,
but the configuration entry was not found in the FUSCFG member.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
68
Make sure that the entry specified by the CFG parameter is correct, and add the entry to the FUSCFG
member.
●
PGTE2228E IPPORT not 5 numeric characters - Record: nnn
Explanation:
The IPPORT parameter was specified in the FUSCFG member, but the IPPORT parameter was not
defined as 5 numeric characters. nnn showed the relative record number in the FUSCFG member that
is in error.
Specify ports less than 10000 with leading zeroes so that the IP port is exactly 5 numeric characters.
●
PGTE2229E IPADDR: iii.iii.iii.iii not in dotted decimal notation - record: nnn
Explanation:
The IPADDR parameter was specified in the FUSCFG member, but the IPADDR parameter was not in
the correct format for an IP address. The IP address must be specified in dotted decimal notation
such as 192.24.152.1. iii.iii.iii.iii showed the IP address in error. nnn showed the relative record
number in the FUSCFG member that was in error.
●
PGTE2230E STCNAME/IPADDR/IPNAME/LUNAME not defined for config cccccccc
Explanation:
A CFG entry that pointed to entry cccccccc in the FUSCFG member was specified. That member did
not specify any of these parameters: STCNAME, IPNAME, IPADDR, or LUNAME. One of these parameters
is required in each FUSCFG entry.
Correct the FUSCFG entry to specify one of these parameters and retry the request.
●
PGTE2231E Required field ffffffff missing from config cccccccc
Explanation:
A CFG entry that pointed to entry cccccccc in the FUSCFG member was specified. Required field ffffffff
was missing from that entry.
Add required field ffffffff to entry cccccccc in FUSCFG and retry the request.
●
PGTE2232E DYNALLOC failed for DSN ddddddd R15=xx ERROR=yy INFO=zz
Explanation:
The Platform Server REXX interface tried to allocate the Platform Server audit files, but received a
dynamic allocation error. The data set that was being allocated was dddddddd. The errors are
documented in the z/OS Authorized Assembler Service Reference manual.
●
PGTE2233E Unable to allocate AUDPATH dsn dddddddd: Dataset not found
Explanation:
The Platform Server REXX interface tried to allocate the Platform Server audit data set dddddddd.
Dynamic allocation could not find the data set. Check the entry in the FUSCFG file to make sure that
the AUDPATH1 and AUDPATH2 statements are defined correctly.
●
PGTE2234E Unable to allocate AUDPATH dsn dddddddd: dd xxxxxxxx already allocated
Explanation:
The Platform Server REXX interface tried to allocate the Platform Server audit data set dddddddd for
ddname xxxxxxxx, but dynamic allocation indicated that the ddname was already allocated. The
Platform Server will continue and use the data set currently allocated. This message is for
informational purposes only.
●
PGTE2235E FUSREXXM open failed for ddname FUSPDS01
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
69
The Platform Server REXX interface tried to open ddname FUSPDS01 to read the directory of a PDS
and get a list of members in that PDS. The open operation failed. Other messages displayed
preceding this message will indicate the reason for the error.
●
PGTE2236E FUSREXXM member count exceeds 1000 members - request terminated
Explanation:
The Platform Server REXX interface tried to read the directory of a PDS and found that more than
1000 members were in the PDS directory. FUSSMEM has a limit that it can process no more than 1000
members from a single PDS file. The request was terminated.
●
PGTE2237E Unable to allocate FUSPDS01 dsn dddddddd: Dataset not found
Explanation:
The Platform Server REXX interface tried to allocate the Platform Server data set dddddddd, but
dynamic allocation indicated that the file was not found. Check theLFILE parameter on the FUSSMEM
exec to make sure that the local data set name was correct.
●
PGTE2238E Unable to allocate FUSPDS01 dsn dddddddd: dd xxxxxxxx already allocated
Explanation:
The Platform Server REXX interface tried to allocate the Platform Server data set dddddddd for
ddname xxxxxxxx, but dynamic allocation indicated that the file was already allocated. The Platform
Server continues and uses the data set currently allocated. This message is for informational
purposes only.
●
PGTE2239E LFILE requested: dddddddd is not a PDS - cannot get member list
Explanation:
The file dddddddd was specified in the FUSSMEM REXX exec, but that file was not a PDS. Only PDS
files can be specified on the FUSSMEM exec.
●
PGTE2241E uuuuuuuu Surrogate logon for vvvvvvvv failed R15/R0=rr ss:
tttttttttttttttttttttttt
Explanation:
The LUSER parameter was entered without the LPASS parameter. This is called a surrogate logon,
and the Platform Server checked the RACF/ACF2/TOPS SURROGAT class to make sure that user
uuuuuuuu was authorized to submit a job on behalf of user vvvvvvvv. The return codes (rr ss) and a
text description of the error was also displayed. The transfer terminated with errors.
If necessary, enter the LUSER and LPASS parameters so that surrogate checking is not performed, or
make the necessary security system changes to support surrogate job submission.
●
PGTB2242E User not Authorized to use Platform Server: Request terminated due to
ENFORCE mode
Explanation:
The Platform Server was defined to restrict its usage to a limited group of users. The user that
submitted the file transfer request was not authorized to use the Platform Server. The Platform
Server GLOBAL EXTENDED_SECURITY_RESOURCE parameter was set to ENFORCE. Therefore, the file
transfer was terminated with errors.
●
PGTB2244E User not Authorized to use Node xxxxxxxx: Request terminated due to
ENFORCE mode
Explanation:
The Platform Server was defined to restrict the usage of the Platform Server nodes to a limited
group of users. The user that submitted the file transfer request was not authorized to use the
Platform Server node xxxxxxxx. The second parameter of the Platform Server GLOBAL
EXTENDED_SECURITY_RESOURCE parameter was set to ENFORCE. Therefore, the file transfer was
terminated with errors.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
70
●
PGTB2246E RACF TOKENXTR failed: SAFRC=@1 RC=@2 REA=@3: Request submitted without
TOKEN
Explanation:
A batch job or TSO task executed the RACF TOKENXTR command, but the request failed. This
message displayed the SAF return code, the RACF return code, and the RACF reason code. The
request was submitted without the RACF token. Depending on the way the MFT server is
configured, the request might fail if tokens are required by the node submitting the transfer.
●
PGTS2246E ssssssss uuuuuuuu failed R15/R0=04 04: mmmmmmmmmmmmmmmmmmmm
Explanation:
At the start of a transfer, MFT executed a RACF call but received an error. ssssssss is a text message
that indicates the type of call. uuuuuuuu defines the user ID associated with the request while
mmmmmmmmm is a text explanation of the type of error that occurred.
Typically two types of errors could occur: surrogate logon and authorization check errors. Most
surrogate logon errors occur because the user does not have the RACF authority to impersonate
another user. Authorization check errors occur typically because the user does not have
authorization to a RACF facility class defined to the Platform Server. Surrogate logon errors cause
the transfer to fail. Authorization check errors cause the transfer to fail if MFT extended resource
checking is in fail mode, but transfers continue if MFT extended resource checking is in warn mode.
●
PGTS2270E GENCB for FUSMSG ACB Failed R15=xx R0=yy
Explanation:
The Platform Server message inquiry program tried to issue a GENCB command to create control
blocks required to read the FUSMSG VSAM file and received an error. xx contained the low order byte
of R15, while yy contained the low order byte of R0.
If this error persists, contact TIBCO Technical Support. The FUSMSG request is terminated when
this message is received.
●
PGTS2271E GENCB for FUSMSG RPL Failed R15=xx R0=yy
Explanation:
The Platform Server message inquiry program tried to issue a GENCB command to create control
blocks required to read the FUSMSG VSAM file but received an error. xx contained the low order byte
of R15, while yy contained the low order byte of R0.
If this error persists, contact TIBCO Technical Support. The FUSMSG request is terminated when
this message is received.
●
PGTS2272E OPEN for FUSMSG ACB Failed R15=xx ERFLG=yy
Explanation:
The Platform Server message inquiry program tried to open the FUSMSG VSAM file but received an
error. xx contained the low order byte of R15, while yy contained the contents of the ACBERFLG field.
These error codes can be found in this IBM manual: DFSMS/MVS macro Instructions for Data Sets.
●
PGTS2273E Get for FUSMSG File Failed R15=xx RTNCD=yy
Explanation:
The Platform Server message inquiry program tried to read a record from the FUSMSG VSAM file
using the VSAM GET macro, but received an error. xx contained the low order byte of R15, while yy
contained the contents of the RPLERRCD field. These error codes can be found in this IBM manual:
DFSMS/MVS macro Instructions for Data Sets.
●
PGTS2274E Point for FUSMSG File Failed R15=xx RTNCD=yy
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
71
The Platform Server message inquiry program tried to position itself to a record in the FUSMSG
VSAM file using the VSAM POINT macro, but received an error. xx contained the low order byte of
R15, while yy contained the contents of the RPLERRCD field. These error codes can be found in the
IBM manual: DFSMS/MVS macro Instructions for Data Sets.
●
PGTS2275E CLOSE for FUSMSG ACB Failed R15=xx ERFLG=yy
Explanation:
The Platform Server message inquiry program tried to close the FUSMSG VSAM file, but received an
error. xx contained the low order byte of R15, while yy contained the contents of the ACBERFLG field.
These error codes can be found in the IBM manual: DFSMS/MVS macro Instructions for Data Sets.
●
PGTE2315E General Registers at time of error
Explanation:
The general registers will follow this message.
●
PGTE2316E Access Registers at time of error
Explanation:
The access registers will follow this message.
●
PGTE2317E Rx:XXXXXXXX Rx:XXXXXXXX Rx:XXXXXXXX Rx:XXXXXXXX
Explanation:
This message will contain the registers at the time of abend in the user exit.
●
PGTS2400E CCC xxxxx request failed: Global CCC_ADMIN_FACILITY parameter not
defined
Explanation:
A Platform Server Command Center request was received from a remote node. The request was
denied because of the security validation. The field xxxxx defines the type of authorization that is
requested. The GLOBAL CCC_ADMIN_FACILITY parameter is not defined. Requests will not be given
authorization unless this parameter was defined.
®
See the GLOBAL CCC_xxxxx_FACILITY parameters in TIBCO Managed File Transfer Platform Server
for z/OS Installation and Operations for more information about the changes that must be made.
●
PGTS2401E CCC Select Unknown Error=xxxxxxxxxx
Explanation:
The Platform Server Command Center (CCC) tried to process a REFRESH or ALTER request, but the
error code returned by the Platform Server was unknown. The error code (xxxxxxxx) was displayed.
The request was denied, and a return code was returned indicating the cause of the failure.
If this message persists, contact TIBCO Technical Support.
●
PGTS2402E CCC xxxxx request denied by Security Validation: ttttttttttttttttttttt
Explanation:
A Platform Server Command Center request was received from a remote node. The request was
denied because of the security validation. The field xxxxx defined the type of authorization that was
requested.
Use the RACF PERMIT command to authorize a user for the required function. Descriptive text about
the cause of the failure was displayed at the end of the message.
●
PGTS2403E The Platform Server Node LIST Failed - Node Name not found:
Node=nnnnnnnn: Request Terminated
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
72
A Platform Server Command Center NODE LIST request was received, but node nnnnnnnn was not
enabled. The node must be enabled before it can be listed.
●
PGTS2406E The Platform Server Profile xxxxxxxx request failed: RC=nn
Explanation:
A Platform Server Command Center PROFILE request was received. The request failed with return
code nn.
Look for other messages describing the cause of the failure.
●
PGTS2407E The Platform Server User=uuuuuuuu Not Authorized to Add Profile for
LocalUser=uuuuuuuu
Explanation:
A Platform Server Command Center PROFILE ADD request was received from user uuuuuuuu.
User uuuuuuuu tried to add a PROFILE for local user llllllll but was not authorized to add profile
requests for other users.
If you want user uuuuuuuu to add profile requests for other users, define the RACF CONTROL
access to the RACF facility by the GLOBAL BOSSID parameter.
●
PGTS2408E The Platform Server User=uuuuuuuu Not Authorized to Delete Profile for
LocalUser=uuuuuuuu
Explanation:
A Platform Server Command Center PROFILE DELETE request was received from user uuuuuuuu.
User uuuuuuuu tried to delete a PROFILE for local user llllllll but was not authorized to delete
profile requests for other users.
If you want user uuuuuuuu to delete profile requests for other users, define RACF CONTROL access
to the RACF facility by the GLOBAL BOSSID parameter.
●
PGTS2409E The Platform Server Required Transfer field missing: xxxxxxxxx
Explanation:
A Platform Server Command Center TRANSFER request was received, but a required field was
missing. Field xxxxxxxx was required to execute a TRANSFER request but that field was missing.
The transfer request was terminated with errors.
Fill in the missing field and retry the request.
●
PGTS2410E The Platform Server Transfer field value invalid: xxxxxxxx
Explanation:
A Platform Server Command Center TRANSFER request was received but a field was defined with
an invalid value. The value for field xxxxxxxx was invalid. The transfer request was terminated with
errors.
Correct the field value and retry the request.
●
PGTS2411E The Platform Server OPER DataFlow internal error: xxxxxxxxxxxxxxxx
Explanation:
A Platform Server Command Center request is received, but the Platform Server detects an internal
error. If this request can be reproduced, perform a Platform Server trace, retry the request and send
the trace to TIBCO Technical Support.
●
PGTS2412E The facility class specified in the GLOBAL BOSSID(bbbbbbbb) is not
defined: Request terminated
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
73
A Platform Server Command Center PROFILE request was received. The Platform Server tried to
check the GLOBAL BOSSID facility class to see if the request was allowed, but the facility class
(bbbbbbbb) was not defined to RACF. The Platform Server rejected the request.
●
PGTS2413E LocalUser(uuuuuuuu) cannot be used unless it has CONTROL auth to Global
BOSSID(bbbbbbbb)
Explanation:
A Platform Server Command Center PROFILE ADD request is received. The Command Center user
tries to add a PROFILE for local user uuuuuuuu, but is not authorized to add profile requests for
other users. If you want to add profile requests for other users, the Command Center user must
have RACF CONTROL access to the RACF facility defined by the GLOBAL BOSSID parameter. The
Platform Server rejects the request.
●
PGTS2415E The Platform Server Node field ffffffff missing or invalid: Node
nnnnnnnn not enabled
Explanation:
A Platform Server Command Center NODE ADD request was received, but a field was not defined,
or defined with an invalid value. The value for field xxxxxxxx was invalid. Node nnnnnnnn was not
enabled.
Correct the request and resubmit the request.
●
PGTS2416E Open failed for CONFIG dd: Node request terminated
Explanation:
A Platform Server Command Center NODE ADD request was received. The Platform Server tried to
open the CONFIG DD statement, but the OPEN request failed. This was most likely because the
Command Center user was not authorized to access the CONFIG DD statement. The node is not
enabled. The Command Center user who made the request must be given Update authorization for
the DSN defined by the CONFIG DD statement.
●
PGTS2417E Abend aaa received opening CONFIG DD for Output: Node request
terminated
Explanation:
A Platform Server Command Center NODE ADD request was received. The Platform Server tried to
open the CONFIG DD statement, but received abend code aaa. This was most likely because the
Command Center user was not authorized to access the CONFIG DD statement. The node is not
enabled. The Command Center user who made the request must be given Update authorization for
the DSN defined by the CONFIG DD statement.
●
PGTS2418E Write failed for CONFIG DD member mmmmmmmm: Abend Code=aaa: Node
request terminated
Explanation:
A Platform Server Command Center NODE ADD request is received. The Platform Server tries to
write a record to the CONFIG DD statement, but receives abend code aaa. This is most likely
because the PDS defined by the CONFIG DD ran out of space. Look up abend code aaa in the IBM
z/OS DFSMS Macro Instructions for Data Sets manual. The node is not enabled.
●
PGTS2419E STOW REPLACE Failed for Node member mmmmmmmm: R15=xx R0=yy: Node
Request terminated
Explanation:
A Platform Server Command Center NODE ADD request was received. The Platform Server issued
a STOW macro to write a directory entry to the CONFIG DD statement, but the STOW was
terminated with an error. R15 and R0 contain the error codes. This is most likely because the PDS
defined by the CONFIG DSN ran out of space in the directory. The node is not enabled.
Look up the STOW R15/R0 codes in the IBM z/OS DFSMS Macro Instructions for Data Sets manual.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
74
●
PGTS2421E STOW DELETE failed for Node member mmmmmmmm: R15=xx R0=yy: Node Request
terminated
Explanation:
A Platform Server Command Center NODE DELETE request was received. The Platform Server
issued a STOW macro to delete a directory entry to the CONFIG DD statement, but the STOW was
terminated with an error. R15 and R0 contain the error codes. The node is not deleted.
See the STOW R15/R0 codes in the IBM z/OS DFSMS Macro Instructions for Data Sets manual.
●
PGTS2422E The Platform Server Node DELETE Failed - Node Name not found:
Node=nnnnnnnn
Explanation:
A Platform Server Command Center NODE DELETE request was received for node nnnnnnnn, but
the node was not enabled. Only nodes that are enabled can be deleted. The request failed.
●
PGTS2423E The Platform Server xxxxx function Failed - Node nnnnnnnn not defined
with xxxxxxxx support
Explanation:
A Command Center user issued a Platform Server request xxxxx. The function failed because the
node that initiated the request (nnnnnnnn) was not defined with
COMMAND_CENTER_SUPPORT=xxxxxxx.
For node nnnnnnnn to perform this function, update the node COMMAND_CENTER_SUPPORT parameter
to add the necessary value.
●
PGTS2424E The Platform Server xxxxx function Failed - Node not defined for IPAddr
nnn.nnn.nnn.nnn
Explanation:
A Command Center user issued a Platform Server request xxxxx. The function failed because the IP
address (nnn.nnn.nnn.nnn) that initiated the request was not defined as a node entry.
For node nnnnnnnn to perform this function, add a node definition for this IP address that includes
the node COMMAND_CENTER_SUPPORT parameter.
●
PGTS2425E CCC xxxxx request failed: GLOBAL CCC_ADMIN_FACILITY=yyyyyyyy not
defined to RACF
Explanation:
A Command Center user issued the Platform Server request xxxxx. The function failed because the
GLOBAL CCC_ADMIN_FACILITY parameter was not defined.
Define the parameter for the function (xxxxx) to work because the Platform Server will check this
RACF facility resource to make sure that the user is authorized to perform this function. Perform the
following steps:
1. Define the GLOBAL CCC_ADMIN_FACILITY parameter.
2. Define the RACF facility class defined by the GLOBAL CCC_ADMIN_FACILITY parameter.
3. Give the necessary users access to CCC_ADMIN_FACILITY through the RACF PERMIT command.
4. Stop and start the Platform Server started task.
●
PGTS2427E CCC rrrrrrrr request failed - nnnnnnnn exceeds maximum length of nn
characters
Explanation:
The Platform Server Command Center initiated a request to z/OS to perform request rrrrrrr. The
request failed because the parameter defined as nnnnnnn exceeded the maximum length. The
request was terminated with an error.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
75
●
PGTS2429E CCC rrrrrrrr request failed - xxxxxxxx must be from 1 to 32 characters
and cannot have imbedded spaces
Explanation:
The Platform Server Command Center initiated a request to z/OS to perform request rrrrrrr. The
request failed because the parameter defined as xxxxxxxx was invalid. This parameter must be
between 1 and 32 characters and cannot have embedded spaces. The request was terminated with
an error.
●
PGTS2430E STOW Append Failed for Node member nnnnnnnn: R15=nn R0=nn: Node Request
terminated
Explanation:
The Platform Server Command Center tried to add a new node definition to the Platform Server, but
received an error when issuing the z/OS STOW macro. The member name to be added was
nnnnnnnn. The request was terminated with an error.
See the error codes defined by the R15 and R0 fields in the IBM manual DFSMS Macros for Datasets.
●
PGTS2451E FUSPING Invalid Data received: @1 : Expecting Negotiation record
Explanation:
The Platform Server CFPING command was executed, but invalid data was received from the
conversation partner.
If this message persists, take a trace of the Platform Server CFPING request and send it to TIBCO
Technical Support. Note that the CFPING functionality is supported only for version 6.0 or higher.
●
PGTS2452E FUSPING FMH7 received from partner
Explanation:
The Platform Server CFPING command was issued, but FMH7 was received from the conversation
partner. This message typically means that the Platform Server system did not support the CFPING
functionality. Note that the CFPING functionality is supported only for the version 6.0 or higher.
●
PGTS2453E FUSPING Error processing PARM parameter: Request terminated
Explanation:
The Platform Server CFPING command was executed, but the PARM parameter was entered
incorrectly. This message is typically displayed with other messages that describe the cause of the
problem. The CFPING request failed.
●
PGTS2454E FUSPING xxxxxxxx parameter yyyyyyyy exceeds max length of 64 characters
Explanation:
The Platform Server CFPING command was executed, but one of the parameters was incorrect.
Parameter xxxxxxxx exceeded the maximum length of 64 characters. The value yyyyyyyy defined
whether the field was detected on PARM of SYSIN DD statement. The CFPING request failed.
●
PGTS2455E FUSPING Error processing SYSIN parameter: Request terminated
Explanation:
The Platform Server CFPING command was executed, but one of the SYSIN parameters was
incorrect. This message is typically displayed with other messages that describe the cause of the
problem. The CFPING request failed.
●
PGTS2456E FUSPING Invalid value supplied for parameter: xxxxxxxx
Explanation:
The Platform Server CFPING command was executed, but an invalid value was specified for
parameter xxxxxxxx. The CFPING request failed.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
76
Correct the parameter and resubmit the request.
●
PGTS2457E FUSPING Open failed for xxxxxxxx dd: Request terminated
Explanation:
The Platform Server CFPING command was executed, but the OPEN operation failed for DD
statement xxxxxxxx. The CFPING request failed.
●
PGTS2458E FUSPING Invalid parameter defined: xxxxxxxx: Request terminated
Explanation:
The Platform Server CFPING command was executed, but an invalid parameter (xxxxxxxx) was
specified. The CFPING request failed.
Correct the parameter and resubmit the request.
●
PGTS2461E FUSPING Protocol Error: xxxxxxxx: Request terminated
Explanation:
A Platform Server CFPING request was executed, but the Platform Server detected an internal error.
If this request can be reproduced, perform a Platform Server trace, retry the request and send the
trace to TIBCO Technical Support.
●
PGTS2462E FUSPING Packet nnnn: Length mismatch: Out=xxxx In=yyyy
Explanation:
A Platform Server CFPING DATA request was executed. The Platform Server sent a packet to the
remote system and expected the identical packet to be transmitted back by the remote system.
However, the Platform Server detected that the length of the packet sent back by the remote system
(yyyy) did not match the length of the packet originally sent (xxxx). Value nnnn defined the packet
number where the error was detected.
●
PGTS2463E 'FUSPING Packet nnnn: Data does not match'
Explanation:
A Platform Server CFPING DATA request was executed. The Platform Server sent a packet to the
remote system and expected the identical packet to be transmitted back by the remote system.
However, the Platform Server detected that the packet sent back by the remote system did not
match the packet originally sent. Value nnnn defined the packet number where the error was
detected.
●
PGTS2464E FUSPING Network error: Request terminated
Explanation:
A Platform Server CFPING request was executed. The Platform Server initiated a TCP connection to
the remote Platform Server system but a network error was detected. The following reasons might
cause this error:
●
●
The IP name or IP address defined was incorrect.
●
The Platform Server is not listening on the IP port that was defined.
●
The remote Platform Server system that supported the CFPING command was not later than
version 6.0.
PGTS2465E FUSPING to Host nnn.nnn.nnn.nnn failed - RC=nn: Message follows
Explanation:
The FUSPING program was executed, and an error message was received from the partner. Typically
this means that the partner was not authorized to execute the function or an early version of the
Platform Server software that did not support the FUSPING functionality was running on the remote
system. An additional message will show more detail about the error.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
77
●
PGTE2601E Platform Server DNI not started due to errors
Explanation:
A valid GLOBAL DNI key was specified, but DNI was not started because of errors. Typically this is
because there was a problem when creating the DNIACT data space or accessing the DNICFG
configuration file. Other messages accompanying this message will give additional information
about the error that caused the problem.
●
PGTE2602E Platform Server DNI Requires DFSMS V1.3 or higher: DNI not started
Explanation:
A valid GLOBAL DNI key was specified, but DNI was not started because the DFSMS version was
not supported. The Platform Server DNI required at least version 1.3 or later of DFSMS.
●
PGTE2603E Platform Server DNI Requires member name on cccccccc command: not
entered
Explanation:
The Platform Server DNI operator command cccccccc was executed, but the required member
name was not entered.
Re-enter the command with the member name.
●
PGTE2604E DNI FAIL_ACTION invalid: no postprocessing performed - DNIACT record
deleted
Explanation:
An invalid FAIL_ACTION parameter in the DNICFG entry was specified. At post processing time,
this message was displayed to indicate that no post processing could be performed. The DNIACT
entry was deleted without any post-processing.
Correct the DNICFG entry to specify the correct post processing FAIL_ACTION parameter.
●
PGTE2605E DNI FAIL about to rename DSN dddddddd to nnnnnnnn
Explanation:
A DNI request was completed unsuccessfully, and DNI was about to rename a data set from
ddddddd to nnnnnnnn. This was because the FAIL_ACTION parameter was specified as RENAME. This
message is for informational purposes only.
●
PGTE2606E DNI FAIL about to delete DSN dddddddd
Explanation:
A DNI requestwas completed unsuccessfully, and DNI was about to delete data set ddddddd. This
was because the FAIL_ACTION parameter was specified as DELETE. This message is for informational
purposes only.
●
PGTE2607E DNI GOOD_ACTION invalid: no postprocessing performed - DNIACT record
deleted
Explanation:
An invalid GOOD_ACTION parameter was specified in the DNICFG entry. At post processing time,
this message was displayed to indicate that no post processing could be performed. The DNIACT
entry was deleted without any post processing.
Correct the DNICFG entry to specify the correct post processing GOOD_ACTION parameter.
●
PGTE2608E DNI GOOD about to rename DSN dddddddd to nnnnnnnn
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
78
A DNI request was completed successfully, and DNI was about to rename a data set from ddddddd to
nnnnnnnn. This was because the GOOD_ACTION parameter was specified as RENAME. This message is
for informational purposes only.
●
PGTE2609E DNI GOOD about to delete DSN dddddddd
Explanation:
A DNI request was completed successfully, and DNI was about to delete data set ddddddd. This was
because the GOOD_ACTION parameter was specified as DELETE. This message is for informational
purposes only.
●
PGTE2610E DNI error on Postprocessing xxxxxxxx request r15=nn
Explanation:
The DNI interface tried to perform post-processing request xxxxxxxx, but received return code nn.
xxxxxxxx will be either CATALOG, UNCATLG, DELETE, or RENAME.
If this message persists, contact TIBCO Technical Support.
●
PGTE2611E DNI member mmmmmmmm not found: DNIDISA command failed
Explanation:
The DNIDISA operator command was entered to disable a DNICFG entry, but member name
mmmmmmmm was not found in the active DNICFG entries.
Check the member name that is entered, and reenter the command if necessary with the correct
member name.
●
PGTE2612E DNI member mmmmmmmm already enabled: DNIENA command failed
Explanation:
The DNIENA command was entered to enable a DNICFG entry, but member mmmmmmmm was already
active.
●
PGTE2613E DNI member DNISTART not found in DNICFG member: no members activated
Explanation:
At startup, DNI tried to read member DNISTART from the DNICFG DD statement. DNI could not
find member DNISTART. As a result, no DNI members will be activated at startup time.
●
PGTE2614E DNI error opening ddname DNICFG: no members activated
Explanation:
At startup, DNI tried to open the DNICFG file, but received an open error. No members will be
activated, but DNI will continue to execute. Other messages accompanying this message will give
additional information about the error that caused the problem.
●
PGTE2615E DNI DNICFG DD statement missing: no members activated
Explanation:
At startup, DNI detected that the DNICFG DD statement was missing from the Platform Server
startup JCL. No members will be activated, but the Platform Server will continue to run.
Check the Platform Server startup JCL and make sure that the DNICFG DD statement is included.
●
PGTE2616E DNI DNICFG must be RECFM=FB,LRECL=80: no members activated
Explanation:
The DNICFG file must be defined as RECFM=FB and LRECL=80. The block size could be any multiple
of 80. The file defined as DNICFG was not defined using these characteristics. No members will be
activated.
Correct the RECFM and LRECL parameters to conform to these requirements.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
79
●
PGTE2617E DNI member xxxxxxxx disabled: DNIDISA command successful
Explanation:
The DNIDISA operator command was entered to disable a DNICFG entry, and the entry was
disabled successfully.
●
PGTE2618E DNI DNISTART error: member name > 8 BYTES: no members activated
Explanation:
The Platform Server DNI was reading the DNISTART member that defined the members that must be
enabled at startup, and found one member name that exceeded the maximum member length of 8
bytes. No members will be activated from this line in the DNISTART member.
Correct the entry in DNISTART and restart the Platform Server. Optionally, use the DNIENA command
to manually start any entries that are incorrectly specified.
●
PGTE2619E DNI Error reading member mmmmmmmm: Member not found
Explanation:
The Platform Server DNI tried to enable member mmmmmmmm either at startup or because of an DNIENA
command. But the member was not found in the DNICFG file.
Check the member name, and fix the DNISTART member, or the DNIENA command. The member will
not be enabled.
●
PGTE2620E DNI parameter format error in member mmmmmmmm record nn: Record follows
Explanation:
A parameter was specified in line nn of DNICFG member mmmmmmmm, but the parameter specified
invalid or unsupported data. The member will not be enabled. The record in error will be displayed
on the next line.
®
See the section on DNI in TIBCO Managed File Transfer Platform Server for z/OS User's Guide for the
exact syntax of the parameter.
●
PGTE2621E DNI Record: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Explanation:
A parameter error occurred in a record of the DNICFG file.This record will be displayed.
Accompanying messages show in more detail the cause of the error.
●
PGTE2622E DNI parameter not found in member mmmmmmmm record nn: Record follows
Explanation:
An invalid parameter was specified in line nn of DNICFG member mmmmmmmm. The member will
not be enabled. The record in error will be displayed on the next line.
®
See the section on DNI in TIBCO Managed File Transfer Platform Server for z/OS User's Guide for the
parameters that are supported.
●
PGTE2624E DNI No free slots on DNICFG Dataspace: Member mmmmmmmm not activated
Explanation:
A user attempts to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but there is no spaces on the DNICFG data space to store the data. Use the DNICFGQ
parameter of the started task PARM statement to add more slots on the data space.
●
PGTE2625E DNI DSN field required but not entered: member mmmmmmmm not enabled
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but the DSN parameter was not entered in member mmmmmmmm. DSN (or its equivalent
LF/LFILE) is required in each DNI entry.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
80
●
PGTE2626E DNI COMMAND not supported for RECEIVE: member mmmmmmmm not enabled
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but the COMMAND parameter was not supported for a RECEIVE request. Member
mmmmmmmm is not enabled.
●
PGTE2627E DNI COMMAND/TYPE parameters conflict: member mmmmmmmm not enabled
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but the TYPE and COMMAND parameters conflicted with each other. The member is not
enabled.
Review the Platform Server Batch interface parameters for a more thorough explanation of these
parameters.
●
PGTE2628E DNI PROTOCOL=APPK required for TYPE=COMMAND: Member mmmmmmmm not
enabled
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command but did not specify PROTOCOL=APPK. Member mmmmmmmm is not enabled.
●
PGTE2629E DNI NODE/LIST/IPADDR/IPNAME required: member mmmmmmmm not enabled
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but a required parameter was not configured. DNI requires the NODE, LIST, IPADDR or
IPNAME parameter be defined in each DNICFG member. The member is not enabled.
●
PGTE2630E DNI REQUEST=SEND/RECEIVE required: member mmmmmmmm not enabled
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but the REQUEST parameter was not defined. REQUEST=SEND/RECEIVE must be defined in
each DNICFG member. The member is not enabled.
●
PGTE2631E DNI FAIL_ACTION required: member mmmmmmmm not enabled
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but the FAIL_ACTION parameter was not defined. FAIL_ACTION-RENAME/DELETE must be
defined in each DNICFG member. The member is not enabled.
●
PGTE2632E DNI FAIL_NEWDSN required: member mmmmmmmm not enabled
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but the FAIL_NEWDSN parameter was not defined. FAIL_NEWDSN must be defined when
FAIL_ACTION=RENAME. The member is not enabled.
●
PGTE2633E DNI GOOD_ACTION required: member mmmmmmmm not enabled
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but the GOOD_ACTION parameter was not defined. GOOD_ACTION=RENAME/DELETE must be
defined in each DNICFG member. The member is not enabled.
●
PGTE2634E DNI GOOD_NEWDSN required: member mmmmmmmm not enabled
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
81
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but the GOOD_NEWDSN parameter was not defined. GOOD_NEWDSN must be defined when
GOOD_ACTION=RENAME. The member is not enabled.
●
PGTE2635E DNI ** parameter must be preceeded by a . and must be the last
qualifier
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but the DSN (or LF/LFILE) parameter was specified with an invalid wildcard parameter.
When a wildcard ** is specified, it must be the only data in the qualifier, and no characters can
appear after it. The member is not enabled.
●
PGTE2636E DNI %NODE/%IPADDR must not be the first qualifier: member mmmmmmmm not
enabled
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but the %NODE or %IPNAME parameter were specified incorrectly. %NODE and %IPNAME must
not be the first qualifier. The member is not activated.
●
PGTE2637E DNI %NODE/%IPADDR must be the only data in the qualifier: member
mmmmmmmm not enabled
Explanation:
A user attempted to enable a DNI entry either through the STARTUP member or through the DNIENA
command, but the %NODE or %IPNAME parameter were specified incorrectly. %NODE and %IPNAME must
be the only characters in the qualifier. The member is not activated.
●
PGTE2638E DNI Transaction tttttttttt not found in DNIACT DSP for DSN dddddddd:
Purge failed
Explanation:
A DNI request was completed, and DNI tried to perform post processing of this request. The
request could not be found in the DNIACT data space. Therefore, the request could not be purged
from the data space. This error is typically caused when the DNIACT data space is out of sync with
the Platform Server queue data space (DIVDDSTM). This error can also be caused by the user
issuing the DNIPURGE request to purge a request from the DNIACT data space.
●
PGTE2639E DNI DSN dddddddd not available for xxxxxxxx access: Request will be
retried at next interval
Explanation:
DNI detected that a file meeting its selection criteria was created, but the file was in use and could
not be processed by DNI. DNI will try to process the request at the next scan interval.
●
PGTE2640E DNI nn requests queued: DNI TRN=tttttttt
Explanation:
When DNI created a request that was sent to a destination list, this messages was displayed to show
the number of transfers that were actually queued. nn defined the number of requests that were
queued, and tttttttt showed the DNI transaction number that was generated.
●
PGTE2641E DNI Schedule request failed RC=nn
Explanation:
DNI tried to schedule a request, but received return code nn. Accompanying messages will show
the actual reason for the failure.
If they do not, then contact TIBCO Technical Support.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
82
●
PGTE2642E DNI No space left in DNIACT DSP: Postprocessing will not be performed
Explanation:
DNI scheduled a request to the active the Platform Server queue, but no space was left on the
DNIACT data space to save the request. No post processing will be performed on this data set.
Use the DNIACTQ parameter of the started task PARM statement to add more slots on the data space.
●
PGTE2644E DNI Unable to update %NODE/%IPADDR parameter: DSN dddddddd Qualifier
invalid
Explanation:
DNBI is unable to perform substitution on the %IPNAME or %NODE parameters because the field is
invalid or missing from data set dddddddd. The request was not queued.
●
PGTE2645E DNI Substitution length exceeds nn for DSN dddddddd: Request not
scheduled
Explanation:
DNI tried to perform substitution for data set dddddddd, but the new length of the field exceeded the
maximum length of nn characters. The request is not queued.
Update the DNICFG parameter file to change the file name to accept less characters.
●
PGTE2646E DNI Substitute parameter xxxxxxxx not found: Request not scheduled
Explanation:
The user specified an invalid DNI substitutable parameter xxxxxxxx.
®
See the DNI section in TIBCO Managed File Transfer Platform Server for z/OS User's Guide for more
information on substitutable parameters that are supported.
●
PGTE2648E DNI Transid tttttttt not found: DNIPURGE command failed
Explanation:
The DNIPURGE command for DNI transfer ID tttttttt was entered. Transfer ID tttttttt was not found.
Therefore, the request is not purged form the DNIACT queue.
Run the DNIDISP command without a transfer ID to display a list of requests that are on the
DNIACT queue.
●
PGTE2649E DNI Transid tttttttt not found: DNIDISP command failed
Explanation:
The DNIDISP command was entered for DNI transfer ID tttttttt. Transfer ID tttttttt was not found.
Therefore, the request is not displayed.
Run the DNIDISP command without a transfer ID to display a list of requests that are on the
DNIACT queue.
●
PGTE2653E DNI xxxxxxxx command error: TRN must be 8 hex digits
Explanation:
A DNIPURGE or DNIDISP command was issued with an invalid transfer ID. The transfer ID must be 8
hexadecimal digits (0 - 9, A - F).
●
PGTE2654E DNI error on dsn dddddddd: not authorized to xxxxxxxx the dataset
Explanation:
TA post-processing error occurred when trying to rename or delete data set dddddddd. The request
failed, and post processing was terminated. The Platform Server must have read/write/control
authority for any data set that is used by DNI.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
83
●
PGTE2655E DNI xxxxxxxx Error: tttttttttttttttttttttttttttt - RC = nn
Reason=ssssssss
Explanation:
TA DNI post-processing error occurred. The request was specified as xxxxxxxx. ttttt was a text
representation of the error that ended with return code nn. The request failed, and post processing is
terminated. The reason code ssssssss gives additional information about the cause of the failure.
●
PGTE2657E DNI Error loading IGGCSI00: Using DNICSI00 module for LOCATE requests
SMS Version: vvrr
Explanation:
This message is only displayed when the DFSMS version on your system is 1.4 or later. vvrr was the
release of SMS that was on your system. The IBM Catalog Search Interface module IGGCSI00 was
not loaded. As a result, the platform DNICSI00 module was used in its place. Typically, DNICSI00 is
used only for installations with SMS 1.3 and earlier. Accompanying this message is an IBM CSV
message which gives the reason that the LOAD failed.
●
PGTE2658E DNI Continuation Error: > 4 records contain continuation in column 72:
member=mmmmmmmm record=nn
Explanation:
DNI configuration member mmmmmmmm encountered an error on record nn. A maximum of 4
consecutive records could contain a continuation character in column 72. DNI found more than 4
consecutive records with a continuation character in column 72. Member mmmmmmm is not
activated. Message 2621 is typically displayed after this message to show the current record at the
time the error occurs.
●
PGTE2659E DNI Continuation Error: Parameter complete: column 72 has continuation:
member=mmmmmmmm record=nn
Explanation:
DNI configuration member mmmmmmmm encountered an error on record nn. The user specified a
complete parameter, but the continuation character was turned on. Member mmmmmmm is not
activated. Message 2621 is typically displayed after this message to show the current record at the
time the error occurs.
●
PGTE2660E DNI Validate failed for xxxxxxxx – yyyyyyyy contains invalid characters
for z/OS DSN: member nnnnnnnn not enabled
Explanation:
Member nnnnnnnn was enabled at startup, or through the DNIENA command. However, an error was
found with substitution parameter yyyyyyyy. xxxxxxxx is typically a parameter that required a data
set substitution such as FAIL_NEWDSN. When the substitution was attempted, the result was an
invalid MVS data set name. Member xxxxxxxx is not enabled
●
PGTE2661E DNI Pathname Exceeds 256 bytes: xxxxxxxxxxxxxxxx'
Explanation:
An HFS directory had a data set whose path exceeded the maximum allowed length of 256 bytes.
When the error occurred, the DNI program ignored this file and continues to process the next file in
the directory.
●
PGTE2662E xxxxxxxx yyyyyyyy
Explanation:
An error occurred when the Platform Server DNI program used a USS request to read an HFS
directory. This message displays a text version of a message that describes the error.
If you receive this error, contact TIBCO Technical Support.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
84
●
PGTE2663E DNI Found invalid Filetype for path: xxxxxxxxxxxxxxx
Explanation:
The Platform Server DNI program was processing a file but did not support the file type. The
Platform Server only supported files defined as Regular Files. When the error occurred, the DNI
program ignored this file and continues to process the next file in the directory.
●
PGTE2664E DNI Local DSN specified: xxxxxxx may not contain HFS / character
Explanation:
The user defined a Platform Server DNI DSN as an MVS data set, but the data set defined in the
GOOD_NEWDSN or FAIL_NEWDSN parameter contained a forward slash (/) which indicated an HFS file.
MVS data sets cannot be renamed to HFS data sets; therefore, this DNI definition is not supported.
Correct the definitions and activate the DNI member through the DNIENA command.
●
PGTE2665E DNI Local HFS file specified: xxxxxxxxxxx must contain HFS / character
Explanation:
The user defined a Platform Server DNI DSN as an HFS file, but the data set defined in the
GOOD_NEWDSN or FAIL_NEWDSN parameter did not contain a forward slash (/) which indicated an
MVS file. HFS data sets cannot be renamed to MVS data sets; therefore, this DNI definition was not
supported.
Correct the definitions and activate the DNI member through the DNIENA command.
●
PGTE2666E DNI NO / found in HFS file: xxxxxxxxxxxxxxxxx
Explanation:
The Platform Server DNI configuration program detected that a file was an HFS file, but it did not
detect a forward slash (/) in the file name. This DNI definition was not supported.
If this error occurs, contact TIBCO Technical Support.
●
PGTE2667E DNI File contains invalid GENERIC characters in DIR name: xxxxxxxxxxx
Explanation:
The Platform Server DNI configuration program detected that an HFS file contained generic
characters (* or %) in the path name. Generic characters are only allowed in the file name. This DNI
definition is not supported.
Correct the definitions and activate the DNI member through the DNIENA command.
●
PGTE2668E DNIACT ALET not found: DNIPURGE failed
Explanation:
A DNI request completed processing and the Platform Server contacted the DNI system to purge
the request from the DNIACTIV queue. However, the DNI program could not purge the request
from the DNIACT dataspace because the ALET associated with the dataspace was not available. The
DNIPURGE request failed, and the request will remain on the DNIACT queue.
Use the DNIPURGE command to manually purge the request from the queue.
●
PGTE2669E xxxxxxxx and yyyyyyyy parameters are mutually exclusive
Explanation:
The user attempted to enable a DNI member but entered two parameters that were mutually
exclusive. xxxxxxxx and yyyyyyyy parameters conflicted with each other. Additional messages
should document the member that is in error.
®
For more information, see the section on DNI in TIBCO Managed File Transfer Platform Server for Z/os
User's Guide.
Correct the error and use the DNIENA command.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
85
●
PGTF2670E DNI MQ Error Member=mmmmmmmm: Invalid MQ QMGR defined: 1 to 4
characters must follow $MQ: and is terminated with :
Explanation:
The user attempted to use a MQ message queue within DNI, but the queue manager name was
defined incorrectly. When using MQ, the DSN parameter must be specified as DSN=
$MQ:xxxx:queue_name; where xxxx is the MQ Queue Manager name. The Queue Manager name
must be from 1 to 4 bytes long and be followed by a colon (:). mmmmmmmm is the member that is in
error.
Correct the error, and enable the node by using the DNIENA operator command.
●
PGTE2673E DNINODE detail display failed: DNI node nnnnnnnn not found
Explanation:
The user entered the DNINODE command and specified the DNINODE name to display detailed
information of this node. But the DNI node name nnnnnnnn was not enabled. Use the DNINODE
command without any parameters to determine the DNI node names that are enabled. Only after a
DNI node is enabled, detailed information about the node is displayed.
●
PGTE2675E DNI xxxxxxxx failed: Cannot get exclusive access for DSN=ddddddddddd
Explanation:
The DNI program completed a request and attempted to either rename or delete data set dddddddd.
To do this, the DNI program required exclusive access to the data set. The DNI program could not
get exclusive access to that data set. The DELETE or RENAME function is not be performed.
●
PGTF2676E MQ DNI Error: Load Error on module mmmmmmmm: MQ SCSQLOAD/SCSQAUTH must
be in STEPLIB
Explanation:
The DNI program attempted to access an MQ message queue, but received an error it attempted to
load one of the required MQ programs. mmmmmmmm defined the name of the program that was not
loaded. To use MQ files under the Platform Server, two libraries (SCSQLOAD and SCSQAUTH)
must be in either the LINKLST or the Platform Server STEPLIB.
●
PGTF2677E MQ DNI Error: FAIL_ACTION/GOOD_ACTION not allowed when processing MQ
files
Explanation:
The user defined the DNI DSN as an MQ message queue, but incorrectly specified either the
FAIL_ACTION or GOOD_ACTION parameter. These parameters were not valid when an MQ transfer
took place. The DNI node is not enabled.
●
PGTF2678E MQ DNI Error: MQ rrrrrrrr Error RC=xx REA=yy: tttttttttttttttttt
Explanation:
An error occurred when the DNI program processed an MQ message queue. rrrrrrrr defined the
type of request that was performed, while xx defined the return code, and yy defined the reason
code. tttttttttttttttttt contained a text explanation of the error.
●
PGTF2679E MQ DNI Error Cannot get Shared access to Message Queue qqqqqqqq
Explanation:
An error occurred when the DNI program processed an MQ message queue indicating that the DNI
program failed to get shared access to an MQ message queue. qqqqqqqq defines the name of the
queue that caused the error. When this error occurred, the DNI request failed and is retried at a later
time.
●
PGTE2680E DNI Invalid xx in member mmmmmmmm: GDG must be specified as (+1) for
FAIL_NEWDSN and GOOD_NEWDSN
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
86
Explanation:
The user attempted to specify a GDG for the FAIL_NEWDSN or GOOD_NEWDSN parameter but
incorrectly specified the GDG qualifier. In these parameters, the only GDG qualifier that is allowed
is +1. The DNI member is not enabled.
Correct the error, and enable the DNI node by using the DNIENA command.
●
PGTE2681E DNI Invalid DSN in member mmmmmmmm: GDG must be specified as (0) for
DSN parameter
Explanation:
The user attempted to specify a GDG for the DSN parameter but incorrectly specified the GDG
qualifier. In this parameter, the only GDG qualifier that is allowed is 0. The DNI member is not
enabled.
Correct the error, and enable the DNI node by using the DNIENA command.
●
PGTE2682E DNI Rename failed for dddddddddddd: Locate failed for GDG ggggggggggg
Explanation:
When DNI was processing a file, it attempted to rename dataset dddddddd to a GDG called gggggggg.
The Platform Server attempted to get the correct GDG number, but the locate for the new dataset
name failed. This could mean that the GDG base was not correctly defined for dasaset gggggggg.
Review the DNI member to make sure that the GDG names are defined correctly.
●
PGTE2700E PPASCRPT: FINDVECT failed: Request terminated
Explanation:
A PPA CALLJCL request was executed for program PPASCRPT, but program PPASCRPT received
an internal error and could not continue processing. The PPA request is terminated.
Contact TIBCO Platform Technical support.
●
PGTE2701E PPASCRPT: Request failed: No PARM data passed to this program
Explanation:
A PPA CALLJCL request was executed for program PPASCRPT but no PARM data was passed in
the PPA data field. PPASCRPT expects an optional Node parameter as well as a required script
name. The PPA request is terminated.
Correct the PPA command and execute the file transfer again.
●
PGTE2702E PPASCRPT: Request failed: Script data invalid or missing
Explanation:
A PPA CALLJCL request was executed for program PPASCRPT but no script name was passed in
the PPA data field. PPASCRPT expects an optional node parameter as well as a required script
name. The PPA request is terminated.
Correct the PPA command and execute the file transfer again.
●
PGTE2703E PPASCRPT: Request failed: NODE name invalid
Explanation:
A PPA CALLJCL request was executed for program PPASCRPT but the node name passed was
invalid (either 0 bytes or more than 8 bytes). The PPA request is terminated.
Correct the PPA command and execute the file transfer again.
●
PGTE2705E PPASCRPT: Script schedule request failed: See accompanying messages for
more details
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
87
A PPA CALLJCL request was executed for program PPASCRPT. The script was not scheduled
successfully to the started task. Accompanying this message will be messages that will explain in
more detail why the request was not scheduled successfully.
●
PGTT2800E Activity tttttttttt hit EOF attempting to reach restart record 9999:
Request Terminated
Explanation:
SAPI request tttttttttt was being restarted. The Platform Server was positioning itself to record 9999,
but before it reached that record, End Of File was detected on the file. The request is terminated
with a temporary file error. The request will be restarted from the beginning the next time the job
output is selected by the Platform Server.
●
PGTT2801E Activity tttttttttt Restart record count 9999 exceeds CKPT record count
9999: Request Terminated
Explanation:
SAPI request tttttttttt was being restarted. The Platform Server was positioning itself to record 9999,
but its IO routines detected a blocking error because the actual restart point exceeded that record
number. The request is terminated with a temporary file error. The request will be restarted from the
beginning the next time the job output is selected by the Platform Server.
●
PGTT2802E Activity tttttttttt FUSSAPIP could not find NODE nnnnnnnn: Request
Terminated
Explanation:
The Platform Server SAPI interface detected a report that met its selection criteria and initiated a
transfer request to that node. Before the request could be processed however, the Platform Server
attempted to locate that node entry but the node entry was not found.
Make sure that the node entry was not deactivated using the Platform Server DISABLE command. If
this message persists, contact TIBCO Technical Support.
●
PGTT2805E Activity tttttttttt FUSSAPIP substitution length exceeds max 256 for
RDSN=rrrrrrrrrr
Explanation:
The Platform Server was processing SAPI request tttttttttt, and the Platform Server was performing
parameter substitution, but the length of the target remote file exceeded 256 bytes.
Change the node SAPI_REMOTE_FILE to make the dataset name shorter. Then disable and enable
the node definition for the change to take place.
●
PGTT2806E Activity tttttttttt FUSSAPIP eeeeeeee error: tttttttt R15=99
Explanation:
The Platform Server was processing request tttttttttt, but received an error processing SAPI request
type eeeeeeee. A test message is displayed that gives more information about the error code. The
value in R15 is also displayed.
For SAPI return code information, see IBM manual OS/390 MVS Using the Subsystem Interface.
●
PGTT2807E Activity tttttttttt FUSSAPIP eeeeeeee error: tttttttt: SSOBRETN=99
Explanation:
The Platform Server was processing request tttttttttt, but received an error processing SAPI request
type eeeeeeee. A test message is displayed that gives more information about the error code. The
value returned in field SSOBRETN is also displayed.
For SAPI return code information, see IBM manual OS/390 MVS Using the Subsystem Interface.
●
PGTT2808E Activity tttttttttt FUSSAPIP eeeeeeee error: tttttttt: SSS2REAS=99
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
88
Explanation:
The Platform Server was processing request tttttttttt, but received an error processing SAPI request
type eeeeeeee. A test message is displayed that gives more information about the error code. The
value returned in field SSS2REAS is also displayed.
For SAPI return code information, see IBM manual OS/390 MVS Using the Subsystem Interface.
●
PGTT2809E OSISAPIC QUEUE Add failed with RC=999: Request not processed
Explanation:
The Platform Server detected JES spool output that met the selection criteria defined in the node
definition and attempted to schedule a transfer request. but the transfer request failed with return
code 999. Additional messages should display the reason for the error. If the return code is 253, the
user profile has not been defined for the node. Optionally, the user can specify the user ID/password
to use for SAPI requests on the node DEFAULT_USERID and DEFAULT_PASSWORD parameters.
●
PGTT2810E OSISAPIC SAPI Count error: tttttttt: R15=99
Explanation:
The Platform Server issued an SAPI count request but received an error. A test message is displayed
that gives more information about the error code. The value in R15 is also displayed.
For SAPI return code information, see IBM manual OS/390 MVS Using the Subsystem Interface.
●
PGTT2811E OSISAPIC SAPI Count error: tttttttt: SSOBRETN=99
Explanation:
The Platform Server issued an SAPI Count request, but received an error. A test message is
displayed that gives more information about the error code. The value in field SSOBRETN is also
displayed. SAPI return code information is documented in IBM manual OS/390 MVS Using the
Subsystem Interface.
●
PGTT2812E OSISAPIC SAPI Count error: tttttttt: SSS2REAS=99
Explanation:
The Platform Server issued an SAPI Count request, but received an error. A test message is
displayed that gives more information about the error code. The value in field SSS2RETN is also
displayed. SAPI return code information is documented in IBM manual OS/390 MVS Using the
Subsystem Interface.
●
PGTE2901E mmmmmmmmmmmmmmmmmm
Explanation:
This message displays the record in error when the RADIUS configuration program detects an error.
This message is always accompanied by one or more additional messages that give detailed reasons
for the error.
●
PGTF3012E Selection Diagnostic: File Busy for activity xxxx
Explanation:
The remote system reported that the file required to transfer to or from was in use by another user.
The request will be purged by the server; re-initiate the request at another time.
●
PGTF3109E Activity xxxx unsuccessful with Node yyyy Return Code zzzz
Explanation:
The transfer failed with the return code zzzz.
●
PGTF3120E tttttttt >56 bit Encryption not allowed: Activity tttttttt terminated:
Contact TIBCO Technical Support
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
89
The Platform Server version that you currently have does not support encryption where keys exceed
56 bits. Therefore, 3DES and BLOWFISH_LONG encryption are not supported. The US Department
of Commerce restricts the export of software with encryption keys exceeding 56 bits to countries
other than Canada.
If you are in the USA or Canada and receive this message, contact TIBCO Technical Support.
●
PGTF3121E Encryption mismatch: Partner may not support DES/3DES/BLOWFISH
encryption
Explanation:
The Platform Server was sending encrypted data to its session partner, but the session partner may
not support the desired encryption algorithm.
Check that the remote Platform Server node supports the encryption algorithm that you have to use.
●
PGTF3122E Activity tttttttt for node nnnnnnnn does not specify AUTHENTICATION:
Required by GLOBAL AUTHENTICATE parm
Explanation:
The Platform Server was configured by the GLOBAL AUTHENTICATE parm to require authentication.
Node nnnnnnnn did not specify authentication. Therefore, the request will be terminated.
Add the AUTHORIZATION_KEY to the NODE definition and retry the request.
●
PGTF3123E Activity tttttttt for node nnnnnnnn: AuthKey 1111111111111111 <> NODE
AUTHENTICATION_KEY 2222222222222222
Explanation:
A transfer specified that authentication was being run. However, the authentication keys that were
defined for the remote node did not match the keys transmitted from one node to another.
nnnnnnnn defined the node in error. 1111111111111111 is the authentication key that was
transmitted across the line, and 2222222222222222 is the authentication key that was defined in the
node definition. The request is terminated.
●
PGTF3124E Activity tttttttttt for node nnnnnnnn does not specify AUTHENTICATION:
Required by NODES AUTHENTICATION_KEY
Explanation:
A responder request was received from node nnnnnnnn that did not specify authentication. The
Platform Server scanned the node definitions and found a match for an LUNAME/IPAddress that
required authentication. The request is terminated.
●
PGTF3125E Activity tttttttttt for node nnnnnnnn Remote Authentication Key
1111111111111111: NODE entry not found
Explanation:
A responder request was received from node nnnnnnnn that specified authentication. The Platform
Server scanned the node entries and did not find a match on authentication key 1111111111111111.
The request is terminated.
●
PGTF3126E Activity tttttttttt for node nnnnnnnn: Authentication key
1111111111111111 matches wrong node xxxxxxxx
Explanation:
A responder request was received from node nnnnnnnn that specified authentication. The Platform
Server scanned the node entries and found a match on authentication key 1111111111111111. The
node that matched the request (xxxxxxxx) did not match the IPAddress/LUName of the node that
sent the request. The request is terminated.
●
PGTF3127E Activity tttttttttt for node nnnnnnnn: Remote node does not support
Authentication
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
90
Explanation:
The Platform Server attempted to initiate a request to node nnnnnnnn. The request requires
authentication. However, the remote node did not support authentication. The transfer is
terminated.
Make sure that all the Platform Server systems have the most current version of software.
●
PGTF3128E Activity tttttttttt for node nnnnnnnn: AuthKey kkkkkkkkkkkkkkkk does
not match remote AUTHKEY definition
Explanation:
The Platform Server was responding to a transfer request for node nnnnnnnn that required
authentication. The Platform Server determined that the authentication key used by this system did
not match the authentication key configured in the remote system. As a result, the Platform Server
terminates activity tttttttttt.
Make sure that the authentication key defined on the remote system matches the authentication key
kkkkkkkkkkkkkkkk that is automatically generated by this system the first time that the Platform Server
is started.
●
PGTF3129E Activity tttttttttt for node nnnnnnnn: HASHKEY mismatch - Insure Local
and Remote configs match
Explanation:
The Platform Server request tttttttt for node nnnnnnnn was using the Platform Server HASHKEY
processing. The Platform Server detected that the HASHKEY values on the local and remote
systems did not match. The transfer is terminated with errors.
●
PGTF3130E Activity tttttttttt for node nnnnnnnn: HASHKEY not defined to Local
system
Explanation:
The Platform Server responder was configured to use HASHKEY processing when communicating
with node nnnnnnnn. Node nnnnnnnn however, initiated a request without using HASHKEY
processing. The transfer is terminated with errors.
●
PGTF3131E Activity tttttttttt for node nnnnnnnn: HASHKEY not defined to Remote
system
Explanation:
The Platform Server responder was not configured to use HASHKEY processing when
communicating with node nnnnnnnn. Node nnnnnnnn however, initiated a request using
HASHKEY processing. The transfer is terminated with errors.
●
PGTF3132E Activity tttttttttt for node nnnnnnnn: HASHKEY not supported on Remote system
Explanation:
The Platform Server has been configured to use HASHKEY processing when communicating with
NODE nnnnnnnn. However, NODE nnnnnnnn does not support HASHKEY processing. This
message is displayed and the request is terminated with errors.
●
PGTF3134E Activity tttttttttt: SSL error with node nnnnnnnn Diag=xx
Explanation:
An SSL request was made to node nnnnnnnn, and the SSL authentication failed. The Diag code gives
additional information about the reason for the failure. Additional messages should be displayed
giving the actual reason for the failure. The file transfer request is terminated.
●
PGTF3136E SSL Request terminated with Node nnnnnnnn: Global SSLIPPORT not defined
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
91
A user requested SSL authentication on a file transfer request, but the GLOBAL SSLIPPORT
parameter was not configured. When this parameter is not configured, the Platform Server does not
activate the SSL interface code. The file transfer request is terminated.
●
PGTF3137E SSL Request terminated with Node nnnnnnnn: no MSGQ slots available max=xxx
Explanation:
A user requested SSL authentication on a file transfer request with node nnnnnnnn. The Platform
Server supports multiple MSGQ slots, and will re-use them when a transfer request completes.
If this problem persists, restart and the Platform Server will automatically recreate the MSG table. If
this problem continues happening, contact TIBCO Technical Support.
●
PGTF3140E mmmmmmmmmmmmmmmmmmmmmmm SSL MSGQ Error
Explanation:
A user requested SSL authentication on a file transfer request, but an error was received processing
the SSL Message Queue. A detailed text message is also displayed to give a better understanding of
the error.
●
PGTF3141E SSL Internal CID mismatch: Record bypassed: XXXXXXXX YYYYYYYY
Explanation:
A user requested SSL authentication on a file transfer request. The Platform Server was reading the
Message queue and found invalid information in that queue. It is possible that this information was
from an old transfer that did not complete or from an application that was incorrectly using the
Platform Server message queue. The Platform Server purges the invalid record and continues
reading the message queue until it finds the correct record.
●
PGTF3142E SSL Invalid MSGQ Request type: Not R/W
Explanation:
A user requested SSL authentication on a file transfer request. The Platform Server was reading the
Message queue, and found invalid information in that queue. It is possible that this information was
from an old transfer that did not complete or from an application that was incorrectly using the
Platform Server message queue. The File transfer request is terminated with an error.
●
PGTF3143E SSL xxxxxxxx error: yyyyyyyy RC=rr
Explanation:
A user requested SSL authentication on a file transfer request. The Platform Server was processing
the request and detected an error on SSL call xxxxxxxx. The return code and a text explanation of the
error is also displayed. The file transfer request is terminated with an error.
●
PGTF3145E mmmmmmmmmmmmmmmmmmm
Explanation:
The Platform Server was requesting a request from UNIX system services, and the request failed.
This message gives a text explanation of the error. The transfer request is terminated with errors.
●
PGTF3146E SSL SHA data < 24 bytes: Decryption Failed
Explanation:
The Platform Server was performing SSL decryption of a data packet, but the data packet was less
than 24 bytes. Since the SHA (Secure Hashing Algorithm) requires 24 bytes to run, the Platform
Server was unable to complete the decryption request. The file transfer request failed with errors.
If this request can be reproduced, take a Platform Server TCPTRAC and send the trace output to
TIBCO Technical Support.
●
PGTF3147E SSL SHA counters do not match: CounterL=aaaaaaaa CounterR=bbbbbbb
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
92
Explanation:
The Platform Server was performing SSL Decryption of a data packet, but the SHA counters did not
match. The file transfer request failed with errors.
If this request can be reproduced, take a Platform Server TCPTRAC and send the trace output to
TIBCO Technical Support.
●
PGTF3148E SSL SHA Hash values do not match
Explanation:
The Platform Server was performing SSL decryption of a data packet, but the SHA hash values did
not match. The file transfer request failed with errors. Message 3149 will accompany this message
with more detailed information on the HASH values.
If this request can be reproduced, take a Platform Server TCPTRAC and send the trace output to
TIBCO Technical Support.
●
PGTF3149E SSL SHA HASH AAAAAAAA Value=bbbbbbbb
Explanation:
The Platform Server was performing SSL decryption of a data packet, but the SHA hash values did
not match. The file transfer request failed with errors. This message accompanies message 3148.
●
PGTF3150E Restart of Transnum tttttttttt Failed - Transfer is in Active state:
Request yyyyyyyyyy Purged
Explanation:
The Platform Server received a request for a file transfer checkpoint restart. When looking through
its queues, it found the proper transfer request to restart, but the transfer request was in an ACTIVE
state. The Platform Server terminates the transfer request with and purges the transfer request.
If this problem persists, contact TIBCO Technical Support.
●
PGTF3151E Activity tttttttttt Invalid Deallocate received from nnnnnnnnnn:
Request terminated with errors
Explanation:
The Platform Server was processing Initiator activity tttttttttt. It received a deallocate request when it
expected to receive data from the partner. This is typically caused by a problem on the remote
Platform Server system.
If this problem persists, take a Platform Server trace, and send the trace output to TIBCO Technical
Support.
●
PGTF3153E Activity tttttttttt: xxxxxxxx ENQ for DSN dddddddd failed: File is
currently in use
Explanation:
The Platform Server attempted to access a dataset but is unable to because the dataset was in use.
xxxxxxxx defines whether the request was for shared or exclusive access to the dataset, and ddddddd
defines the dataset that the Platform Server was trying to use. The Platform Server considers this to
be a temporary error, and will retry the request if the GLOBAL FILE_ERROR_TRY_COUNT was not
exceeded.
●
PGTF3154E xxxxxxxx error on activity: tttttttt node: nnnnnnnn - try count exceeds
GLOBAL default - activity purged
Explanation:
The Platform Server detected a temporary file error. The file error try count exceeded the GLOBAL
FILE_ERROR_TRY_COUNT, so the transfer request will be purged from the queue.
If necessary, correct the error that caused the temporary file error and resubmit the request.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
93
●
PGTF3157E tttttttt CALL to program @2 Unsuccessful: Return code=rr
Explanation:
The Platform Server received a CALLPROG or CALLJCL request from a remote system. The
Platform Server called program pppppppp. The call was unsuccessful, and the program passed a
return code of nn (this should be non-zero) back to the Platform Server.
●
PGTF3158E tttttttt Error on LOAD of program pppppppp: Program not found: Make
sure program is in Platform Server STEPLIB
Explanation:
The Platform Server received a CALLPROG or CALLJCL request from a remote system. The
Platform Server attempted to load program pppppppp, but the z/OS LOAD request failed. This is
usually because the load module was not located in the z/OS LINKLST or the Platform Server
STEPLIB.
●
PGTF3159E tttttttttt rrrrrrrr Program pppppppp abended with code=xxx
Explanation:
The Platform Server received a CALLPROG or CALLJCL request from a remote system. The
Platform Server called program pppppppp, but the program abended with code xxx. Additional
messages will display the PSW and registers at the time of the error.
Review the called program to make sure that the linkage between this program and the Platform
Server is correct.
●
PGTF3160E tttttttttt Invalid rrrrrrrr data passed: Request terminated
Explanation:
The Platform Server received a CALLPROG or CALLJCL request from a remote system. The
Platform Server was processing the request, but the data passed to the Platform Server was invalid.
That is most likely because the data passed in the CALLPROG or CALLJCL did not contain a valid
program name. The CALLPROG or CALLJCL request was unsuccessful.
●
PGTF3161E tttttttttt Invalid rrrrrrrr Program Name: Program name must be 1 to 8
characters followed by a space
Explanation:
The Platform Server received a CALLPROG or CALLJCL request from a remote system. The
Platform Server was processing the request, but the data passed to the Platform Server was invalid.
That is most likely because the data passed in the CALLPROG or CALLJCL contained a program
name that was longer than 8 characters. The CALLPROG or CALLJCL request was unsuccessful.
●
PGTE3162E Abend xxx detected in rrrrrrrr pppppppp - PSW: wwwwwwww yyyyyyyy
Program Address: aaaaaaaa
Explanation:
The Platform Server received a CALLPROG or CALLJCL request from a remote system. The
Platform Server called program pppppppp, but the program abended. This message displays the
abend code, and the PSW associated with the abend. It also displays the address of the program that
was called.
Review the called program to make sure that the linkage between this program and the Platform
Server is correct.
●
PGTE3163E General Registers at time of error
Explanation:
The Platform Server received a CALLPROG or CALLJCL request from a remote system. The
Platform Server called program pppppppp, but the program abended. This message indicates that
following this message will be a display of the general registers at the time of the abend.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
94
Review the called program to make sure that the linkage between this program and the Platform
Server is correct.
●
PGTE3164E Access Registers at time of error
Explanation:
The Platform Server received a CALLPROG or CALLJCL request from a remote system. The
Platform Server called program pppppppp, but the program abended. This message indicates that
following this message will be a display of the access registers at the time of the abend.
Review the called program to make sure that the linkage between this program and the Platform
Server is correct.
●
PGTE3165E R1:aaaaaaaa R2:bbbbbbbb R3:cccccccc R4:dddddddd
Explanation:
The Platform Server received a CALLPROG or CALLJCL request from a remote system. The
Platform Server called program pppppppp, but the program abended. This message displays the
general/access registers at the time of the error. The general registers start with R, while the access
registers start with AR. Review the called program to make sure that the linkage between this
program and the Platform Server is correct.
●
PGTE3166E tttttttttt DSN invalid on Platform Server SUBMIT: DSN null or exceeds
44 characters: Request terminated
Explanation:
The Platform Server received a SUBMIT request from a remote system. The Platform Server was
processing the request, but the data passed to the Platform Server was invalid. That is most likely
because the DSN passed in the SUBMIT contained a dataset name that was 0 characters or longer
than 44 characters. The SUBMIT request was unsuccessful.
●
PGTE3167E tttttttttt MEMBER invalid on Platform Server SUBMIT: Member exceeds 8
characters: Request terminated
Explanation:
The Platform Server received a SUBMIT request from a remote system. The Platform Server was
processing the request, but the data passed to the Platform Server was invalid. That is most likely
because the member name passed in the SUBMIT contained a name that was longer than 8
characters. The SUBMIT request was unsuccessful.
●
PGTE3168E tttttttttt MEMBER defined on Platform Server SUBMIT but GLOBAL
JOB_SUBMIT_DSN not defined: Request terminated
Explanation:
The Platform Server received a SUBMIT request from a remote system. The Platform Server was
processing the request, and recognized that only a member name was passed in the SUBMIT
request. The Platform Server detected that the GLOBAL JOB_SUBMIT_DSN was not defined however.
This parameter is required if only a member name is included on the SUBMIT request. You can
either define the GLOBAL JOB_SUBMIT_DSN parameter or specify the fully qualified dataset name
with a member. The SUBMIT request was unsuccessful.
●
PGTE3169E tttttttttt Platform Server SUBMIT parm count exceeds max of 50: Request
terminated
Explanation:
The Platform Server received a SUBMIT request from a remote system. The Platform Server was
processing the request and detected that more than 50 symbolic parameters were passed on the
SUBMIT request. The Platform Server limits the number of symbolic parameters to 50. The SUBMIT
request was unsuccessful.
●
PGTE3170E tttttttttt Platform Server SUBMIT PARM field invalid: data=dddddddd:
Request terminated
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
95
Explanation:
The Platform Server received a SUBMIT request from a remote system. The Platform Server was
processing the request and detected that the data passed was invalid. Most likely this is because of
the symbolic parameter not being in the format &PARM1=parmdata. The data in error was also
displayed (dddddddd). The SUBMIT request was unsuccessful.
●
PGTE3171E tttttttttt Platform Server SUBMIT PARM 1st character must be ampersand:
data=ddddddddddd: Request terminated
Explanation:
The Platform Server received a SUBMIT request from a remote system. The Platform Server was
processing the request and detected that the data passed was invalid. Most likely this is because the
symbolic parameters were not prefixed with an ampersand ( & ). The data in error is also displayed
(dddddddd). This message indicates that the SUBMIT request was unsuccessful.
●
PGTE3172E tttttttttt Platform Server SUBMIT PARM field invalid: data=@2: Request
terminated
Explanation:
The Platform Server received a SUBMIT request from a remote system. The Platform Server was
processing the request and detected that the data passed was invalid. Most likely this was because
of the symbolic parameter not being in the format &PARM1=parmdata. The data in error is also
displayed (dddddddd). The SUBMIT request was unsuccessful.
●
PGTE3173E tttttttttt Platform Server SUBMIT PARM Quotes invalid: data=dddddddd:
Request terminated
Explanation:
The Platform Server received a SUBMIT request from a remote system. The Platform Server was
processing the request and detected that the data passed was invalid. When an individual
parameter contains a space or other character that would terminate the parm, the data should be
enclosed in a single quote. This message indicates that the Platform Server has detected the start of a
symbolic parm enclosed in a single quote, but could not find the terminating quote. The data in
error is also displayed (dddddddd). The SUBMIT request was unsuccessful.
●
PGTE3174E tttttttttt Platform Server SUBMIT output data length > max allowed=nn:
Request terminated
Explanation:
The Platform Server received a SUBMIT request from a remote system. The Platform Server was
performing parameter substitution but detected that the length of the data exceeded the maximum
allowed length of nn. The SUBMIT request was unsuccessful.
●
PGTE3175E Activity tttttttttt NON SSL request received from NODE nnnnnnnn: SSL
Required by GLOBAL SSL_REQUEST
Explanation:
The Platform Server received a non-SSL request on the correct IPPORT. Based on the value of the
GLOBAL SSL_REQUEST parameter, it determined that requests coming from this IP Address must be
SSL requests.
Either change the remote node to make this an SSL request or modify the GLOBAL SSL_REQUEST
parameter to allow requests to come from this node without SSL.
●
PGTE3176E Activity tttttttttt SSL Request received on NON SSL port for NODE
nnnnnnnn: Request Terminated
Explanation:
The Platform Server received an SSL request on a NON-SSL port. The Platform Server displays this
message and notifies the remote system of the error.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
96
Change the IPPORT on the remote system so that it specifies the port number of the SSL port.
Optionally, change the remote system to not utilize SSL on the request.
●
PGTF3181E xxxx error on activity: tttttttttt node: nnnnnnnn - try count exceeded
- activity put on HOLD
Explanation:
A network or file errors as indicated by xxxx was detected on Initiator transfer tttttttttt to node
nnnnnnnn. The maximum try count was exceeded for this request. The administrator set the
GLOBAL HOLD_TEMPORARY_NETWORK_ERRORS and or the GLOBAL HOLD_TEMPORARY_FILE_ERRORS
parameter to YES. A transfer is placed on HOLD when the max number of tries is exhausted.
●
PGTF3184E Activty tttttttttt ENCRYPT xxxxx does not meet HIPAA regulations:
Request Terminated
Explanation:
The Platform Server was executing a responder 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. For responder tasks, the transfer request
is terminated. This message is sent to the remote system that initiated the request.
Increase the encryption level of the remote system to one that meets the HIPAA requirements.
●
PGTF3185E Activty tttttttttt Node=nnnnnnnn: xxxxxxxxxx turned off due to NODE
definition
Explanation:
The Platform Server was executing the Platform Server Initiator activity tttttttt for node nnnnnnnn.
The node definitions specified either COMPRESS=NEVER or ENCRYPT =NEVER (xxxxxxxxx). The
Platform Server therefore turned off encryption or compression for this transfer request. This is an
informational message only. No action is required. The transfer continues normally with the new
encryption type.
●
PGTF3186E Activty tttttttttt Node=nnnnnnnn: Invalid Data STATE - Expecting SEND
state: Data=xxxxxxxx
Explanation:
The Platform Server was executing the Platform Server Responder activity tttttttt for node
nnnnnnnn. The Platform Server detected an internal STATE error. The transfer request is terminated
with errors.
If this problem can be re-created, take a trace (TRON or TCPTRON) and send the results to TIBCO
Technical Support.
●
PGTF3188E tttttttttt xxxxxxxx request denied by CFACCESS yyyyyyyy_OPTION=NEVER
config
Explanation:
The Platform Server responder transaction tttttttttt was running. The Platform Server CFACCESS
processing detected that the yyyyyyyy_OPTION=NEVER parameter was defined. Since the transfer
type matches the CFACCESS type defined, the transfer is terminated with errors and this message is
sent to the remote Platform Server system.
●
PGTF3189E tttttttttt CFACCESS DSN exceeds 54 characters on ROOT or FORCE request
Explanation:
The Platform Server responder transaction tttttttttt was running. The Platform Server CFACCESS
processing attempted to convert the file name because the CFACCESS entry was defined as either
ROOT or FORCE. During the file name conversion, the length of the dataset name exceeded the
maximum length of 54 characters. The transfer is terminated with errors and this message is sent to
the remote Platform Server system.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
97
●
PGTF3191E tttttttttt CFALIAS entry not found for user uuuuuuuu Node nnnnnnnn:
Request Terminated
Explanation:
The Platform Server responder transaction tttttttttt was running. The Platform Server CFALIAS
processing was defined by the CFALIAS DD statement. The Platform Server did not find a match for
user uuuuuuuu and node nnnnnnnn. The default is to not allow the file transfer request. The transfer
is terminated with errors and this message is sent to the remote Platform Server system.
®
See the TIBCO Managed File Transfer Platform Server for z/OS Installation and Operation Guide for more
information on how to configure the CFALIAS parameters.
●
PGTF3192E tttttttttt CFALIAS ALLOW=NO defined for user uuuuuuuu Node nnnnnnnn:
Request Terminated
Explanation:
The Platform Server responder transaction tttttttttt was running. The Platform Server CFALIAS
processing found a match for user uuuuuuuu and node nnnnnnnn on a config statement that was
defined as ALLOW=NO. This indicates that the user was not allowed to perform the requested
function with this node. The transfer is terminated with errors and this message is sent to the remote
Platform Server system.
●
PGTE3193E tttttttttt CFALIAS Substitution length exceeds nn for DSN dddddddddd:
Request Terminated
Explanation:
The Platform Server responder transaction tttttttttt was running. The Platform Server CFALIAS
processing found a match for user and node on a config statement. The Platform Server was
performing variable substitution and detected that the length of the converted file name exceeded
the maximum value of nn bytes. The transfer is terminated with errors and this message is sent to
the remote Platform Server system.
●
PGTE3194E tttttttttt CFALIAS Substitution parameter pppppppp not found for DSN
dddddddddd: Request Terminated
Explanation:
The Platform Server responder transaction tttttttttt was running. The Platform Server CFALIAS
processing found a match for the user and node on a config statement. The Platform Server was
performing variable substitution and found a variable that was not defined internally. Since dataset
names cannot have imbedded % characters, the Platform Server treats this as an error. The transfer
is terminated with errors and this message is sent to the remote Platform Server system.
●
PGTE3195E ttttttttt CFDIR invalid file name defined or file name not defined
Explanation:
A remote Platform Server system requested a dataset catalog or directory list but passed an invalid
file name to the Platform Server. The transfer is terminated and this message is sent back to the
remote Platform Server system.
●
PGTF3197E tttttttttt $CFDIR xxxxx ENQ for DSN dddddddddd failed: File is in use
Explanation:
A Platform Server system requested a dataset catalog or directory list. The Platform Server was
processing this list, found a PDS that matched the criteria, but detected that the file was already in
use. The Platform Server will not process PDS because it cannot get either shared or exclusive access
to the file (xxxxx). It requires this access to be able to read the directory of the PDS. The transfer is
terminated and this message is sent back to the Platform Server system.
●
PGTF3198E tttttttttt $CFDIR File Allocation failed for DSN dddddddddd: Command
execution terminated
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
98
Explanation:
A Platform Server system requested a dataset catalog or directory list. The Platform Server was
processing this list, found a PDS that matched the criteria, but received an error while trying to
allocate the dataset. The dataset must be allocated in order to be able to read the directory of the
PDS. The transfer is terminated and this message is sent back to the Platform Server system.
●
PGTF3199E tttttttttt $CFDIR Read failed with retcode xx Command Execution
terminated
Explanation:
A Platform Server system requested a dataset catalog or directory list. The Platform Server was
processing this list, found a PDS that matched the criteria, but received an error while trying to read
the directory list of the PDS. The transfer is terminated and this message is sent back to the Platform
Server system.
●
PGTE3200E tttttttttt $CFDIR Locate for DSN=dddddddddd exceeds max count of nn
entries
Explanation:
A Platform Server system requested a dataset catalog or directory list. The Platform Server was
processing this list and issued a call to process the list. The number of entries in the catalog that
matched the catalog request exceeded the maximum allowed of nn entries. The transfer is
terminated and this message is sent back to the Platform Server system.
Check the dataset name that is looked up (dddddddd) and make it more specific so that fewer entries
are returned by the catalog lookup program.
●
PGTE3201E tttttttttt $CFDIR CSI Locate failed R15=xx DSN=dddddddddd
Explanation:
A Platform Server system requested a dataset catalog or directory list. The Platform Server was
processing this list and issued a call to process the list. When processing the catalog request, the
Platform Server received return code xx. The transfer is terminated and this message is sent back to
the Platform Server system.
Check the dataset name ddddddd to make sure that it is valid. If the dataset name is valid, contact
TIBCO Technical Support.
●
PGTE3204E tttttttttt Directory limit exceeded for Directory Scan: ddddddddddddddd
Explanation:
The Platform Server processes up to 100 subdirectories on a single directory file transfer request.
This message indicates that a request was received to extract files from a directory, but the Platform
Server detected more than 100 subdirectories in a transfer request. The request is terminated with
errors.
Modify the directory transfer request so that less than 100 subdirectories are detected.
●
PGTE3205E tttttttttt Path name exceeds 256 bytes for file: ffffffffffffffffffffff
Explanation:
The Platform Server was processing a directory request. The Platform Server allows the path name
(fully qualified file name that includes the directory and file name) for a transfer to be up to 256
bytes. While processing the request, the Platform Server detected a file that was more than 256 bytes
long. The Platform Server flags this as an error and terminates the request.
●
PGTE3206E tttttttttt mmmmmmmmmmmmmmmmmmmmm
Explanation:
An error occurred extracting file names from a directory. This message provides a description of the
problem that occurred. When this message is displayed, the request is terminated with errors.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
99
●
PGTE3207E tttttttttt Directory name invalid - Must start with Slash(/):
ddddddddddddd
Explanation:
The Platform Server was extracting files from a directory. The directory name contained a slash (/)
which indicates that the request was a directory request. When processing a directory request, the
Platform Server requires that the directory name start with a slash, but the directory did not start
with a slash. The Platform Server terminates the request with an error.
Update the file name. Make sure that if a directory structure is to be processed, the directory name
must start with a slash.
●
PGTF3208E tttttttttt Directory name invalid - Wildcard cannot be in first
directory: ddddddddddd
Explanation:
The Platform Server was extracting files from a directory. The first qualifier of the directory name
contained a wildcard character. When processing a directory request, the Platform Server requires
that there be no wildcard character in the first directory within the path. The Platform Server
terminates the request with an error. The user should update the file name. Make sure that if a
directory structure is to be processed, the directory name must not contain a wildcard character in
the primary directory.
●
PGTF3209E ttttttttt Directory name invalid - Pathname returned from xxxxxxxx
exceeds 256 bytes
Explanation:
The Platform Server was processing a directory transfer request. The Platform Server allows the
path name (fully qualified file name that includes the directory and file name) for a transfer to be up
to 256 bytes. While processing the request, the Platform Server detected a file that was more than
256 bytes long. The Platform Server flags this as an error and terminates the transfer request.
●
PGTF3212E tttttttttt xxxx Directory Schedule failed RC=nn
Explanation:
The Platform Server attempted to process a directory transfer request. The Platform Server tried to
schedule a request to send or receive (xxxx) one of the files but the schedule request failed with a
non-zero return code. The transfer request that caused the error was not completed. The CONTINUE
parameter determines if additional files are processed.
●
PGTF3213E tttttttttt Receive Directory Failed: Network error on yyyyyyyy request
Explanation:
The Platform Server was processing a directory transfer Receive request. The Platform Server was
contacting the Platform Server system to get a list of files on that system but received a network
error. The transfer request is terminated with errors.
Make sure that the IP Address and IP Port are correct for this request. Also make sure that the
Platform Server nodes are at the V5.5 level or later.
●
PGTF3214E tttttttttt xxxx Directory Failed: Invalid data received from remote
system
Explanation:
The Platform Server was processing a directory transfer Receive request. The Platform Server
successfully contacted the remote system, but the data that was received from the remote system
was invalid. Other messages are displayed that indicate the exact cause of the failure. The transfer
request was terminated with errors.
●
PGTF3216E tttttttttt Directory Transfer failed: PATH name invalid - Must start
with /
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
100
Explanation:
The Platform Server was processing a directory transfer request and was extracting files from a
directory. The directory name contained a slash (/) which indicates that the request was a directory
request. When processing a directory request, the Platform Server requires that the directory name
start with a slash, but the directory did not start with a slash. The Platform Server terminates the
request with an error.
Update the file name. Make sure that if a directory structure is to be processed, the directory name
must start with a slash.
●
PGTF3217E tttttttttt Directory Transfer failed: PATH name invalid - Generic
character cannot be in 1st directory
Explanation:
The Platform Server was processing a directory transfer request and was extracting files from a
directory. The first qualifier of the directory name contained a generic (or wildcard) character. When
processing a directory request, the Platform Server requires that there be no generic or wildcard
character in the first directory within the path. The Platform Server terminates the request with an
error. The transfer request is terminated with errors.
Update the file name. Make sure that if a directory structure is to be processed, the directory name
must not contain a generic/wildcard character in the primary directory.
●
PGTF3219E tttttttttt Directory Transfer: File count exceeded limit - Make filter
parameters more restrictive
Explanation:
The Platform Server was performing a directory transfer Receive. The Platform Server extracted the
file list from the remote system and was saving this information. The number of transfers that the
Platform Server accepts is around 2000, but depends on the length of the file names. For shorter file
names, it will accept more than 2000 and if the file names are long, it will process less than 2000 file
transfers. The transfer request is terminated with errors.
●
PGTF3220E tttttttttt FMH7 received from partner: Message follows
Explanation:
The Platform Server was performing a directory transfer receive. The Platform Server was extracting
the file list from the Platform Server node but received an error from the remote system. A
descriptive error message follows this message.
Make sure that the Platform Server system is at the 5.5 level of higher. The transfer request is
terminated with errors.
●
PGTF3221E tttttttttt FMH7 received from partner: Error processing FMH7 data
Explanation:
The Platform Server was performing a directory transfer receive. The Platform Server was extracting
the file list from the Platform Server node but received an error from the remote system. While
trying to receive the descriptive error, the Platform Server detected a network error and was unable
to receive the message.
make sure that the Platform Server system is at the 5.5 level of later. The transfer request is
terminated with errors.
●
PGTF3224E tttttttttt LocalFile PDS not found in Catalog - DSN=dddddddddddd
Explanation:
The Platform Server was performing a directory transfer Send for a PDS. The Platform Server
looked up the file in the z/OS catalog but was not able to find the file in the catalog. The user should
check the file name to make sure that it was defined correctly. The transfer request is terminated
with errors.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
101
●
PGTF3225E tttttttttt LocalFile not PDS for member transfer - DSN=ddddddddddddd
Explanation:
The Platform Server was performing a directory transfer send for a PDS. The Platform Server looked
up the file in the z/OS catalog and was able to find the file in the catalog, but the file was not a PDS
file. The transfer request is terminated with errors.
Check the file name to make sure that it was defined correctly.
●
PGTF3228E aaaaaaaaaa: RocketStream request invalid for SNA destination nnnnnnnn
Explanation:
The Platform Server was initiating a request and detected that this request was defined as a
RocketStream request. However, the node definition was defined as SNA, and RocketStream does
not process SNA requests. The transfer is terminated with an error.
●
PGTF3229E aaaaaaaaaa: RocketStream RSHOST not defined for destination nnnnnnnn
Explanation:
The Platform Server was initiating a request and detected that this request was defined as a
RocketStream request. However, the RSHOST parameter was not defined by either the GLOBAL
RSHOST or the file transfer RSHOST definitions. The transfer is terminated with an error.
●
PGTF3230E aaaaaaaaaa: Send Directory Token processing complete: Node=nnnnnnnn
RF=ffffffff
Explanation:
The user specified a token in the NODE parameter of an initiator file transfer. This capability allows
you to compute the node name from a component of the Local File Name. This message is an
information message that shows the new node name that was computed for activity aaaaaaaaaa.
●
PGTF3233E Activty aaaaaaaaaa nnnnnnnn GLOBAL FIPS140 mode set but Request was not
SSL and no NODE definition found
Explanation:
An incoming transfer request was detected by the Platform Server z/OS system. The GLOBAL was
running with an FIPS 140 security policy. However, the request was not SSL, and no node definition
was found. The request is terminated with errors.
When running in FIPS 140 mode, all requests must be SSL unless a node definition
overrides the FIPS setting.
●
PGTF3234E Activty aaaaaaaaaa nnnnnnnn GLOBAL FIPS140 mode set but Request was not
SSL and NODE was set to FIPS mode
Explanation:
An incoming transfer request was detected by the Platform Server z/OS system. The GLOBAL was
running with an FIPS 140 security policy. However, the request was not SSL and a node definition
was found, but the node definition was set to FIPS mode. The request is terminated with errors.
When running in FIPS 140 mode, all requests must be SSL unless a node definition
overrides the FIPS setting.
●
PGTF3235E aaaaaaaaaa nnnnnnnn ENCRYPT must be AES when GLOBAL FIPS140 is set:
Transfer terminated
Explanation:
An incoming transfer request was detected by the Platform Server z/OS system. The GLOBAL was
running with na FIPS 140 security policy. However, the request was not initiated with AES
encryption. The request is terminated with errors.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
102
When running in FIPS 140 mode, AES encryption is required.
●
PGTF3236E tttttttttt Request terminated by EXIT04 (Pre-Allocation) Node=nnnnnnnn
LocalFile: ffffffffffff
Explanation:
Exit program FUSEX04 was turned on by the GLOBAL EXIT04 parameter. The return code from
FUXEX04 indicated that the transfer be terminated. This message indicates that transfer request
tttttttttt for Node nnnnnnnn was terminated. The local file associated with the request is ffffffffff.
●
PGTF3237E tttttttttt Directory Receive File created too long LF=llllll
Explanation:
A directory receive was being performed. MFT sent a request to the transfer partner to list the files
eligible to transfer. The length of the file name (llllll) was greater than 255 characters. Since MFT
supports a maximum file length of 255 characters, MFT returns an error and terminates the transfer.
●
PGTE3248E tttttttttt: Local CRC=cccccccc Partner CRC=cccccccc: CRC Mismatch Transfer terminated with error
Explanation:
Platform Server was configured to perform CRC checking; the partner also supported CRC
processing. At the end of transfer, the CRC computed by the sender did not match the CRC
computed by the receiver. The transfer is terminated with an error
●
PGTE3254E tttttttttt: CUNLCNV Not loaded from SYS1.CSSLIB: Transfer terminated
Explanation:
The transfer attempted to perform a UNICODE code conversion but module CUNLNV was not
loaded. Module CUNLCNV is required to perform UNICODE code conversion. The transfer is
terminated with an error. Message PGTS0208E should have been displayed at startup to indicate
that code conversion is disabled due to a load error.
●
PGTE3255E tttttttttt: CCSID format invalid: Must be: CC:12345:12345
Explanation:
The LCT (LOCALCTFILE) parameter was defined with a code conversion starting with "CC:". The
format of this parameter is: CC:12345:12345. All five digits must be defined for both the source and
the target CCSID when using the LCT parameter with the "CC:" format. The transfer is terminated.
●
PGTE3256E tttttttttt: CCSID invalid - Not supported: ccccc
Explanation:
The LCT (LOCALCTFILE) parameter was defined with an invalid code conversion table number
(ccccc). The transfer is terminated.
●
PGTE3258E tttttttttt: Compression Interface not started: Transfer terminated
Explanation:
The Platform Server attempted to perform ZLIB or LZ compression, but the compression
environment was not initialized or had shut down unexpectedly. Additional messages should be
displayed with more detailed explanation of why the initialization failed.
●
PGTE3259E tttttttttt: Compression StartThread FAILED: Retcode=nn: transfer
terminated
Explanation:
The Platform Server attempted to perform ZLIB or LZ compression, but the compression start
thread failed.
Contact TIBCO Technical Support and send the started task logs to TIBCO Technical Support.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
103
●
PGTF3505E SSL ClientDN validation failed: Request terminated
Explanation:
An SSL request was received from node nnnnnnnn. The Platform Server was checking the
Distinguished Name (DN) received and found an error. Additional messages will be displayed with
more information about the error. Processing of the request is terminated.
●
PGTF3506E SSL ClientDN invalid: Must start with /
Explanation:
An SSL request was received from node nnnnnnnn. The Platform Server was checking the
Distinguished Name (DN) received, and found an error. Additional messages will be displayed with
more information about the error. Processing of the request is terminated.
●
PGTF3507E SSL ClientDN invalid: must be /CN/L/ST/C/OU/O/SN
Explanation:
An SSL request was received from node nnnnnnnn. The Platform Server was checking the
Distinguished Name (DN) received, and found an error. The Distinguished Name (DN) checking
determined that an invalid component of the DN was found. The only valid components are: /
DN(Comman Name); /L (Locality); /ST (State); /C (Country); /OU (Organizational Unit); /O
(Organization); and /SN (Serial Number). Processing of the request is terminated.
●
PGTE3511E tttttttttt: TLS STARTTHREAD FAILED: Retcode=nn: transfer terminated
Explanation:
The Platform Server attempted TLS communication, but the TLS start thread failed.
Contact TIBCO Technical Support and send the started task logs to TIBCO Technical Support.
●
PGTE3512E tttttttttt: TLS Interface not started: TLS transfer terminated
Explanation:
The Platform Server attempted to TLS communication, but the TLS interface was not started. If a
TLS port was configured, additional messages should be displayed with detailed explanation of
why the TLS initialization failed.
Make sure that the Platform Server is listening on one or more TLS ports; TLS initialization only
occurs when the Platform Server is configured to listen on a port.
●
PGTE3521E SSLAUTH Error: Expecting / on Record xxxx: Record follows
Explanation:
The SSL configuration was processing the SSLAUTH file and found a problem with the configuration
data. The program was expecting a / on record xxxx of the file. The record in error will be displayed
following this message. This entry in the SSLAUTH file will not be enabled.
●
PGTE3533E SSL processing terminated due to errors: Check previous messages for
exact cause
Explanation:
The Platform Server SSL processing was terminated with errors. This message is displayed after the
detail messages that give more detailed explanation of the actual error.
●
PGTE3534E SSL INIT Failed CID Mismatch CID=aaaaaaaaaa bbbbbbbbb: SSL Processing
terminated
Explanation:
The Platform Server was communicating with its SSL task and received invalid data from the task.
The Platform Server SSL processing is terminated. If this problem continues, bring up the Platform
Server SSL task with SSLDEBUG=HIGH parm.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
104
®
See TIBCO Managed File Transfer Platform Server for z/OS Installation and Operation Guide for more
information on the SSLDEBUG parm option.
●
PGTE3535E SSL INIT Error: Retcode=rr Errno=nn: SSL Processing terminated
Explanation:
The Platform Server received an error during the SSL initialization processing. The error code that
was received was rr, while the errno was nn. The following message should give more information
about the actual cause of the error. The Platform Server SSL processing is terminated.
If this problem continues, bring up the Platform Server SSL task with the SSLDEBUG=HIGH parm.
®
See the TIBCO Managed File Transfer Platform Server for z/OS Installation and Operation Guide for more
information on the SSLDEBUG parm option.
●
PGTE3536E tttttttttttttttttttttttttttttttttttttttttttt
Explanation:
The Platform Server received an error during the SSL initialization processing. This message shows
the reason that the SSL processing failed.
●
PGTE3537E SSL INIT Error: No response received received within nnn seconds: SSL
Processing terminated
Explanation:
The Platform Server started the SSL subtask, and was waiting for a response to the startup. The
Platform Server waited the maximum amount of time allowed (nnn seconds) and did not receive a
response. The Platform Server then terminates the SSL task, and SSL processing terminates. Make
sure that any SSL libraries (GSK.GSKLOAD) are allocated to the STEPLIB.
●
PGTE3538E SSL INIT Error: SSL Subtask Terminated Prematurely: SSL Processing
terminated
Explanation:
The Platform Server started the SSL subtask, but before it could start the SSL communication, the
subtask ended. The Platform Server SSL processing terminates. Make sure that any SSL libraries
(GSK.GSKLOAD) are allocated to the STEPLIB.
●
PGTE3539E Activity tttttttttt NODE nnnnnnnn: SSL Subtask terminated prematurely:
SSL Processing terminated
Explanation:
The Platform Server attempted to perform SSL processing but detected that the SSL subtask had
terminated.
If this problem re-occurs, contact TIBCO Technical Support.
●
PGTE3801E Activity tttttttttt xxxx_ACTION invalid: No ACTION data passed
Explanation:
The Platform Server Transfer Action processing was being performed for activity tttttttttt. The action
was invalid because no data was passed to the action. Therefore, the program could not be called.
The transfer continues execution. This message does not affect the outcome of the file transfer.
●
PGTE3802E Activity tttttttttt xxxx_ACTION invalid: Program name exceeds 8 bytes
Explanation:
The Platform Server Transfer Action processing was being performed for activity tttttttttt. The action
was invalid because the program name exceeded 8 bytes. The program name should be the first
parameter after the CALLPGM or CALLJCL parameter and must be from 1 to 8 bytes. It must be
delimited from the data by a space. The transfer continues execution. This message does not affect
the outcome of the file transfer.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
105
●
PGTE3803E Activity tttttttttt xxxx_ACTION invalid: Load failed for program
pppppppp
Explanation:
The Platform Server Transfer Action processing was being performed for activity tttttttttt. The action
was invalid because the program name defined in the CALLJCL or CALLPGM parameter was invalid.
The Platform Server was unable to load program pppppppp. The transfer continues execution. This
message does not affect the outcome of the file transfer.
Make sure that the program is in a library available to the Platform Server started task.
●
PGTE3804E Activity tttttttttt xxxx_ACTION invalid: Program pppppppp abended with
code aaa
Explanation:
The Platform Server Transfer Action processing was being performed for activity tttttttttt. Program
pppppppp was called, but the program abended with abend code aaa. Other messages will display
the PSW and registers of the abending program. The transfer continues execution. This message
does not affect the outcome of the file transfer.
●
PGTE3805E Activity tttttttttt xxxx_ACTION invalid: COMMAND not supported
Explanation:
The Platform Server Transfer Action processing was being performed for activity tttttttttt. The action
request was COMMAND, but the Platform Server for z/OS does not support Command processing.
The transfer continues execution. This message does not affect the outcome of the file transfer.
●
PGTE3806E Activity tttttttttt xxxx_ACTION Transfer Racroute failed: ACTION
processing terminated
Explanation:
The Platform Server Transfer Action processing was being processed for activity tttttttttt. The
Platform Server attempted to validate the userid and password but realized that a prior userid/
password validation failed. Therefore, no program could be called. The transfer continues execution.
This message does not affect the outcome of the file transfer.
●
PGTE3807E Activity tttttttttt xxxx_ACTION File Error on DSN=dsn(member): Error
message follows
Explanation:
The Platform Server Transfer Action processing was being performed for activity tttttttttt. The
Platform Server attempted to submit a job into the internal reader, but received an error performing
file I/O. Subsequent messages will detail the reason for the error. The transfer continues execution.
This message does not affect the outcome of the file transfer.
●
PGTE3808E Activity tttttttttt xxxx_ACTION DSN invalid: DSN null or exceeds 44
characters: Job not submitted
Explanation:
The Platform Server Transfer Action processing was being performed for activity tttttttttt. The
Platform Server attempted to submit a job into the internal reader, but the DSN of the source JCL
was invalid. The transfer continues execution. This message does not affect the outcome of the file
transfer.
●
PGTE3809E Activity tttttttttt xxxx_ACTION MEMBER invalid: Member exceeds 8
characters: Job not submitted
Explanation:
The Platform Server Transfer Action processing was being performed for activity tttttttttt. The
Platform Server attempted to submit a job into the internal reader, but the MEMBER of the source
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
106
JCL was invalid. The transfer continues execution. This message does not affect the outcome of the
file transfer.
●
PGTE3810E Activity tttttttttt xxxx_ACTION SUBMIT error: MEMBER defined but
JOB_SUBMIT_DSN not defined: Job not submitted
Explanation:
The Platform Server Transfer Action processing was being performed for activity tttttttttt. The
Platform Server attempted to submit a job into the internal reader. Only the member name was
defined. In this case, the Platform Server got the DSN from the GLOBAL JOB_SUBMIT_DSN but this
parameter was not defined. The transfer continues execution. This message does not affect the
outcome of the file transfer.
●
PGTE3811E Activity tttttttttt xxxx_ACTION RACROUTE failed: mmmmmmm SAF=rr RC=qq
Explanation:
The Platform Server Transfer Action processing was being performed for activity tttttttttt. The
Platform Server attempted to establish the security environment using the RACROUTE macro, but
the RACROUTE VERIFY request failed. The return codes and a text message indicating the reason
for the failure were also defined. The transfer continues execution. This message does not affect the
outcome of the file transfer.
●
PGTE3813E Activity tttttttttt xxxx_ACTION COMMAND error: PPA COMMAND processing
denied by CFACCESS NEVER config
Explanation:
The Platform Server was executing a PPA (Post Processing Action) request. PPA was checking the
config file and detected a match. The entry was defined with COMMAND_OPTION=NEVER.
The PPA Command is not executed. The file transfer is not affected by this message.
CFACCESS
●
PGTE3814E Activity tttttttttt xxxx_ACTION SUBMIT error: PPA SUBMIT processing
denied by CFACCESS NEVER config
Explanation:
The Platform Server was executing a PPA (Post Processing Action) request. PPA was checking the
CFACCESS config file and detected a match. The entry was defined with the SUBMIT_OPTION=NEVER.
The PPA SUBMIT is not performed. The file transfer is not affected by this message.
●
PGTE3815E Activity tttttttttt xxxx_ACTION SUBMIT error: SUBMIT member name too
long for CFACCESS ROOT config
Explanation:
The Platform Server was executing a PPA (Post Processing Action) SUBMIT request. PPA was
checking the CFACCESS config 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
transfer file name exceeded the maximum member length of 8 bytes. The PPA SUBMIT is not
performed. The file transfer is not affected by this message.
●
PGTE3817E PPA Substitution length exceeds nn for PPA Data xxxxxxxx : PPA not
performed
Explanation:
The Platform Server was performing parameter substitution for the PPA (Post Processing Actions)
fields. The PPA substitution caused the length of the PPA data to exceed the maximum allowed of
nn bytes. PPA processing is not performed for this PPA data. The transfer is not affected by this
message.
●
PGTE3818E PPA Substitute parameter pppppppp not found: PPA not performed
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
107
The Platform Server was performing parameter substitution for the PPA (Post Processing Actions)
fields. The PPA substitution detected that substitute variable (pppppppp) was not found. The
substitution variable is ignored and the Platform Server PPA substitution processing continues with
the next byte in the PPA data. The transfer is not affected by this message.
●
PGTE3819E tttttttttt: PPA SUBMIT failed - Shared ENQ Failed for DSN:
dddddddddddddd
Explanation:
A PPA was defined to SUBMIT a job into the internal reader. In order to submit the JOB, the dataset
(dddddd) that contains the JCL must be allocated. This message indicates that an ENQ for DSN
ddddddd failed. The PPA SUMIT will not be performed. An accompanying message will display the
job that is holding the ENQ for this DSN.
●
PGTE3830E FUSUTIL xxxxxxxx failed: Cannot get yyyyyyyy access to DSN=dddddddd
Explanation:
The Platform Server was processing the Platform Server for z/OS FUSUTIL utility and attempted to
rename, delete or see if a file exists. The Platform Server attempted to get either shared or exclusive
access to dataset ddddd but could not get this access because the dataset was in use. If FUSUTIL is
executed as a result of a PPA request, the PPA request terminates with an error and the transfer is
not affected. If FUSUTIL is executed as part of the Platform Server Command processing, the
request is terminated and this message sent back to the Platform Server system.
●
PGTE3831E FUSUTIL xxxxxxxx error on DSN dddddddd: not authorized to yyyyyyy the
dataset
Explanation:
The Platform Server was processing the Platform Server for z/OS FUSUTIL utility and attempted to
rename or delete a dataset. The Platform Server attempted to either catalog or uncatalog a dataset
but could not do this because it received an error indicating that it was not authorized to perform
this function. FUSUTIL processing is terminated. If FUSUTIL is executed as a result of a PPA
request, the PPA request terminates with an error and the transfer is not affected. If FUSUTIL is
executed as part of the Platform Server Command processing, the request is terminated and this
message sent back to the Platform Server system.
●
PGTE3832E FUSUTIL xxxxxxxx yyyyyyyy Error: tttttttttttttttt - RC=rr Reason=ss
Explanation:
The Platform Server was processing the Platform Server for z/OS FUSUTIL utility and attempted to
rename or delete a dataset. The Platform Server attempted to either catalog, uncatalog, delete or
rename a dataset, but could not do this because it received an error. A text message is displayed that
gives more information about the error. FUSUTIL processing is terminated. If FUSUTIL is executed
as a result of a PPA request, the PPA request terminates with an error and the transfer is not
affected. If FUSUTIL is executed as part of the Platform Server Command processing, the request is
terminated and this message sent back to the Platform Server system.
●
PGTE3833E FUSUTIL xxxxxxxx yyyyyyyy failed - DSN not found: dddddddddddd
Explanation:
The Platform Server was processing the Platform Server for z/OS FUSUTIL utility and attempted to
rename, delete, or see if a dataset exists. The Platform Server was checking the catalog to see if the
file exists, but received an error that indicated that the file did not exist. FUSUTIL processing is
terminated. If FUSUTIL is executed as a result of a PPA request, the PPA request terminates with an
error and the transfer is not affected. If FUSUTIL is executed as part of the Platform Server
Command processing, the request is terminated and this message sent back to the Platform Server
system.
●
PGTE3834E FUSUTIL xxxxxxxx yyyyyyyy failed trying to get new DSN for
GDG=gggggggggg
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
108
Explanation:
The Platform Server was processing the Platform Server for z/OS FUSUTIL utility and attempted to
RENAME a dataset. The target of the rename was a GDG. The Platform Server was issuing a call to
get the new GDG name for the dataset, but received an error on this call. Check to make sure that
GDG processing is allowed for DSN gggggggg. FUSUTIL processing is terminated. If FUSUTIL is
executed as a result of a PPA request, the PPA request terminates with an error and the transfer is
not affected. If FUSUTIL is executed as part of the Platform Server Command processing, the
request is terminated and this message sent back to the Platform Server system.
●
PGTE3835E FUSUTIL Command ccccccc either missing or invalid: Must be R, RENAME,
D, DELETE, E, EXIST
Explanation:
The Platform Server was processing the Platform Server for z/OS FUSUTIL. While parsing the
FUSUTIL command line data, the Platform Server did not detect the operation to perform. Valid
operations are R, RENAME, D, DELETE, E, EXIST. If FUSUTIL is executed as a result of a PPA
request, the PPA request terminates with an error and the transfer is not affected. If FUSUTIL is
executed as part of the Platform Server Command processing, the request is terminated and this
message sent back to the Platform Server system.
●
PGTE3836E FUSUTIL RENAME new DSN has invalid GDG name - Must be (+1): dddddddddd
Explanation:
The Platform Server was processing the Platform Server for z/OS FUSUTIL. While parsing the
FUSUTIL command line data, the Platform Server detected that a dataset was to be renamed to a
GDG, but the GDG dataset was not defined as +1. The only way that FUSUTIL will rename a file to a
GDG is if the GDG is defined as +1. If FUSUTIL is executed as a result of a PPA request, the PPA
request terminates with an error and the transfer is not affected. If FUSUTIL is executed as part of
the Platform Server Command processing, the request is terminated and this message sent back to
the Platform Server system.
●
PGTE3837E FUSUTIL xxxxxxxx failed yyyyyyyy parameter not defined
Explanation:
The Platform Server was processing the Platform Server for z/OS FUSUTIL. While parsing the
FUSUTIL command line data, the Platform Server detected that one of the required parameters for a
RENAME, DELETE, EXIST was missing. Field yyyyyyyy defined the field that was missing. If
FUSUTIL is executed as a result of a PPA request, the PPA request terminates with an error and the
transfer is not affected. If FUSUTIL is executed as part of the Platform Server Command processing,
the request is terminated and this message sent back to the Platform Server system.
●
PGTE3838E FUSUTIL Request failed: File Name invalid or exceeds 44 characters
Explanation:
The Platform Server was processing the Platform Server for z/OS FUSUTIL. While parsing the
FUSUTIL command line data, the Platform Server detected that one of the file names exceeded the
maximum length of 44 characters. If FUSUTIL is executed as a result of a PPA request, the PPA
request terminates with an error and the transfer is not affected. If FUSUTIL is executed as part of
the Platform Server Command processing, the request is terminated and this message sent back to
the Platform Server system.
●
PGTE3839E FUSUTIL About to DELETE DSN: dddddddd
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 delete a dataset. The dataset that is to be deleted is
ddddddd. This message is displayed for information purposes only.
●
PGTE3841E FUSUTIL xxxxxxxx invalid for VSAM DSN: dddddddddddd
Explanation:c
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
109
The Platform Server was processing the Platform Server for z/OS FUSUTIL utility. The Platform
Server detected that one of the files be renamed or delete was a VSAM dataset. THE FUSUTIL utility
does not support VSAM datasets. The dataset that could not be renamed is ddddddd. If FUSUTIL is
executed as a result of a PPA request, the PPA request terminates with an error and the transfer is
not affected. If FUSUTIL is executed as part of the Platform Server Command processing, the
request is terminated and this message sent back to the Platform Server system.
●
PGTE3842E FUSUTIL xxxxxxxx invalid for TAPE DSN: dddddddddddd
Explanation:
The Platform Server was processing the Platform Server for z/OS FUSUTIL utility. The Platform
Server detected that one of the files be renamed or delete was a TAPE dataset. THE FUSUTIL utility
does not support TAPE datasets. The dataset that could not be renamed is ddddddd. If FUSUTIL is
executed as a result of a PPA request, the PPA request terminates with an error and the transfer is
not affected. If FUSUTIL is executed as part of the Platform Server Command processing, the
request is terminated and this message sent back to the Platform Server system.
●
PGTE3851E CFACCESS End of File received - expecting continuation record
Explanation:
The Platform Server received an end of file while it was waiting for a continuation record. The last
configuration entry is ignored because it is incomplete.
Review the CFACCESS configuration file and make sure that the last entry is valid.
●
PGTE3852E CFACCESS NODE and IPADDR parameters are mutually exclusive: Record nnnn
Explanation:
The Platform Server was reading the CFACCESS configuration file, and detected that the NODE and
parameters were both entered in the same entry. These parameters are mutually exclusive.
The configuration entry that caused the problem is ignored.
IPADDR
Review the CFACCESS entry that ends at record nnnn and remove one of the parameters.
●
PGTE3853E CFACCESS USERID or NODE/IPADDR parameters must be entered: Record: nnnn
Explanation:
The Platform Server was reading the CFACCESS configuration file, and detected that neither the
USERID nor NODE/IPADDR parameters were entered. Either the USERID or NODE/IPADDR parameter
must be entered for each entry. Review the CFACCESS entry that ends at record nnnn and add one of
the parameters. The configuration entry that caused the problem is ignored.
●
PGTE3854E CFACCESS Invalid parameter pppppppp: Incorrect length or incorrect
parameter: Record nnnn
Explanation:
The Platform Server was reading the CFACCESS configuration file, and detected an invalid parameter
was entered on record nnnn. It could be an invalid parameter, or the length of the parameter may be
incorrect. The configuration entry that caused the problem is ignored.
●
PGTE3855E CFACCESS too many parameters entered for one CFACCESS request: Record
nnnn
Explanation:
The Platform Server was reading the CFACCESS configuration file, and detected that too many
parameters were entered on record nnnn. It is possible that two entries were processed together due
to a continuation error. The configuration entry that caused the problem is ignored.
●
PGTE3856E Input data: ddddddddddddddddddddd
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
110
The Platform Server was reading the CFACCESS configuration file, and detected an error. This
message displays the data that was in error. A prior message indicates the cause of the error.
●
PGTE3857E CFACCESS Open failed on DD CFACCESS - Bypassing CFACCESS File
processing
Explanation:
The Platform Server attempted to open the CFACCESS DD statement, but the open failed. The
parameter file is not processed, and as such no CFACCESS checking is performed.
CFACCESS
Review the accompanying z/OS messages to determine the cause of the failure.
●
PGTE3859E CFACCESS IPADDR Invalid IPV4 or IPV6 address: Record nn
Explanation:
The Platform Server was processing CFACCESS configuration file record nnnn. When processing the
Message IPADDR parameter, the Platform Server detected that the IP Address defined was not in the
proper format, either dotted decimal for IPV4 or colon delimited for IPV6. The configuration entry
that caused the problem is ignored.
Correct the IPADDR parameter, and refresh the CFACCESS file through the Platform Server
operator command.
CFACCESSREFRESH
●
PGTE3860E CFACCESS SOURCE parameter must be INITIATOR, RESPONDER or BOTH: Record
nnnn
Explanation:
The Platform Server was processing CFACCESS configuration file record nnnn. When processing the
SOURCE parameter, the Platform Server detected invalid data. The only values allowed are
INITIATOR, RESPONDER, or BOTH. The configuration entry that caused the problem is ignored.
Correct the SOURCE parameter, and refresh the CFACCESS file through the Platform Server
CFACCESSREFRESH operator command.
●
PGTE3861E CFACCESS SEND_OPTION must be ROOT, FORCE, ALLOW, REJECT, NEVER or USE:
Record nnnn
Explanation:
The Platform Server was processing CFACCESS configuration file record nnnn. While processing the
SEND_OPTION parameter the Platform Server detected invalid data. The only values allowed are
ROOT, FORCE, ALLOW, REJECT, NEVER or USE. The configuration entry that caused the problem is
ignored.
Correct the SEND_OPTION parameter, and refresh the CFACCESS file through the Platform Server
CFACCESSREFRESH operator command.
●
PGTE3864E CFACCESS SUBMIT_OPTION must be ALLOW, ROOT or NEVER: Record nnnn
Explanation:
The Platform Server was processing CFACCESS configuration file record nnnn. When processing the
SUBMIT_OPTION parameter the Platform Server detected invalid data. The only values allowed are
ALLOW, ROOT or NEVER. The configuration entry that caused the problem is ignored.
Correct the SUBMIT_OPTION parameter, and refresh the CFACCESS file through the Platform Server
operator command.
CFACCESSREFRESH
●
PGTE3865E CFACCESS SEND_OPTION on OS/390 does not support ALLOW or REJECT: Record
nnnn
Explanation:
The Platform Server was processing CFACCESS configuration file record nnnn. Wen processing the
parameter, the Platform Server detected invalid data. The values ALLOW and REJECT
SEND_OPTION
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
111
are not supported on the Platform Server for z/OS. The configuration entry that caused the problem
is ignored.
Correct the SEND_OPTION parameter, and refresh the CFACCESS file through the Platform Server
operator command.
CFACCESSREFRESH
●
PGTE3866E CFACCESS RECEIVE_OPTION on OS/390 does not support ALLOW or REJECT:
Record nnnn
Explanation:
The Platform Server was processing CFACCESS configuration file record nnnn. While processing the
RECEIVE_OPTION parameter, the Platform Server detected invalid data. The values ALLOW and
REJECT are not supported on the Platform Server for z/OS. The configuration entry that caused the
problem is ignored.
Correct the RECEIVE_OPTION parameter, and refresh the CFACCESS file through the Platform Server
CFACCESSREFRESH operator command.
●
PGTE3867E CFACCESS SEND_DIR required when SEND_OPTION is ROOT or FORCE: Record
nnnn
Explanation:
The Platform Server was processing CFACCESS configuration file and reached the end of the entry at
record nnnn. The Platform Server detected that the SEND_OPTION was specified as FORCE or ROOT,
but the SEND_DIR parameter was not defined. SEND_DIR is required when SEND_OPTION is FORCE
or ROOT. The configuration entry that caused the problem is ignored.
Correct the SEND_OPTION parameter, and refresh the CFACCESS file through the Platform Server
operator command.
CFACCESSREFRESH
●
PGTE3868E CFACCESS RECEIVE_DIR required when RECEIVE_OPTION is ROOT or FORCE:
Record nnnn
Explanation:
The Platform Server was processing CFACCESS configuration file and reached the end of the entry
at record nnnn. The Platform Server detected that the RECEIVE_OPTION was specified as FORCE or
ROOT, but the RECEIVE_DIR parameter was not defined. RECEIVE_DIR is required when
RECEIVE_OPTION is FORCE or ROOT. The configuration entry that caused the problem is ignored.
Correct the RECEIVE_OPTION parameter, and refresh the CFACCESS file through the Platform Server
CFACCESSREFRESH operator command.
●
PGTE3869E CFACCESS SUBMIT_DIR required when SUBMIT_OPTION is ROOT: Record
Explanation:
The Platform Server was processing CFACCESS configuration file and reached the end of the entry at
record nnnn. The Platform Server detected that the SUBMIT_OPTION was specified as ROOT, but the
SUBMIT_DIR parameter was not defined. SUBMIT_DIR is required when SUBMIT_OPTION is ROOT. The
configuration entry that caused the problem is ignored.
Correct the SUBMIT_OPTION parameter, and refresh the CFACCESS file through the Platform Server
operator command.
CFACCESSREFRESH
●
PGTE3881E CFALIAS End of File received - expecting continuation record
Explanation:
The Platform Server was processing the CFALIAS configuration file. The last record in the file had a
continuation character that indicated that there were more records to be processed. But when
reading the next record, the Platform Server received an End Of File indicator. The last record is
marked as an error and is not processed.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
112
Review the CFALIAS configuration file and make sure that the last record is defined correctly. You
can use the CFALIASREFRESH operator command to refresh the CFALIAS configuration file once the
error is resolved.
●
PGTE3882E CFALIAS NODE and IPADDR parameters are mutually exclusive: Record nn
Explanation:
The Platform Server was processing the CFALIAS configuration file. Both the IPADDR and NODE
parameters were defined for the same entry, but these parameters were mutually exclusive. The
entry is marked as an error and is not processed.
Remove either the NODE or IPADDR parameter on the record in error. The field nn defines the record
that is in error. You can use the CFALIASREFRESH operator command to refresh the CFALIAS
configuration file once the error is resolved.
●
PGTE3883E CFALIAS USERID or NODE/IPADDR parameters must be entered: Record: nn
Explanation:
The Platform Server was processing the CFALIAS configuration file. Neither the IPADDR nor the NODE
parameters were defined for an entry. Either NODE or IPADDR must be defined for every entry in the
CFALIAS config file. The entry is marked as an error and is not processed.
Add either the NODE or IPADDR parameter on the record in error. The field nn defines the record that
is in error.
Use the CFALIASREFRESH operator command to refresh the CFALIAS configuration file after the error
is resolved.
●
PGTE3884E CFALIAS Invalid parameter pppppppp: Incorrect length or incorrect
parameter: Record nn
Explanation:
The Platform Server was processing the CFALIAS configuration file. Parameter pppppppp was not
recognized or has an invalid length. The entry is marked as an error and is not processed.
Make sure that the parameter is entered correctly with correct delimiters (comma) and the equal
sign separates the parameter from the configured value. The field nn defines the record that is in
error. Use the CFALIASREFRESH operator command to refresh the CFALIAS configuration file after
the error is resolved.
●
PGTE3885E CFALIAS too many parameters entered for one CFALIAS request: Record nn
Explanation:
The Platform Server was processing the CFALIAS configuration file. The Platform Server detected
that too many parameters were defined for a single entry. This is most likely because the user
incorrectly added the continuation character (comma) at the end of the entry, so the Platform Server
continued processing the next record as a part of the previous entry. The entry is marked as an error
and is not processed.
Make sure that the parameter is entered correctly with correct delimiters (comma) and the equal
sign separates the parameter from the configured value. Make sure that there is no delimiter at the
end of the entry in this table. The field nn defines the record that is in error. Use the
CFALIASREFRESH operator command to refresh the CFALIAS configuration file after the error is
resolved.
●
PGTE3886E Input data: ttttttttttttttttttttttttttttt
Explanation:
The Platform Server was processing the CFALIAS configuration file and detected an error. This
message displays the record that was in error. It is always paired with another message that
indicates the cause of the error.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
113
Refer to that message to determine why the message is in error. In some cases, this message will
point to the last record in a configuration entry. It may not actually point to the record in error if the
error is detected when the Platform Server is validating the parameters to make sure that all
parameter were entered and that mutually exclusive parameters were not entered incorrectly.
●
PGTE3887E CFALIAS Open failed on DD CFALIAS - Bypassing CFALIAS File processing
Explanation:
The Platform Server was processing the CFALIAS configuration file and attempted to open the
CFALIAS DD statement. The Platform Server received an error opening the CFALIAS config file.
Check to see if the member name in the CFALIAS config file is correct and if the Platform Server is
authorized to access the file defined by the CFALIAS DD statement. CFALIAS processing is
bypassed. No CFALIAS processing will be performed for any transfers. Correct the problem and
restart the Platform Server.
●
PGTE3889E CFALIAS IPADDR: Invalid IPV4 or IPV6 address: Record nn
Explanation:
The Platform Server was processing the CFALIAS configuration file. The Platform Server detected
that an IPADDR parameter had an invalid format for the IP Address. The IPADDR parameter value
must be in standard dotted decimal format for IPV4 and colon delimited for IPV6. The entry is
marked as an error and is not processed.
Make sure that the IPADDR parameter has a correct format IP Address. The field nn defines the
record that is in error. You can use the CFALIASREFRESH operator command to refresh the CFALIAS
configuration file once the error is resolved.
●
PGTE3890E CFALIAS SOURCE parameter must be INITIATOR, RESPONDER or BOTH: Record
nn
Explanation:
The Platform Server was processing the CFALIAS configuration file. The Platform Server detected
that an invalid value was entered for the SOURCE parameter. Valid parameter values are INITIATOR,
RESPONDER, or BOTH. The entry is marked as an error and is not processed. The field nn defines the
record that is in error.
Use the CFALIASREFRESH operator command to refresh the
error is resolved.
●
CFALIAS
configuration file after the
PGTE3891E CFALIAS TYPE parameter must be SEND, RECEIVE or BOTH: Record nn
Explanation:
The Platform Server was processing the CFALIAS configuration file. The Platform Server detected
that an invalid value was entered for the TYPE parameter. Valid parameter values are SEND,
RECEIVE, or BOTH. The entry is marked as an error and is not processed. The field nn defines the
record that is in error.
Use the CFALIASREFRESH operator command to refresh the CFALIAS configuration file after the error
is resolved.
●
PGTE3892E CFALIAS xxxxxxxx parameter required but missing: Record nn
Explanation:
The Platform Server was processing the CFALIAS configuration file. The Platform Server detected
that a required parameter was missing. Parameter xxxxxxxx was not entered. Make sure that
parameter xxxxxxxx is entered correctly with correct delimiters (comma) and that the equal sign
separates the parameter from the configured value. The entry is marked as an error and is not
processed. The field nn defines the record that is in error.
Use the CFALIASREFRESH operator command to refresh the CFALIAS configuration file after the error
is resolved.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
114
●
PGTE3893E CFALIAS ALLOW parameter must be YES or NO: Record nn
Explanation:
The Platform Server was processing the CFALIAS configuration file. The Platform Server detected
that an invalid value was entered for the ALLOW parameter. Valid parameter values are YES or NO.
The entry is marked as an error and is not processed. The field nn defines the record that is in error.
Use the CFALIASREFRESH operator command to refresh the CFALIAS configuration file after the error
is resolved.
●
PGTE3894E CFALIAS FILE and ALIAS cannot be defined when ALLOW parameter is
defined: Record nn
Explanation:
The Platform Server was processing the CFALIAS configuration file. The Platform Server detected
that both the FILE/ALIAS and ALLOW parameters were defined for the same entry. These parameters
are mutually exclusive. The entry is marked as an error and is not processed. The field nn defines
the record that is in error.
Use the CFALIASREFRESH operator command to refresh the CFALIAS configuration file after the error
is resolved.
●
PGTE3902E SUBJCL Invalid Request Type - Must be SUBMIT: Record nn
Explanation:
The SUBJCL configuration program was reading an entry. The SUBMIT parameter was not the first
parameter in the file. The Platform Server requires that the SUBMIT parameter be the first parameter
in the config entry. This error can sometimes occur when a record is continued incorrectly. The
record number in error is displayed as nn. The entry read was marked as an error and will not be
enabled.
●
PGTE3903E SUBJCL Found SUBMIT - expecting continuation data: Record nn
Explanation:
The SUBJCL configuration program was expecting to read a continuation record but instead foud a
SUBMIT parameter. The SUBMIT parameter must be the first parameer defined and must not be
defined a second time. This error can sometimes occur when a record was continued incorrectly. The
record number in error is displayed as nn. The entry read was marked as an error and will not be
enabled.
●
PGTE3904E SUBJCL Invalid parameter ppppp: Incorrect length or incorrect
parameter: Record nn
Explanation:
The SUBJCL configuration program was reading parameter ppppp. Parameter ppppp is either
incorrect or the length of the parameter exceeded the maximum length allowed. The record number
in error is displayed as nn. The entry read was marked as an error and will not be enabled.
®
See the TIBCO Managed File Transfer Platform Server for z/OS Installation and Operation Guide for more
information on the data expected for this parameter.
●
PGTE3905E SUBJCL too many parameters entered for one SUBJCL request: Record nn
Explanation:
The SUBJCL configuration program was reading parameter ppppp but found too many parameters
asigned to a single entry. This is most likely caused by incorrectly placed commas at the end of
every line. These lines were considered continuation lines and the data was processed. The record
number in error was displayed as nn. The entry read was marked as an error and will not be
enabled.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
115
●
PGTE3906E Input data: ttttttttttttttttttttttttttttttt
Explanation:
This message displays the input data associated with a config entry that is in error. Additional
messages are displayed to describe the cause of the error.
●
PGTE3907E SUBJCL Open failed on DD SUBJCL - Bypassing SUBJCL File processing
Explanation:
The Platform Server SUBJCL configuration program was opening the SUBJCL DD statement but
encountered an error. SUBJCL processing is terminated.
Refer to the z/OS messages on the console for more information about this error.
●
PGTE3909E SUBJCL Required parameter pppppppp missing on SUBMIT request: Record nn
Explanation:
Required parameter pppppppp was missing on the SUBMIT request. The record number in error was
displayed as nn. The entry read was marked as an error and will not be enabled.
●
PGTE3910E SUBJCL Requires one of following parms: DSN/PROCESS/IPADDR/NODE Record:
nn
Explanation:
The SUBJCL configuration program read a complete entry. One of the following parameters was
required:DSN, PROCESS, IPADDR, NODE. The record number in error was displayed as nn. The entry
read was marked as an error and will not be enabled.
●
PGTE3911E SUBJCL TYPE must be SEND, RECEIVE or BOTH
Explanation:
The user entered the SUBJCL TYPE parameter but entered invalid data for this parameter. The only
valid values are SEND, RECEIVE, or BOTH. The entry read was marked as an error and will not be
enabled.
Correct the parameter in error, and use the SUBJCLREFRESH command to refresh the SUBJCL config.
●
PGTE3912E SUBJCL SOURCE must be INITIATOR, RESPONDER or BOTH
Explanation:
The user entered the SUBJCL SOURCE parameter but entered invalid data for this parameter. The
only valid values are INITIATOR, RESPONDER or BOTH. The entry read was marked as an error and
will not be enabled.
Correct the parameter in error, and use the SUBJCLREFRESH command to refresh the SUBJCL config.
●
PGTE3913E SUBJCL STATUS must be SUCCESS, FAILURE or BOTH
Explanation:
The user entered the SUBJCL STATUS parameter but entered invalid data for this parameter. The
only valid values are SUCCESS, FAILURE or BOTH. The entry read was marked as an error and will not
be enabled.
Correct the parameter in error, and use the SUBJCLREFRESH command to refresh the SUBJCL config.
●
PGTE3914E SUBJCL IPADDR invalid dotted decimal format
Explanation:
The user entered the SUBJCL IPADDR parameter but entered invalid data for this parameter. The
must be entered in dotted decimal format. The entry read was marked as an error and will
not be enabled.
IPADDR
Correct the parameter in error, and use the SUBJCLREFRESH command to refresh the SUBJCL config.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
116
●
PGTE3921E TRCLASS Open failed on DD TRCLASS - Bypassing TRCLASS File processing
Explanation:
An attempt was made to open the TRCLASS DD statement but the open failed. This message will
typically be accompanied by other messages describing the error. TRCLASS processing will be
disabled.
●
PGTE3923E TRCLASS error on record nn: Invalid value for pp: xxxxxxx
Explanation:
When processing the TRCLASS configuration file, an error was found on record nn. The value for the
parameters (defined as xxxx) is displayed.
Correct the parameter and issue the TRCLASSREFRESH operator command.
●
PGTE3924E TRCLASS error on record nn: Required Parameter pp not defined: xxxxxx
Explanation:
When processing the TRCLASS configuration file, an error was found on record nn. Required
parameter (xxxxx) was not defined. Correct the parameter and issue the TRCLASSREFRESH operator
command.
●
PGTE3925E TRCLASS error on record nn: Invalid Parameter: pp
Explanation:
When processing the TRCLASS configuration file, an error was found on record nn. Parameter
(xxxxx) is invalid.
Correct the parameter and issue the TRCLASSREFRESH operator command.
●
PGTE3926E TRCLASS error on record nn: NUM 0 is reserved: pp
Explanation:
When processing the TRCLASS configuration file, an error was found on record nn. NUM=0 is reserved
and cannot be defined.
Correct the parameter and issue the TRCLASSREFRESH operator command.
●
PGTE3927E Abend xx-yy detected opening ddname TRCLASS: TRCLASS processing
bypassed
Explanation:
When processing the TRCLASS configuration file, abend xx-yyy was received opening the TRCLASS
DD statement. If this is an 013-18 error, it means that the member was not found. TRCLASS
processing will be disabled.
After resolving the cause of this issue, you may need to restart the MFT started task.
●
PGTE3929E TRCLASS error on record nn: NAME cannot be DEFAULT:xxxxxx
Explanation:
When processing the TRCLASS configuration file and found an error on record nn. TRCLASS Name
“DEFAULT” is reserved and cannot be defined.
Correct the parameter and issue the TRCLASSREFRESH operator command.
●
PGTE3930E TRCLASS error on record nn: NUM already used: xxxxxx
Explanation:
When processing the TRCLASS configuration file, an error was found on record nn. TRCLASS NUM
was already used and cannot be used twice. Correct the parameter and issue the TRCLASSREFRESH
operator command.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
117
●
PGTE3931E TRCLASS error on record nn: TRCLASS already used: xxxxxx
Explanation:
When processing the TRCLASS configuration file, an error was found on record nn. TRCLASS
NAME was already used and cannot be used twice. Correct the parameter and issue the
TRCLASSREFRESH operator command.
●
PGTE3933E tttttttttt TRCLASS "nnnnnnnnnn" not found: Using Default TRCLASS
Explanation:
A transfer was submitted that defined a transfer class. Transfer class nnnnnnnnnn was not found in
the TRCLASS table and the default transfer class that allows unlimited transfers will be used.
Review the TRCLASS names that were defined by the TRCLASS DD statement. Either add the
TRCLASS to the TRCLASS config file and issue the TRCLASSREFRESH operator command, or change
the TRCLASS associated with the file transfer to match an existing TRCLASS definition
●
PGTE3952E tttttttttt MEMBER invalid on Platform Server SUBMIT: Member exceeds 8
characters: Request terminated
Explanation:
Activity tttttttttt was completed. The SUBJCL processing attempted to submit a job into the internal
reader, but the member name associated with the SUBJCL entry was invalid. SUBJCL processing
terminates without the job being submitted.
Check the JCL parameter in the SUBJCL configuration member to make sure that the member name
is between 1 and 8 characters.
●
PGTE3953E tttttttttt MEMBER defined on Platform Server SUBMIT but GLOBAL
JOB_SUBMIT_DSN not defined: Request terminated
Explanation:
Activity tttttttttt was completed. The SUBJCL processing attempted to submit a job into the internal
reader. Only the member name was specified by the SUBJCL JCL parameter. The Platform Server
extracted the GLOBAL JOB_SUBMIT_DSN parameter to get the dataset, but that parameter was not
defined. Therefore, the Platform Server could not read the JCL to submit into the internal reader. If
you want to specify the member name in the JCL parameter, then the GLOBAL JOB_SUBMIT_DSN
parameter must be defined. SUBJCL processing terminates without the job being submitted.
●
PGTE3954E tttttttttt Platform Server SUBJCL output data length > max allowed=xx:
Request terminated
Explanation:
Activity tttttttttt was completed. The SUBJCL program attempted to write the data into the internal
reader. The Platform Server was performing parameter substitution but detected that with the
parameter substitution, the data record exceeded 72 bytes. Since JCL only accepts 72 bytes, an error
occurs. SUBJCL processing terminates without the job being submitted successfully.
Make sure that the total length of any line after parameter substitution completes must be 72
characters or less.
●
PGTE3955E nnnnnnnn SUBJCL RACF Error: SAF RC=nn RACF RC=nn: nn
Explanation:
Activity nnnnnnnn was completed. The Platform Server attempted to perform a RACROUTE
VERIFY to setup the security environment for the SUBJCL job submission. The RACROUTE
VERIFY failed. This message displays the error code associated with the failure. A descriptive text
message is also displayed. SUBJCL processing terminates without the job being submitted
successfully.
●
PGTE3956E tttttttttt Platform Server SUBJCL Transfer Racroute failed: SUBJCL
processing terminated
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
118
Explanation:
Activity tttttttttt was completed. The Platform Server attempted to perform a RACROUTE VERIFY
to setup the security environment for the SUBJCL job submission. The Platform Server detected
however, that the file transfer failed because the RACROUTE VERIFY attempted during the file
transfer failed. SUBJCL processing terminates without the job being submitted successfully.
●
PGTE3957E tttttttttt Platform Server SUBJCL File Error on DSN=dsn(member): Error
message follows
Explanation:
The Platform Server SUBJCL processing was being performed for activity tttttttttt. The Platform
Server attempted to submit a job into the internal reader, but received an error performing file I/O.
Subsequent messages will detail the reason for the error. The transfer continues execution. This
message does not affect the outcome of the file transfer.
●
PGTB4100E Parameter not recognized in next record
Explanation:
The specified record of the Platform Server batch job had an invalid parameter.
Correct the parameter and re-submit the job.
●
PGTB4101E LPASS Parameter required when defining Responder Profiles for a
different user
Explanation:
The user attempted to create a responder profile and the GLOBAL RESPONDER_PROFILE_LPASS was
set to YES. However, the user did not enter the LPASS parameter. When
RESPONDER_PROFILE_LPASS=YES is defined, the LPASS parameter is required. The request is
terminated and the responder profile is not added or updated.
●
PGTB4102E Invalid parameter value in next record
Explanation:
The specified record of the Platform Server batch job had an invalid parameter.
Correct the parameter and re-submit the job.
●
PGTB4103E Dataset name not cataloged
Explanation:
The dataset name used in this transfer was not cataloged.
Catalog or change the dataset name and re-submit the transfer.
●
PGTB4104E Load failed for module OSIRECOV or OSIETCO1
Explanation:
The Platform Server attempted to load its error recovery modules but failed. Two possible causes for
this error could be that there was not enough REGION was supplied on the EXEC card or that there
was an invalid STEPLIB.
See the accompanying CSV messages displayed by z/OS for more information on the cause of the
failure.
●
PGTB4105E OPERAND READ BEFORE A PROCESS CARD
Explanation:
The Platform Server Process card must be the first statement in the SYSIN parameters of the
Platform Server batch job.
Correct the error and re-submit the job.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
119
●
PGTB4106E INVALID NUMBER OF OPERANDS IN NEXT RECORD
Explanation:
Too many parameters were provided in the specified record of the Platform Server batch job.
Correct the parameter and re-submit the job.
●
PGTB4107E NO MORE ROOM LEFT IN THE SERVER WORK QUEUE
Explanation:
The profile dataset needs to be expanded.
Use the DEFPROF member in the JCL library to increase the size of the file.
●
PGTB4108E FUSION SERVER NOT AVAILABLE
Explanation:
The FUSPROF program was unable to detect the MFT started task. Make sure that the FUSPROF job
is running on the same computer as the MFT started task.
●
PGTB4109E SECURITY DENIED ACCESS
Explanation:
Access was denied to the dataset that is either being sent or received.
Make sure that the userid for this transfer has permission to access the specified dataset. Correct the
error and re-submit the transfer.
●
PGTB4113E SEVERE ERROR - RETURN CODE IS NOT RECOGNIZED
Explanation:
The Platform Server batch interface program received a communications error which it did not
recognize.
Contact TIBCO Technical Support for assistance.
●
PGTB4115E NO PROCESS CARD IN THE SYSIN FILE
Explanation:
The Platform Server Process card must be the first statement in the SYSIN parameters of the
Platform Server batch job.
Correct the error and re-submit the job.
●
PGTB4116E PRIOR PROCESS NOT QUEUED - PARAMETER ERROR
Explanation:
There is an invalid parameter in the specified record of the Platform Server batch job.
Correct the parameter and re-submit the job.
●
PGTB4117E REQUIRED PARAMETER MISSING IN NEXT RECORD
Explanation:
A parameter was missing in the specified record of the Platform Server batch job.
Specify the required parameter and re-submit the job.
●
PGTB4118E REQUIRED PARAMETER INVALID IN NEXT RECORD
Explanation:
An invalid parameter was found in the specified record of the Platform Server batch job.
Correct the required parameter and re-submit the job.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
120
●
PGTB4121E NEXT PARM CONFLICTS WITH A PRIOR PARM
Explanation:
An invalid parameter was found in the specified record of the Platform Server batch job. Most likely
there was a parameter that was specified multiple times.
Correct the parameter and re-submit the job.
●
PGTB4122E THE SPECIFIED LIST WAS NOT FOUND
Explanation:
The list specified to be used to distribute the file was not found.
Correct or add the list to the CONFIG member and re-submit the job.
●
PGTB4123E PRIOR PROCESS NOT QUEUED - NODE PARAMETER IS REQUIRED
Explanation:
The NODE parameter was not specified in the batch job.
Add the
●
NODE
parameter with a valid node and re-submit the job.
PGTB4126E SERVER xxxx NEVER ACTIVE SINCE IPL - TRANSACTION NOT QUEUED
Explanation:
This is a general message that is displayed when trying to queue a transfer to a server that is not
currently active and has not been active since the last IPL.
●
PGTB4127E APPLICATION must be KNFUSION if TRANS_TYPE=COMMAND
Explanation:
Check your Platform Server SYSIN parameters, correct the error and re-submit the job.
●
PGTB4128E TRANSFER must be SEND if TRANS_TYPE=COMMAND
Explanation:
Check your Platform Server SYSIN parameters, correct the error and re-submit the job.
●
PGTB4129E TRANS_TYPE must be COMMAND if COMMAND/REXXEXEC/CALLJCL/CALLPROG/SUBMIT
parameters set
Explanation:
Check your Platform Server SYSIN parameters, correct the error and re-submit the job.
●
PGTB4130E COMMAND parameter must be present if TRANS_TYPE=COMMAND or for REXX
requests
Explanation:
Check your Platform Server SYSIN parameters or REXX request, correct the error and re-submit the
job.
●
PGTB4131E Server xxxx not active and WAIT=YES coded on SYSIN - transaction not
queued
Explanation:
When the WAIT parameter is set to YES, the initiator would remain active until the transfer is
complete and this would be forever if the server is not active. Therefore the transaction is not
queued.
●
PGTB4132E A parameter value must be specified in the next record
Explanation:
A record was found that had only a parameter and no value. A value must be specified.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
121
Correct the input and resubmit the job.
●
PGTB4133E User Profile not found for LOCAL USER/NODE combination
Explanation:
The user profile was not defined and the remote node specified.
Define a profile for the user and node combination, or specify a remote user and password instead
of USER=PROFILE.
●
PGTB4134E PROFILE dataspace not created - unable to find match on User Profile
Explanation:
The user profile dataspace was not created when the Platform Server was brought up.
Correct this problem and resubmit the job or specify a remote user and password instead of
USER=PROFILE.
●
PGTB4135E Server server_name not active AND step not running APF Authorized transfer not queued
Explanation:
The Platform Server was not active and the step was not running APF authorized. This transaction
was not queued. A transaction can be queued when the server is down, but the job step must be
running APF authorized.
Change the job step to run APF authorized and resubmit the job, or bring up the Platform Server
server and resubmit the job.
●
PGTB4136E PRINTER_NAME parameter is ignored on a local PRINT activity
Explanation:
The PRINTER_NAME parameter was specified for remote printers only. This is just an
informational message that because it is a receive activity, the printer name specified is ignored.
●
PGTB4137E TIMEOUT interval exceeded: Request has not completed
Explanation:
The Platform Server batch interface was invoked. The user specified WAIT=YES and configured the
parameter to a non-zero value. The TIMEOUT interval expired before the request
completed. Because the PURGE parameter was not set to YES, the request will not be purged form the
Platform Server request queue. The Platform Server batch program is terminated with a return code
indicating a timeout.
TIMEOUT
●
PGTB4138E TIMEOUT interval exceeded: Request has been purged due to PURGE=YES
Explanation:
The Platform Server batch interface was invoked. The user specified WAIT=YES and configured the
parameter to a non-zero value. The PURGE parameter has been set to YES. The TIMEOUT
interval expired before the request completed. Because the PURGE parameter was set to YES, the
request will be purged form the Platform Server request queue. The Platform Server batch program
is terminated with a return code indicating a timeout purge.
TIMEOUT
●
PGTB4139E Error xxxxxxxx on TIMEOUT RESETWAIT request
Explanation:
The Platform Server batch interface was invoked. The user specified WAIT=YES and configured the
TIMEOUT parameter to a non-zero value. The TIMEOUT interval expired before the request completed.
The Platform Server batch interface attempted to issue a RESETWAIT parameter to the started task
before purging the request, but the RESETWAIT failed. One possible reason is that the Platform
Server started task is an older release of the software. This error is ignored and processing will
continue.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
122
●
PGTB4141E Error xxxxxxxx Received Scheduling transfer request
Explanation:
The Platform Server batch interface was invoked and attempted to schedule a file transfer request.
The request failed with return code xxxxxxxx. This message is only displayed when a request failed
with an unknown return code. Typically descriptive messages will be displayed to indicate the
cause of a failure.
●
PGTB4144E Error xxxxxxxx on TIMEOUT PURGE Request
Explanation:
The Platform Server batch interface was invoked. The user specified WAIT=YES, PURGE=YES and
configured the TIMEOUT parameter to a non-zero value. The TIMEOUT interval expired before the
request completed. The Platform Server batch interface attempted to purge the request, but the
purge failed with code xxxxxxxx. One possible reason is that the Platform Server started task is an
older release of the software. Another reason is that the request has already been marked for purge.
This error is ignored and processing will continue.
If this error persists, contact TIBCO Technical Support.
●
PGTB4145E EMAIL_GOOD and MQ_GOOD are mutually exclusive
Explanation:
The user entered the EMAIL_GOOD and MQ_GOOD parameters in the same request. However, these
parameters cannot both be entered for the same request. The transfer request is terminated with a
parameter error.
●
PGTB4146E EMAIL_FAIL and MQ_FAIL are mutually exclusive
Explanation:
The user entered the EMAIL_FAIL and MQ_FAIL parameters in the same request. However, these
parameters cannot both be entered for the same request. The transfer request is terminated with a
parameter error.
●
PGTB4147E APPLICATION must be FUSION if TRANS_TYPE=COMMAND and REXXEXEC/CALLJCL/
CALLPROG/SUBMIT set
Explanation:
Only the Platform Server protocol supports the REXXEXEC, CALLJCL, CALLPROG and SUBMIT
parameters. The user incorrectly set the APPLICATION to some other value. The transfer request is
terminated with a parameter error.
●
PGTB4148E LDISP parameter contains invalid Parenthesis
Explanation:
The Platform Server batch interface was validating the LDISP parameter and detected unbalanced
parenthesis. The transfer request is terminated with a parameter error.
●
PGTB4149E LDISP parameter contains invalid NORMAL Disposition: Must be KEEP,
DELETE, CATLG
Explanation:
The Platform Server batch interface was validating the LDISP parameter and detected an invalid
value for the NORMAL disposition. Valid values are KEEP, CATLG, and DELETE. The transfer request
is terminated with a parameter error.
●
PGTB4150E LDISP parameter contains invalid ERROR Disposition: Must be KEEP,
DELETE, CATLG
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
123
The Platform Server batch interface was validating the LDISP parameter and detected an invalid
value for the ERROR disposition. Valid values are KEEP, CATLG, and DELETE. The transfer request is
terminated with a parameter error.
●
PGTB4151E LDISP ERROR: NEW/CATLG can only be specified on RECEIVE file create
Explanation:
The Platform Server batch interface was validating the LDISP parameter. The user specified a
STATUS of NEW, or a NORMAL/ERROR disposition of CATLG. These values are only valid on a
RECEIVE FILE request. They are invalid on all other types of request. The transfer request is
terminated with a parameter error.
●
PGTB4152E LDISP ERROR: MOD can only be specified on RECEIVE file
Explanation:
The Platform Server batch interface was validating the LDISP parameter. The user specified a
STATUS of MOD. MOD is only valid on a RECEIVE FILE request. It is invalid on all other types of
request. The transfer request is terminated with a parameter error.
●
PGTB4153E LDISP ERROR: SHR cannot be specified along with DELETE: Must be OLD
Explanation:
The Platform Server batch interface was validating the LDISP parameter. The user specified a
STATUS of SHR, and a NORMAL/ERROR disposition of DELETE. When DELETE is specified as a
NORMAL/ERROR disposition, the status cannot be defined as SHR. Change the status field to OLD and
re-submit the request. The transfer request is terminated with a parameter error.
●
PGTB4154E LDISP ERROR: Status must be : SHR, OLD, MOD, NEW, NEWR, NEWA
Explanation:
The Platform Server batch interface was validating the LDISP parameter and detected an invalid
value for the status. Valid values are SHR, OLD, MOD, NEW, NEWR, NEWA. The transfer request is
terminated with a parameter error.
●
PGTB4155E LDISP ERROR: SubParameter error or invalid delimiter
Explanation:
The Platform Server batch interface was validating the LDISP parameter and detected an invalid
delimiter. The parameter must be delimited by commas ( , ). The parameter terminates with a space
or close parenthesis. The transfer request is terminated with a parameter error.
●
PGTB4156E RDISP parameter contains invalid Parenthesis
Explanation:
The Platform Server batch interface was validating the RDISP parameter and detected unbalanced
parenthesis. The transfer request is terminated with a parameter error.
●
PGTB4157E RDISP parameter contains invalid NORMAL Disposition: Must be KEEP,
DELETE, CATLG
Explanation:
The Platform Server batch interface was validating the RDISP parameter and detected an invalid
value for the NORMAL disposition. Valid values are KEEP, CATLG and DELETE. The transfer request
is terminated with a parameter error.
●
PGTB4158E RDISP parameter contains invalid ERROR Disposition: Must be KEEP,
DELETE, CATLG
Explanation:
The Platform Server batch interface was validating the RDISP parameter and detected an invalid
value for the ERROR disposition. Valid values are KEEP, CATLG, and DELETE. The transfer request is
terminated with a parameter error.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
124
●
PGTB4159E RDISP ERROR: NEW/CATLG can only be specified on SEND file create
Explanation:
The Platform Server batch interface was validating the RDISP parameter. The user specified a
STATUS of NEW, or a NORMAL/ERROR disposition of CATLG. These values are only valid on a SEND
FILE request. They are invalid on all other types of request. The transfer request is terminated with
a parameter error.
●
PGTB4160E RDISP ERROR: SHR cannot be specified along with DELETE: Must be OLD
Explanation:
The Platform Server batch interface was validating the RDISP parameter. The user specified a
STATUS of SHR, and an NORMAL/ERROR disposition of DELETE. When DELETE is specified as a
NORMAL/ERROR disposition, the status cannot be defined as SHR. Change the status field to OLD and
resubmit the request. The transfer request is terminated with a parameter error.
●
PGTB4161E RDISP ERROR: MOD can only be specified on SEND file
Explanation:
The Platform Server batch interface was validating the RDISP parameter. The user specified a
STATUS of MOD. MOD is only valid on a SEND FILE request. It is invalid on all other types of request.
The transfer request is terminated with a parameter error.
●
PGTB4162E RDISP ERROR: Status must be : SHR, OLD, MOD, NEW, NEWR, NEWA
Explanation:
The Platform Server batch interface was validating the RDISP parameter and detected an invalid
value for the status. Valid values are SHR, OLD, MOD, NEW, NEWR, NEWA. The transfer request is
terminated with a parameter error.
●
PGTB4163E RDISP ERROR: SubParameter error or invalid delimiter
Explanation:
The Platform Server batch interface was validating the RDISP parameter and detected an invalid
delimiter. The parameter must be delimited by commas ( , ). The parameter terminates with a space
or close parenthesis. The transfer request is terminated with a parameter error.
●
PGTB4165E Maximum of 4 continuation cards detected
Explanation:
The user was in the Platform Server batch interface (OSIUB000) and detected that more than 4
continuation cards were supplied for the same parameter. This is an error. The Platform Server
supports a maximum of 4 continuation cards.
●
PGTB4166E SYSPRINT open failed: OSIUB000 ending
Explanation:
The Platform Server batch interface attempted to open the SYSPRINT file but the open failed. This is
typically because the SYSPRINT DD statement was not defined. The batch job failed with a non-zero
return code.
Correct the JCL and resubmit the request.
●
PGTB4167E SYSIN open failed: OSIUB000 ending
Explanation:
The Platform Server batch interface attempted to open the SYSIN file but the open failed. This is
typically because the SYSIN DD statement was not defined. The batch job fails with a non-zero
return code.
Correct the JCL and resubmit the request.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
125
●
PGTB4168E SYSIN DCB invalid- must be RECFM=FB,LRECL=80: OSIUB000 ending
Explanation:
The batch interface program (OSIUB000) detected that the SYSIN DCB characteristics were invalid.
The SYSIN DD statement must have the characteristics defined in the message. If the DCB
characteristics are invalid, the batch job fails with a non-zero return code.
Correct the JCL and resubmit the request.
●
PGTB4179E Maximum of 25 members exceeded by MEMBER or XMEMBER parameter
Explanation:
The user entered either the MEMBER or XMEMBER parameter but entered more than 25 member names.
The maximum number of member names that can be entered is 25. The file transfer is not scheduled
for execution.
●
PGTB4180E Maximum member length of 8 exceeded by MEMBER or XMEMBER parameter
Explanation:
The user entered either the MEMBER or XMEMBER parameter but entered a member name longer than
8 characters. The maximum member length is 8 characters. The file transfer is not scheduled for
execution.
●
PGTB4181E MEMBER and XMEMBER parameters cannot be used in same PROCESS request
Explanation:
The user entered both the MEMBER and XMEMBER parameters within the same PROCESS request.
and XMEMBER are mutually exclusive and cannot be entered within the same PROCESS
request. The file transfer is not scheduled for execution.
MEMBER
●
PGTB4182E Token Load Failed for module xxxxxxxx: Transfer not scheduled
Explanation:
The Platform Server batch interface attempted to schedule a file transfer request with the Platform
Server started task (STC). The STC was not active. The Platform Server then attempted to issue a
load for the z/OS token module, but the load request failed. The z/OS token load modules are
typically located in the LPA library. If the load modules are not in the LPA library, the library that
they are located in should be added to the STEPLIB of the job that is scheduling the request. The
request is not scheduled and a return code is set. When the Platform Server started task comes up,
the request can be scheduled again. If the started task is up, check that the value assigned to the
SERVER parameter in the EXEC PARM matches the name of the started task that is active.
●
PGTB4183E Token XXXXXXXX failed RC=yy: Transfer not scheduled
Explanation:
The Platform Server batch interface attempted to schedule a file transfer request with the Platform
Server started task (STC). The STC was not active. The Platform Server then attempted to issue a
z/OS token request, but token request xxxxxxxx failed with return code yy. The request is not
scheduled and a return code is set. When the Platform Server started task comes up, the request can
be scheduled again.
If the started task is up, check that the value assigned to the SERVER parameter in the EXEC PARM
matches the name of the started task that is active. Contact TIBCO Technical Support if this error
occurs.
●
PGTB4184E User not authorized to use Platform Server to transfer data
Explanation:
The Platform Server batch interface attempted to schedule a file transfer request with the Platform
Server started task (STC). The Platform Server administrator configured the system so that only
authorized users could use the Platform Server. The user that initiated this request was not
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
126
authorized to use the Platform Server. There are typically other messages that are displayed that
indicate the cause of the failure. The request terminates with an error.
Contact the Platform Server administrator to get authorization to use the Platform Server.
●
PGTB4185E User not authorized to use Platform Server to transfer data to defined
NODE
Explanation:
The Platform Server batch interface attempted to schedule a file transfer request with the Platform
Server started task (STC) to a particular node or IP Address. The Platform Server administrator
configured the system so that only authorized users could use particular the Platform Server nodes.
The user that initiated this request was not authorized to use the defined the Platform Server node.
There are typically other messages that are displayed that indicate the cause of the failure. The
request terminates with an error.
Contact the Platform Server administrator to get authorization to use the Platform Server node.
●
PGTB4188E Error communicating with MFT Started task - Setting Return Code to
SERVER_DOWN
Explanation:
The user selected TCP or SNA communications to communicate with the Platform Server started
task. However the client software detected a TCP or SNA error when attempting to communicate
with the started task. The return code for this process was set to indicate that the Platform Server
started task is down. This message typically means that the Platform Server is down or connectivity
cannot be established to this server. For SNA connection, this could also mean that the
SERVLUNAME was defined incorrectly. For TCP communications, this could also indicate that the
SERVIPADDR, SERVIPNAME, TCPIPJPOBNAME or SERVIPPORT was defined incorrectly.
●
PGTB4190E pppppppp mmmmmmmmmmmmmmmmmmmmmmmmmm
Explanation:
The user entered DCB information for a request, but the DCB information validation routine found
an error with parameter pppppppp. A description of the error is displayed after the parameter name.
The request is terminated with errors.
●
PGTB4191E CONFIG parameter error Transfer terminated
Explanation:
The user defined the EXEC PARM CONFIG parameter to define the connection information for the
started task. However an error occurred when an attempt was made to access the member defined
by the CONFIG parameter. The most likely reason for this error is that the entry defined by the
CONFIG parameter was not found. A WTO message will be displayed that describes the error that
occurred. Note that the CONFIG entry name is case sensitive. It is a good practice to define the
parameters in upper case. The request is terminated with errors.
●
PGTB4192E CONFIG parameter specified but FUSCFG DD statement not defined
Explanation:
The user defined the EXEC PARM CONFIG parameter to define the connection information to the
started task. However the FUSCFG DD statement was not defined. The FUSCFG DD statement is
required when using the JCL PARM CONFIG parameter. The request is terminated with errors.
●
PGTB4196E Local File required for File Send, File Receive or SUBMIT
Explanation:
The user executed a file transfer send, a file transfer receive, or a submit but did not include the
LOCAL_FILE parameter. This parameter is required. The transfer was terminated with an error.
●
PGTB4197E SCRIPT parameter required for SCRIPT execution
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
127
The user scheduled a script to be executed but did not include the SCRIPT parameter. This
parameter is required. The transfer was terminated with an error.
●
PGTS4200E OSIUC000 Syntax Error: dddddddddddddddd
Explanation:
The Platform Server script program attempted to process a script statement and detected an error.
The script was terminated with an error. This message gives a description of the error. Additional
messages are sometimes displayed to give more information about the error.
●
PGTS4201E OSIUC000 No PARM data passed on EXEC: Script terminated
Explanation:
The Platform Server script program was running, but no data was passed to the program in the JCL
PARM. The user must define the information needed to access the Platform Server started task in
the JCL PARM statement. The script was terminated with an error.
●
PGTS4202E OSIUC000 Invalid PARM data passed: Script terminated
Explanation:
The Platform Server script program attempted to process the data passed in the JCL PARM. The
Platform Server detected an invalid PARM parameter or a syntax error in the PARM. The script was
terminated with an error. This message is followed by an additional error message that displays the
data passed.
Review the displayed information to determine the cause of the error.
●
PGTS4203E OSIUC000 OPEN of xxxxxxxx DD failed - Check DD statement: Program
terminated
Explanation:
The Platform Server script program attempted to open DD statement xxxxxxxx but the open failed.
This is typically because the DD statement was not defined. The Platform Server script interface
requires three DD statements: SYSIN, SYSPRINT and SYSTRACE. The script was terminated with
an error.
Correct the JCL and resubmit the job.
●
PGTS4204E OSIUC000 Parameter error on SYSIN record nnn
Explanation:
The Platform Server script program attempted to read the SYSIN parameter file and found an error
at record nnn. The parameter in error is displayed following this message. The script was terminated
with an error.
Correct the parameter and resubmit the job.
●
PGTS4205E OSIUC000 SYSIN parameter count exceeds maximum allowed of 8000
Explanation:
The Platform Server script program attempted to read the SYSIN parameter file and loading the
parameters into storage. The maximum number of parameter lines allowed is 8000, but this number
has been exceeded. The script was terminated with an error.
Change the script so that the number of parameters lines is less than 8000. Either split the script into
two or more scripts, or remove comments from the script.
●
PGTS4206E OSIUC000 SYSIN record length is 0 bytes
Explanation:
The Platform Server script program attempted to read the SYSIN parameter file and found a zero
length record. The Platform Server considers this an error. The script was terminated with an error.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
128
●
PGTS4207E OSIUC000 SYSIN record exceeds 256 byte maximum
Explanation:
The Platform Server script program attempted to read the SYSIN parameter file and found a record
longer than the 256 byte maximum. The Platform Server considers this an error. The script was
terminated with an error.
●
PGTS4208E OSIUC000 Invalid pppppppp Parameter passed in PARM EXEC
Explanation:
The Platform Server attempted to process the JCL PARM parameters and found an error in parameter
pppppppp. The script was terminated with an error.
Correct the parameter, and resubmit the script.
●
PGTS4209E OSIUC000 Debug dddddddddddddddddddddd
Explanation:
This message is displayed when the user set the DEBUGON parameter to turn on script debugging.
Script debugging is typically set when requested by TIBCO Technical Support when there is a
problem with a Platform Server script. This message is for information purposes only.
●
PGTE4210E Abend aaa detected in CALLPGM pppppppp - PSW: xxxxxxxx yyyyyyyy Program
Address: zzzzzzzz
Explanation:
The user issued the Platform Server script CALLPGM function call. This call loaded and called a
user-defined program. The Platform Server detected that the program (pppppppp) abended with
code aaa. The PSW of the abending program was xxxxxxxx yyyyyyyy. The script was terminated with
errors. Additional messages will be displayed to show the registers at the time of the error.
●
PGTE4211E General Registers at time of error
Explanation:
This is an informational message that is displayed when an abend occurred in a user program called
by the CALLPGM function call. It displays the contents of the General Registers at the time of the
error.
●
PGTE4212E Access Registers at time of error
Explanation:
This is an informational message that is displayed when an abend occurred in a user program called
by the CALLPGM function call. It displays the contents of the Access Registers at the time of the
error.
●
PGTE4213E (Register information is displayed)
Explanation:
This message is displayed when an abend has occurred in a user program called by the CALLPGM
function call. It displays the contents of General registers and Access registers at the time of the
error.
●
PGTE4214E Invalid DCB on INCLUDE dd: Must be RECFM=FB,LRECL=80,DSORG=PO
Explanation:
The Platform Server scripting interface detected an INCLUDE parameter. It then went to the
INCLUDE DD statement and opened the file, but the DCB characteristics were invalid. The
INCLUDE DD statement must have the following DCB: RECFM=FB,LRECL,DSORT=PO. The DSORT
parameter indicates that the dataset is a PDS or PDS/E. The script request failed with a parameter
error.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
129
●
PGTE4215E Abend xxx detected opening ddname dddddddd: Script terminated
Explanation:
The Platform Server script program attempted to open ddname dddddddd but the open failed with
abend code xxx. Typical reasons for this error are that the user is not authorized for the script file or
that the member defined in a script PDS is not defined. The script program terminated with a nonzero return code.
See abend xxx in the IBM z/OS MVS System Codes manual.
●
PGTE4216E SYNAD exit entered for ddname dddddddd: Script terminated
Explanation:
The Platform Server script program attempted to process ddname dddddddd, but the get/put failed
when the SYNAD exit was entered. Typical reasons for this error are that the dcb characteristics of
the file are invalid or that the system detects an I/O error. The script program terminated with a nonzero return code.
●
PGTE4217E Activity tttttttttt Script terminated by Purge command
Explanation:
The Platform Server was running a script. The script program checked and determined that a user
entered a PURGE request for the Platform Server script. This message indicates that the script was
purged.
●
PGTE4218E tttttttttt Script error allocating DSN=dddddddddd: mmmmmmmmm
Explanation:
The user attempted to execute a script defined with the INDIRECT parameter. When an attempt was
made to allocate the indirect dataset, a dynamic allocation error was received. The script was
terminated with errors. The dataset name and the error message are displayed.
●
PGTE4219E tttttttttt Script error allocating DSN=dddddddddd: S99ERROR=nnnn
S99INFO=nnnn
Explanation:
The user attempted to execute a script defined with the INDIRECT parameter. When an attempt was
made to allocate the indirect dataset, a dynamic allocation error was received. The dataset name is
displayed along with the dynamic allocation return codes. The script is terminated with errors.
●
PGTE4232E Activity tttttttttt Script execution failed with RC=yy: Script output
is in ddname ddddddd
Explanation:
The Platform Server was running a script. This is an informational message indicating that script
execution was unsuccessful and that any output for this script will be in DD statement dddddddd.
The user can browse the output in the Platform Server started the task output. The script ended with
non-zero return code yy. The script will be purged from the system.
●
PGTE4236E tttttttttt DSN invalid on Platform Server SUBMIT: DSN null or exceeds
44 characters: Request terminated
Explanation:
The Platform Server was running a script and was parsing the SCRIPT name. The Platform Server
detected that the dataset name was longer than the maximum allowed of 44 bytes. The Platform
Server displays this message and the script processing is terminated with errors.
●
PGTE4237E tttttttttt MEMBER invalid on Platform Server SUBMIT: Member exceeds 8
characters: Request terminated
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
130
The Platform Server was running a script and was parsing the SCRIPT name. The Platform Server
detected that the member name was invalid. It was either missing or longer than 8 bytes. The
Platform Server displays this message and the script processing is terminated with errors.
●
PGTE4238E tttttttttt INDIRECT=DELETE not allowed when Member specified:
DSN=dddddddddddd Member=mmmmmmmm
Explanation:
The user was executing a script defined with the INDIRECT parameter set to DELETE. A member
was defined as a part of the indirect dataset name. When INDIRECT=DELETE is defined, a member
cannot be specified. The script is terminated with errors.
●
PGTE4241E Error accessing FUSCFG CONFIG member: mmmmmmmm - Script terminated
Explanation:
The user defined the EXEC PARM CONFIG parameter to define the connection information to the
started task for the script interface. However an error occurred when attempting to access the
member defined by the CONFIG parameter. The most likely reason for this error is that the entry
defined by the CONFIG parameter was not found. Note that the CONFIG entry name is case
sensitive. It is a good practice to define the parameters in upper case. The request is terminated with
errors.
●
PGTE4242E FUSCFG DD statement required when CONFIG parameter is used - Script
terminated
Explanation:
The user defined the EXEC PARM CONFIG parameter to define the connection information to the
started task for the script interface. However the FUSCFG DD statement was not defined. The
FUSCFG DD statement is required when using the JCL PARM CONFIG parameter. The request is
terminated with errors.
●
PGTE4244E tttttttttt Script scheduled with Member Name: SCRIPT DD not found:
Request terminated
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 but the SCRIPT DD was not
defined to the started task. If you want to schedule scripts to run with only a member name, the STC
must have the SCRIPT DD defined that references the script libraries. The request is terminated with
an unrecoverable error.
●
PGTE4245E tttttttttt Script scheduled with Member Name: Member mmmmmmmmmm not
found in SCRIPT DD: Request terminated
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 but the member was not in any of
the libraries defined by the SCRIPT DD. The request is terminated with an unrecoverable error.
Verify that the script name is correct, and make sure that the library that contains the member is
defined by the STC SCRIPT DD.
●
PGTE4246E tttttttttt Script scheduled with Member Name mmmmmmmm: DSN not found
for Concat nn: Request terminated
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 and found the member in one of
the datasets. However, the STC could not determine the dataset name of the file that contained the
member. The request is terminated with an unrecoverable error.
If this error occurs, contact Technical Support.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
131
●
PGTE4247E tttttttttt Script scheduled with Member Name mmmmmmmm: RDJFCB failed
R15=nn: Request terminated
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 and found the member in one of
the datasets. However, the STC received an error when executing the RDJFCB macro. The request is
terminated with an unrecoverable error.
If this error occurs, contact Technical Support.
●
PGTN4250E DSN for send does not exist
Explanation:
The data set name that was specified for the send did not exist.
Check the data set name that was specified to make sure that it exists and also check for spelling
errors.
●
PGTN4251E Failure loading ESTAE routing
Explanation:
An error occurred an attempt was made to load the recovery routine.
Increase the region size. If the problem persists, contact TIBCO Technical Support.
●
PGTN4252E Invalid EFFECT parameter value
Explanation:
The value that was specified in the EFFECT parameter was invalid. The valid values are C for Create,
R for Replace, A for Append, CR for Create/Replace, CA for Create/Append and CN for Create/
Replace/New Attributes.
Correct the parameter and re-submit the transfer.
●
PGTN4253E SAF Authority check failed
Explanation:
The user ID executing the transfer did not have sufficient authority to access the data set.
Contact your Security Administrator for the correct authority.
●
PGTE4256E tttttttttt Script scheduled with Member Name mmmmmmmm: JFCB Not
available for DSN lookup: Request terminated
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 and found the member in one of
the datasets. However, the STC received an error when parsing the control blocks returned by the
RDJFCB macro. The request is terminated with an unrecoverable error.
If this error occurs, contact Technical Support.
●
PGTN4257E DSN (Local File) not defined
Explanation:
The user was executing a file transfer send, a file transfer receive or a submit, but did not include the
LOCAL_FILE parameter. This parameter is required. The transfer is terminated with an error.
●
PGTX4500E Load failed for DFLTAB dddddddd: Request terminating
Explanation:
The user specified the PARM parameter DFLTAB (or used the default DFLTAB), but DFLTAB was not
found in the STEPLIB. FUSXJOB is terminated and a non-zero return code will be set.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
132
Make sure that the DFLTAB name is correct, and that the DFLTAB is located in the Platform Server
STEPLIB.
●
PGTX4503E No PARM statement defined in the JCL
Explanation:
The user executed the Platform Server XCOM interface but did not specify a JCL PARM statement.
The JCL PARM statement is required when using the Platform Server XCOM interface. FUSXJOB is
terminated and a non-zero return code will be set.
●
PGTX4504E PARM parameter ppppppppp > 32 characters
Explanation:
The user executed the Platform Server XCOM interface and specified an invalid PARM parameter.
The parameter length (the data preceding the =) was greater than 32 characters. The first 8 characters
of the data in error (pppppppp) are displayed. FUSXJOB is terminated and a non-zero return code
will be set.
●
PGTX4505E Error processing SYSIN01 parameter: Transfer terminated
Explanation:
The user executed the Platform Server XCOM interface and specified an invalid SYSIN01 parameter.
The parameter that caused the error is displayed in a message preceding this message. FUSXJOB is
terminated and a non-zero return code is set.
●
PGTX4506E SWAIT exceeded on TYPE=INQUIRE for Activity tttttttttttttttt: Trying
next request
Explanation:
The user executed the Platform Server XCOM interface and specified TYPE=INQUIRE. The amount of
time defined by the SWAIT parameter was exceeded. Therefore, FUSXJOB will stop waiting for this
request to complete, and will try the next request specified by the XCOMINQW dataset.
●
PGTX4507E TIMEOUT exceeded on TYPE=INQUIRE for Activity tttttttttttttttt: Trying
next request
Explanation:
The user executed the Platform Server XCOM interface and specified TYPE=INQUIRE. The amount of
time defined by the TIMEOUT parameter was exceeded. Therefore, FUSXJOB will stop waiting for
this request to complete, and will try the next request specified by the XCOMINQW dataset.
●
PGTX4508E SWAIT exceeded on TYPE=EXECUTE for Activity tttttttttttttttt: Purging
request
Explanation:
The user executed the Platform Server XCOM interface and specified TYPE=EXECUTE. The amount of
time defined by the SWAIT parameter was exceeded. Therefore, FUSXJOB will stop waiting for this
request to complete and purge the request from the Platform Server Queue. Based on the PARM
CONTINUE parameter, FUSXJOB may continue processing the next request specified by the SYSIN01
file.
●
PGTX4509E TIMEOUT exceeded on TYPE=EXECUTE for Activity tttttttttttttttt: Purging
request
Explanation:
The user executed the Platform Server XCOM interface and specified TYPE=EXECUTE. The amount of
time defined by the TIMEOUT parameter was exceeded. Therefore, FUSXJOB will stop waiting for
this request to complete and purge the request from the Platform Server queue. Based on the PARM
CONTINUE parameter, FUSXJOB may continue processing the next request specified by the SYSIN01
file.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
133
●
PGTX 4513E PARM error on pppppppp parameter: Job terminated
Explanation:
The user executed the Fusion XCOM interface and specified PARM parameter pppppppp. The value
associated with parameter pppppppp was invalid. FUSXJOB is terminated and a non-zero return code
will be set.
●
PGTX4515E SYSIN01 error on pppppppp parameter: Job terminated
Explanation:
The user executed the Platform Server XCOM interface and specified SYSIN01 parameter pppppppp.
The value associated with parameter pppppppp was invalid. FUSXJOB is terminated and a non-zero
return code will be set.
●
PGTX4518E Error opening ffffffff file: Job terminated
Explanation:
FUSXJOB could not open file ffffffff. This file is required when running the Platform Server XCOM
interface. FUSXJOB is terminated and a non-zero return code will be set.
●
PGTX4519E Invalid PARM field pppppppp: Job terminated
Explanation:
The user executed the Platform Server XCOM interface and specified PARM parameter pppppppp. This
parameter is invalid. FUSXJOB is terminated and a non-zero return code will be set.
●
PGTX4520E Invalid SYSIN01 field ffffffff on Record nn: Job terminated
Explanation:
The user executed the Platform Server XCOM interface and specified SYSIN01 parameter ffffffff. This
parameter is invalid. nn specifies the record number within the SYSIN01 dataset that caused the
error. FUSXJOB is terminated and a non-zero return code will be set.
●
PGTX4521E Activity=tttttttttt Status=ssssssss Record Count=rrrrrrrr Byte
Count=bbbbbbbb
Explanation:
The user executed the Platform Server XCOM interface and specified either TYPE=EXECUTE or
TYPE=INQUIRE. This message is displayed each time the Platform Server reads the status of a
transfer request. This message is displayed for informational purposes only.
●
PGTX4522E Activity tttttttttt received Code rr on Inquire: Marking request as
Failed
Explanation:
The user executed the Platform Server XCOM interface and specified either TYPE=EXECUTE or
The Platform Server communicates with the Platform Server started task to get the
status of a transfer request. FUSXJOB received code rr when inquiring on the status of activity tttttttt.
FUSXJOB marks this request as a failed request and based on the PARM CONTINUE parameter, may
continue with the next request.
TYPE=INQUIRE.
●
PGTX4523E Activity tttttttttt received Code rr on Purge: Request not purged from
Queue
Explanation:
The user executed the Platform Server XCOM interface and specified TYPE=EXECUTE. The Platform
Server communicates with the Platform Server started task to purge a transfer request. FUSXJOB
received code rr when purging on the status of activity tttttttt. Therefore the job may not be purged
from the queue.
●
PGTX4524E DSN defined by LCLDS01 must be defined as DISP=SHR: Request terminated
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
134
Explanation:
The user executed the Platform Server XCOM interface and specified either TYPE=EXECUTE or
TYPE=SCHEDULE. The user defined the local dataset to be transferred by the LCLDS01 DD statement.
When LCLDS01 defines the dataset to be transferred, it must be specified as DISP=SHR to avoid a
lockout situation with the Platform Server started task. FUSXJOB is terminated and a non-zero
return code will be set
●
PGTX4525E LCLDS01 DD statement does not specify DSN= on JCL: Request terminated
Explanation:
The user executed the Platform Server XCOM interface, and specified either TYPE=EXECUTE or
TYPE=SCHEDULE. The user defined the local dataset to be transferred by the LCLDS01 DD statement.
When LCLDS01 defines the dataset to be transferred, it must specify the JCL DSN parameter. The
LCLDS01 DD statement did not define a file using the JCL DSN parameter. FUSXJOB is terminated
and a non-zero return code will be set.
●
PGTX4526E FUSXJOB SVC99 Error on Inquire R15=nn Error code=cc Info code=iiii
Explanation:
The user executed the Platform Server XCOM interface and specified either TYPE=EXECUTE or
TYPE=SCHEDULE. The user defined the local dataset to be transferred by the LCLDS01 DD statement.
FUSXJOB attempted to issue a Dynamic Allocation request (SVC99) to get more information on the
file, but FUSXJOB received an error on the SCV99 request. FUSXJOB is terminated and a non-zero
return code will be set. FUSXJOB is terminated and a non-zero return code will be set.
See the return codes displayed in the IBM zOS MVS Programming: Authorized Assembler Services
Guide manual.
●
PGTX4527E SYSIN01 TYPE parameter missing: Job terminated
Explanation:
The user executed the Platform Server XCOM interface and specified either TYPE=EXECUTE or
TYPE=SCHEDULE. The SYSIN01 TYPE parameter is required but was not specified. FUSXJOB is
terminated and a non-zero return code will be set.
●
PGTX4528E SYSIN01 LFILE parameter missing: Job terminated
Explanation:
The user executed the Platform Server XCOM interface and specified either TYPE=EXECUTE or
The LCLDS01 DD statement, or the SYSIN01 LFILE parameter must specify the
local file name. The local file was not defined by either of these methods. FUSXJOB is terminated
and a non-zero return code will be set.
TYPE=SCHEDULE.
●
PGTX4529E SYSIN01 Remote System not defined via LU/IPADDR/IPNAME/LIST parameters:
Job terminated
Explanation:
The user executed the Platform Server XCOM interface, and specified either TYPE=EXECUTE or
TYPE=SCHEDULE. The remote system name must be defined by the LU, IPADDR, IPNAME or
LIST parameters. None of these parameters was defined. FUSXJOB is terminated and a non-zero
return code will be set.
●
PGTX4530E FUSXJOB QUEUE request failed with code rr: mmmmmmmmmmmmmmmmm
Explanation:
The user executed the Platform Server XCOM interface and specified either TYPE=EXECUTE or
TYPE=SCHEDULE. FUSXJOB attempted to queue a request to the Platform Server request queue but
the request failed with code rr. A text message (mmmmm) is displayed along with the return code.
This request fails and based on the PARM CONTINUE parameter, FUSXJOB may continue with the
next request.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
135
●
PGTX4531E XCOMINQ DD required for TYPE=INQUIRE: Job terminated
Explanation:
The user executed the Platform Server XCOM interface and specified TYPE=INQUIRE. DD statement
XCOMINQW is required for this type of request but was not defined in the JCL. FUSXJOB is
terminated and a non-zero return code will be set.
●
PGTX4532E XCOMINQ data invalid: Must start with FUSSEL TRN=
Explanation:
The user executed the Platform Server XCOM interface and specified TYPE=INQUIRE. FUSXJOB read
DD statement XCOMINQW and expected the data to be in the format FUSSEL TRN= starting in
column 1. The data read from DD statement XCOMINQW was not in this format. FUSXJOB
attempts to process the next record in the XCOMINQW file.
●
PGTX4533E SYSIN01 Parameter @1 not supported by Platform Server: Transfer
terminated
Explanation:
The user executed the Platform Server XCOM interface and specified a parameter that was not
supported by the Platform Server. To continue processing this request could cause a problem with
the transfer request. Therefore, the Platform Server terminates the transfer request and a non-zero
return code will be set.
●
PGTX4534E Abend xxx detected: XCOMJOB terminating
Explanation:
The user was executing the Platform Server XCOMJOB interface program. The Platform Server
detected abend xxx. This message indicates that the XCOMJOB program is terminating with errors.
●
PGTX4535E Abend xxx detected: Activity tttttttttt will be purged
Explanation:
The user was executing the Platform Server XCOMJOB interface program. The Platform Server
detected abend xxx. An active transfer was running and the Platform Server was waiting for it to
complete. The Platform Server terminates activity tttttttttt and then the program with errors.
●
PGTF4600E FUSNEWIO INITIALIZATION ERROR: TRANSFER TERMINATED
Explanation:
the Platform Server was executing a Request for MQ, DB2 or Exit processing and received an error
in the initialization. Informational messages will accompany this message. If this message persists
contact TIBCO Technical Support. The transfer request is terminated with errors.
●
PGTF4601E FUSNEWIO Invalid DSN Type specified: Transfer terminated
Explanation:
The Platform Server was executing a request for MQ, DB2 or Exit processing and detected an
internal error processing the request. Informational messages will accompany this message. The
transfer request is terminated with errors.
If this message persists, contact TIBCO Technical Support.
●
PGTF4602E FUSNEWIO Invalid IO type requested: Transfer terminated
Explanation:
The Platform Server was executing a request for MQ, DB2 or Exit processing and detected an
internal error processing the request. Informational messages will accompany this message. The
transfer request is terminated with errors.
If this message persists, contact TIBCO Technical Support.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
136
●
PGTF4603E xxxxx LRECL must be specified for Binary file transfer: Transfer
terminated
Explanation:
The Platform Server was executing a request for MQ, DB2 or Exit processing. When this is done, the
Platform Server requires the LRECL parameter. This can be specified explicitly, or the Platform Server
partner can pass it. For initiator requests, add the LRECL parameter to the Platform Server
parameter. For responder requests, add the LRECL parameter to the remote system’s Platform Server
parameters. The transfer request is terminated with errors.
●
PGTF4604E MQ Load Error on module mmmmmmmm: MQ SCSQLOAD/SCSQAUTH must be in
STEPLIB
Explanation:
The user requested processing an MQ message queue. The Platform Server received an error
loading module mmmmmmmm. In order to process a message queue, the MQ SCSQLOAD and
SCSQAUTH libraries must be concatenated in the STEPLIB of the Platform Server started task. The
transfer request is terminated with errors.
Add the necessary libraries to the Platform Server startup JCL, and stop and start the Platform
Server address space.
●
PGTF4605E Invalid MQ QMGR defined in DSN: Must be 1 to 4 characters after $MQ:
Explanation:
The user requested processing an MQ message queue. The DSN was formatted incorrectly. The
format for the DSN for MQ files is $MQ:qmgr:qname. QMGR must be a 1 to 4 character MQ queue
manager name. The transfer request is terminated with errors.
●
PGTF4606E Invalid DB2 SSN defined in DSN: Must be 1 to 4 characters after $DF: or
$DB:
Explanation:
The user requested processing a DB2 SQL statement. The DSN was formatted incorrectly. The
format for the DSN for DB2 files is $DB:ssn:sql stmt. SSN must be a 1 to 4 character DB2
subsystem name. The transfer request is terminated with errors.
●
PGTF4607E DB2 Load Error on module mmmmmmmm: DB2 SDSNLOAD must be in STEPLIB
Explanation:
The user requested processing a DB2 SQL statement. The Platform Server received an error loading
module mmmmmmmm. In order to process SQL, the DB2 SDSNLOAD library must be concatenated
in the STEPLIB of the Platform Server started task. The transfer request is terminated with errors.
Add the necessary libraries to the Platform Server startup JCL, and stop and start the Platform
Server address space.
●
PGTF4608E NO SQL statements found in DSN or in SQL file
Explanation:
The user requested processing an DB2 SQL statement. The DSN was formatted incorrectly. The
format for the DSN for DB2 files is $DB:ssn:sql stmt. The SQL statement was not found. The
transfer request is terminated with errors.
●
PGTF4609E SQL SELECT valid only for INPUT requests: Request terminated
Explanation:
The user requested processing a DB2 SQL SELECT statement on a Platform Server RECEIVE
request. Select is valid only on a SEND request. The transfer request is terminated with errors.
●
PGTF4610E SQL xxxxxxxx valid only for OUTPUT requests: Request terminated
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
137
Explanation:
The user requested processing a DB2 SQL statement on a Platform Server SEND request. SQL
Request xxxxxxxx is valid only on a RECEIVE request. The transfer request is terminated with errors
●
PGTF4611E SQL xxxxxxx Request not supported: Request terminated
Explanation:
The user requested processing a DB2 SQL statement. SQL Request xxxxxxxx is not supported by the
Platform Server. The transfer request is terminated with errors.
●
PGTF4612E SQL RETURNMSG not allowed for SELECT SQL Statement: Request terminated
Explanation:
The user requested processing a DB2 SQL SELECT statement. Within the SQL statements is a
Platform Server RETURNMSG statement. RETURNMSG is not allowed on SQL SELECT statements.
The transfer request is terminated with errors.
●
PGTF4613E EXIT02 requested but not activated by Global EXIT02 parameter: Request
terminated
Explanation:
The user requested processing a Platform Server exit to process data sent and received. The
GLOBAL EXIT02 parameter was not turned on. Therefore, the Platform Server will not process the
exit request. The transfer request is terminated with errors.
●
PGTF4614E Abend code aaa detected in User EXIT02 program: Request terminated
Explanation:
The user requested processing a Platform Server exit to process data sent and received. The Platform
Server detected an abend within the exit program. The abend code detected was aaa. The Platform
Server recovers from the error and the transfer request is terminated with errors.
●
PGTF4615E Invalid DSN defined by $DF DSN=dddddddddd: Request terminated
Explanation:
The user requested processing a DB2 SQL file. The name of the dataset that contained the SQL
statements was invalid. The correct format for the DSN for DB2 files is $DB:ssn:ddddddd. The
transfer request is terminated with errors.
●
PGTF4616E Error allocating $DF DSN=ddddddddddddd: Request terminated
Explanation:
The user requested processing a DB2 SQL file. The Platform Server attempted to dynamically
allocate file dddddddddddddd, but received an error. The correct format for the DSN for DB2 files is
$DB:ssn:ddddddd. The transfer request is terminated with errors.
Fix the SQL file name and resubmit the request.
●
PGTF4617E Abend aaa opening $DF DSN=ddddddddddddddddddd: Request terminated
Explanation:
The user requested processing a DB2 SQL file. The Platform Server attempted to open file
dddddddddddddd, but received abend aaa. This typically happened because a member name was not
included (abend 013) or the user did not have the necessary authorization to access the file.
Fix the SQL file name and resubmit the request. The transfer request is terminated with errors.
●
PGTF4618E Error opening $DF DSN=ddddddddddddddddd: Request terminated
Explanation:
The user requested processing a DB2 SQL file. The Platform Server attempted to open file
ddddddddddddddbut it failed. The transfer request is terminated with errors.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
138
Fix the SQL file name and resubmit the request.
●
PGTF4619E SYNAD Exit entered for $DF DSN=@1: Request terminated
Explanation:
The user requested processing a DB2 SQL file. The file was opened and an attempt was made to
read the file, but the SYNAD exit was entered reading the file. The transfer request is terminated
with errors.
Verify that the file contents are valid and resubmit the request.
●
PGTF4620E More than 50 SQL requests contained in $DF DSN=ddddddddddd: Request
terminated
Explanation:
The user requested processing a DB2 SQL file. The file was opened and an attempt was made to
read the file. The maximum number of SQL requests in the file exceeded the maximum allowed of
50. The transfer request is terminated with errors.
Fix the SQL file and resubmit the request.
●
PGTF4621E Total SQL length exceeds 4096 for $DF DSN=ddddddddddddd: Request
terminated
Explanation:
The user requested processing a DB2 SQL file. The Platform Server opened the file and was reading
the file. The maximum length of the SQL requests exceeded the maximum allowed of 4096. Fix the
SQL file and resubmit the request. The transfer request is terminated with errors.
●
PGTF4623E DB2 Current MAX Retcode=rr SQL Retcode=ss Reqest=xxxxxxxx
Explanation:
This message is displayed when an error is received processing an SQL request. This message
displays the request (xxxxxxxx), the return code for the request (ss) and the maximum return code
for any request up to this point (rr).
●
PGTF4624E Invalid DSN Specified: Must be $MQ, $DB, $DF or $EX: Request Terminated
Explanation:
An internal error occurred when processing a Platform Server request.
If this message re-occurs, take a trace of the request and contact TIBCO Technical Support.
●
PGTF4625E MQ xxxxxxxx Error RC=rr REA=ss:
ttttttttttttttttttttttttttttttttttttttttt
Explanation:
An error was received when processing an MQ request. The request type (xxxxxxxx) is displayed
along with a return codes (rr) and reason code(ss). At the end of the message is a text description of
the error. The transfer is terminated with errors.
●
PGTF4626E Call to DSNTIAR Failed Request=xxxxxxxx SQLCODE=cccccccc
Explanation:
The Platform Server received an error on an SQL request and attempted to call DB2 program
DSNTIAR to get the text for the error. The SQL request that originally failed was xxxxxxxx and the
SQL code associated with the SQL error was ccccccc. The transfer is terminated with errors.
●
PGTF4627E DB2 CAF xxxxxxxx Error RC=rr REA=ss: ttttttttttttttttttttttttttttttttt
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
139
The Platform Server received an error processing CAF (Call Attached Facility) xxxxxxxx. The return
code is rr and the reason code is ss. A text message is displayed at the end indicating the cause of the
error. The transfer is terminated with errors.
●
PGTF4628E Exit error return code=rr: Queue message follows
Explanation:
The Platform Server was processing a request for a user exit routine, but the routine terminated with
return code rr. In this case, the user exit program should place an error message in the Platform
Server queue record. The actual error message is displayed in a subsequent message. The transfer is
terminated with errors.
●
PGTF4629E tttttttttttttttttttttttttttttttttttttttttttttttttttttttttttt
Explanation:
This message is used to display the text of the error message created by a user file i/o exit program.
●
PGTF4630E Activity tttttttttt failed: MQ BACKOUT executed to restore Message
Queue qqqqqqq
Explanation:
A request was executed that uses an MQ message queue. The request failed. The MQ file is restored
to its initial state by the MQ BACKOUT request. This message is displayed for informational
purposes only.
●
PGTF4670E tttttttttt PDSE Error: Restart not supported on PDSE Program libraries
Explanation:
A checkpoint restart was attempted for a PDSE program library file transfer request. But the restart
is not supported. The file transfer is terminated with errors.
If this problem persists, contact TIBCO Technical Support.
●
PGTF4671E tttttttttt PDSE Error: SMS call ended before EOF reached on Program
library transfer
Explanation:
The Platform Server was performing a PDSE program library transfer request. The file transfer
ended before End Of File was reached on the file. The file transfer is terminated with errors.
If this problem persists, take a trace on the transfer request, and contact TIBCO Technical Support.
●
PGTF4672E tttttttttt PDSE Error: SMS call completed - cannot process tttttttttt
request
Explanation:
The Platform Server was performing a PDSE program library transfer request. The SMS interface
program ended, but the file transfer software still had data to send or receive. tttttttt defines either
GET or PUT. The file transfer is terminated with errors.
If this problem persists, take a trace on the transfer request and contact TIBCO Technical Support.
●
PGTF4673E tttttttttt PDSE Error: SMS xxxxx exit request(yy) invalid
Explanation:
The Platform Server was performing a PDSE program library transfer request. The SMS interface
program supplied an invalid request type (yy) to the Platform Server program. xxxxxxxx defines
either INPUT or OUTPUT. The file transfer is terminated with errors.
If this problem persists, take a trace on the transfer request, and contact TIBCO Technical Support.
●
PGTF4674E tttttttttt PDSE Error: SMS Return Code=rr Reason=ss: Message follows:
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
140
The Platform Server was performing a PDSE program library transfer request. The SMS interface
program ended with a non-zero return code. rr defines the return code while ss defines the reason
code. The file transfer is terminated with errors. This message will be followed with another
message indicating the reason for the failure.
Review the message that follows and take the appropriate action.
●
PGTF4675E tttttttttt PDSE Error: SMS Return Code=rr Reason=ss: No Message
returned
Explanation:
The Platform Server was performing a PDSE program library transfer request. The SMS interface
program ended with a non-zero return code. rr defines the return code while ss defines the reason
code. The file transfer is terminated with errors. There is no text message returned to indicate the
reason for the failure. If this problem persists, contact TIBCO Technical Support.
●
PGTF4680E tttttttttt VSAM Error: Invalid VSAM File type - Must be KSDS, ESDS, or
RRDS
Explanation:
The Platform Server was processing a file transfer request for a VSAM file. The Platform Server
supports KSDS, ESDS and RRDS files, but the file being processed was not one of the supported
types. tttttttttt is the transaction number. The file transfer is terminated, and this message is sent to
the remote system.
●
PGTF4681E tttttttttt VSAM Error: Restart Docket CRC Error Docket=dddddddddddddddddddd
Explanation:
The Platform Server was restarting a file transfer request for a VSAM file. The Platform Server was
validating the restart information (Docket) and found that the information was invalid. tttttttttt is the
transaction number. The file transfer is terminated, and this message is sent to the remote system.
●
PGTF4682E tttttttttt VSAM yyyyyy Error R15=rr R0=zz: tttttttttttttttttttttttttttt
Explanation:
The Platform Server was processing a file transfer request for a VSAM file. The Platform Server
received an error processing the VSAM MODCB, GENCB or TESTCB (yyyyyy) macro. The return
codes were also displayed along with a short text description of the error. tttttttttt is the transaction
number. The file transfer is terminated, and this message is sent to the remote system.
●
PGTF4683E xxxxxxxx VSAM yyyyyy Error R15=rr ACBERFLG=zz:
tttttttttttttttttttttttttt
Explanation:
The Platform Server was processing a file transfer request for a VSAM file. The Platform Server
received an error processing the VSAM OPEN or CLOSE (yyyyyy) macro. The return codes were
also displayed along with a short text description of the error. tttttttttt is the transaction number. The
file transfer is terminated, and this message is sent to the remote system.
●
PGTF4684E xxxxxxxx VSAM yyyyyy Error RTNCD=tt ERRCD=ee: ttttttttttttttttttttttttt
Explanation:
The Platform Server was processing a file transfer request for a VSAM file. The Platform Server
received an error processing the VSAM GET, POINT, ENDREQ or PUT (yyyyyy) macro. The return
codes were also displayed along with a short text description of the error. tttttttttt is the transaction
number. The file transfer is terminated, and this message is sent to the remote system.
●
PGTF4700E MQ Notify Error: Load Error on module xxxxxxxx: MQ SCSQLOAD/SCSQAUTH
must be in STEPLIB
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
141
A Platform Server request attempted to send a notification to an MQ message queue, but it received
an error when attempting to load one of the required MQ programs. mmmmmmmm defines the
program name that could not be loaded. In order to use MQ files under the Platform Server, two
libraries must be in either the LINKLST or the Platform Server STEPLIB: SCSQLOAD and
SCSQAUTH. The request completes, but the MQ notification will not take place.
●
PGTF4701E MQ Notify Error: Invalid MQ QMGR defined: Must be first 1 to 4
characters terminated with :
Explanation:
A Platform Server request attempted to send a notification to an MQ message queue but the queue
manager name was defined incorrectly. When using MQ, the MQ_GOOD/MQ_FAIL parameters must
be specified as xxxx:queue name where xxxx is the MQ queue manager name. The queue manager
name must be from 1 to 4 bytes followed by a colon ( : ). The request completes, but the MQ
notification will not take place.
●
PGTF4702E EMAIL Notify Error: Invalid QUEUE flags passed: Notify terminated
Explanation:
An internal error occurred with the EMAIL/MQ notification.
Contact TIBCO Technical Support if this error re-occurs.
●
PGTF4703E EMAIL Notify Error: Open failed for ddname FUSEMAIL: Notify terminated
Explanation:
The Platform Server EMAIL notification program attempted to open DD Statement FUSEMAIL, but
the open request failed. The EMAIL notification will not take place. Since the EMAIL notification is
performed after the file transfer completes, receipt of this message does not affect the outcome of the
file transfer request.
●
PGTF4704E EMAIL Notify Error: Dynalloc for dddddddd failed: retcode=xx error=yy
Error! Bookmark not defined.zz
Explanation:
The Platform Server EMAIL notification program attempted to dynamically allocate a file, but the
allocate request failed. The DD statement was dddddddd, and the return code information was also
displayed. The EMAIL notification will not take place. Since the EMAIL notification is performed
after the file transfer completes, receipt of this message does not affect the outcome of the file
transfer request.
If this message persists, contact Technical Support.
●
PGTF4705E EMAIL Notify Error: Dealloc for dddddddd failed: retcode=xx error=yy
info=zz
Explanation:
The Platform Server EMAIL notification program attempted to dynamically deallocate a file, but the
deallocate request failed. The DD statement was dddddddd, and the return code information was also
displayed. The EMAIL notification may have been sent, depending on messages received prior to
this message. Since the EMAIL notification is performed after the file transfer completes, receipt of
this message does not affect the outcome of the file transfer request.
If this message persists, contact Technical Support.
●
PGTF4706E MQ Notify Error: MQ rrrrrrrr Error RC=xx REA=yy: ttttttttttttttttt
Explanation:
The Platform Server MQ notification program attempted to write a record to a message queue but
received an error on a request. rrrrrrrr defines the request that received the error, while xx and yy
are the return and reason codes received. A text message (ttt..tttt) that describes the error was also
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
142
displayed Since the MQ notification is performed after the file transfer completes, receipt of this
message does not affect the outcome of the file transfer request
●
PGTS5120E Invalid xxxx Data: yyyy in Queue Entry for Activity zzzz
Explanation:
This message indicates that there is an integrating problem in the work queue.
●
PGTS5300E FMH-7 Received from xxxx Displaying message
Explanation:
An error was received from node xxxx. See the following messages for a description of that error.
●
PGTS5301E Error Message from Remote System: xxxx
Explanation:
An error message was received from the remote system. The remote message is variable.
●
PGTS5304E Error Message from Remote System: xxxx
Explanation:
An error message was received from the remote system. The remote message is variable.
●
PGTS5305E SEND State after getting negotiation for RECEIVE from xxxx Terminating
Explanation:
An internal error occurred with node xxxx.
If xxxx is a VTAM LU enable the Platform Server VTAM tracing (F servername,TRON), if xxxx is an
IP address enable the Platform Server TCP/IP tracing (F servername,TCPTRON), recreate the
problem and contact TIBCO Technical Support.
●
PGTS5306E Recv State after getting negotiation for Send from xxxx - Terminating
Explanation:
An internal error occurred with node xxxx.
If xxxx is a VTAM LU enable the Platform Server VTAM tracing (F servername,TRON), if xxxx is an
IP address enable the Platform Server TCP/IP tracing (F servername,TCPTRON), recreate the
problem and contact TIBCO Technical Support.
●
PGTS5307E Error Message received from Remote System: xxxx for Activity yyyy
Message follows as message 5308
Explanation:
An error message was received from the remote system. See message PGTS5308E for the remote
message.
●
PGTS5308E Remote Message: xxxx
Explanation:
An error message was received from the remote system. This message displays the error that was
received from the remote system.
●
PGTS5309E Restart for activity xxxx failed - No Queue Entry found
Explanation:
Activity xxxx will not be restarted because it is no longer on the queue.
●
PGTS5851E Error Setting up ACB Call for ACB xxxx
Explanation:
An error occurred when setting up ACB xxxx.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
143
Check for other system messages associated with this ACB. If the problem persists, contact TIBCO
Technical Support.
●
PGTS5852E Error Opening ACB for ACB xxxx
Explanation:
An error occurred when opening ACB xxxx.
Check for other system messages associated with this ACB. If the problem persists, contact TIBCO
Technical Support.
●
PGTS5861E Error Setting up Set Logon Call for xxxx
Explanation:
An error occurred setting up the Set Logon call. Check for other system messages. If the problem
persists contact TIBCO Technical Support.
●
PGTS5862E Error Issuing Set Logon for xxxx
Explanation:
An error occurred when issuing the Set Logon call.
Check for other system messages. If the problem persists contact TIBCO Technical Support.
●
PGTS5863E VTAM SETLOGON GNAMEADD for nnnnnnnn failed: SYSPLEX Generic processing
disabled
Explanation:
The GLOBAL APPC_GENERIC_NAME parameter was defined. It caused the Platform Server to issue a
SETLOGON GNAMEADD for Generic name nnnnnnnn, but the GNAMEADD failed. Additional
messages give the return code and a text explanation of the error.
●
PGTS5900E xxxx
Explanation:
An internal error occurred.
Contact TIBCO Technical Support.
●
PGTS5901E Error Encountered initializing APPC Subtask - Check REGION Parameter on
EXEC statement
Explanation:
The subtask could not allocate enough storage to start.
Increase the Region parameter on the EXEC statement of the started task and re-submit the transfer.
●
PGTS5902E Error Encountered for Activity xxxx occurred issuing [ALLOC | CONNECT]
RC=yyyy
Explanation:
An error occurred when activity xxxx attempted an ALLOC or CONNECT, return code yyyy.
●
PGTS5903E Error Encountered for Activity xxxx sending Control Record to [yyyy |
nnn.nnn.nnn.nnn], Terminating
Explanation:
An error occurred when sending control information for activity xxxx to LU yyyy or IP address
nnn.nnn.nnn.nnn.
Check the console log for further information.
●
PGTS5904E Error Encountered for Activity xxxx Negotiating Control Record to [yyyy
| nnn.nnn.nnn.nnn]
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
144
Explanation:
An error occurred when negotiating control information for activity xxxx to LU yyyy or IP address
nnn.nnn.nnn.nnn.
Check the console log for further information.
●
PGTS5905E File Access Error on xxxx DSN: yyyy
Explanation:
The file to be used for the transfer could not be accessed.
●
PGTS5907E Dynamic Allocation Error xxxx Activity: yyyy DSN: zzzz
Explanation:
An error occurred when trying to dynamically allocate data set zzzz for activity yyyy. Return code
xxxx. Check the log for other allocation-related errors. Correct the problem and re-submit the
transfer.
●
PGTS5909E Invalid Document type of xxxx for Activity yyyy
Explanation:
The document type specified in the work queue entry for the named activity was invalid for the
target remote system.
Re-issue the request.
●
PGTS5991E Currently Unsupported protocol: xxxx requested for Activity yyyy purging request
Explanation:
The user requested that the file transfer to be done using a protocol for which no driver was
installed. For example, the user might have requested TFTP but the driver for TFTP was not
installed.
Contact your sales representative to order additional product features.
●
PGTS6100E ERROR CREATING DATASPACE: xxxx
Explanation:
An error occurred when creating dataspace xxxx. Accompanying messages should show the return
codes received while trying to create the dataspace.
●
PGTS6814E ERROR CREATING OSIQUEUE, IN MODULE OSISDDC0
Explanation:
An error occurred when creating the OSIQUEUE dataspace. Accompanying messages should show
the return codes received while trying to create the dataspace.
●
PGTS6820E ERROR MAPPING OSIQUEUE TO LINEAR VSAM DATASET
Explanation:
An error occurred when mapping the OSIQUEUE dataspace to a linear VSAM file. Accompanying
messages should show the return codes received while trying to map the dataspace
●
PGTS6900E ERROR DELETING DATASPACE xxxx
Explanation:
An error occurred deleting dataspace xxxx. Accompanying messages should show the return codes
received while trying to delete the dataspace.
●
PGTM7100E Error Loading Module xxxx
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
145
An error occurred loading transmission code.
Contact TIBCO Technical Support for assistance.
●
PGTM7101E Error Returned from Module xxxx, RC=yyyy
Explanation:
Contact TIBCO Technical Support if you receive this message.
●
PGTM7201E Activity tranid failed by Installation Authorization exit (EXIT01)
Explanation:
The Platform Server Transfer Authorization Checking Exit indicated that the user was not
authorized to use the Platform Server or did not have access the dataset in question.
●
PGTM7218E RACROUTE AUTH failure for Activity xxxx R15 RC=yyyy SAF RC=zzzz
Explanation:
Local security denied access to data set. Appropriate diagnostic was sent to remote side.
●
PGTM7219E Invalid xxxx exceeds max length 8 for Activity yyyy
Explanation:
The maximum length for xxxx is 8.
●
PGTM7220E RACROUTE VERIFY failure for Activity xxxx R15 RC=yyyy SAF RC=zzzz
Explanation:
The userid is not defined to RACF.
●
PGTM7221E Data set OPEN failed for activity xxxx
Explanation:
The data set specified in the transfer could not be opened.
●
PGTM7222E GDG Base xxxx not found in catalog for activity yyyy
Explanation:
The GDG specified in the transfer could not be found in the catalog.
Verify that the GDG specified exists.
●
PGTM7223E Invalid DCB fields on File CREATE: xxxxxxxx - RECFM=yy
Explanation:
The Platform Server was about to create a new file and was validating the DCB information. The
Platform Server detected invalid DCB information. The RECFM defined was yy (this may have been
the default value), and the parameter in error was xxxxxxxx. This message will be displayed and the
transfer request will fail.
●
PGTM7224E << IBM Error message>>
Explanation:
A dynamic allocation failure occurred. The associated allocation error message is displayed.
See the appropriate IBM Messages manual for a detailed description of the failure. Correct the error
and re-submit the transfer.
●
PGTM7225E DYNALLOC Failed R15=xxxx RC=yyyy Info Reason Code=zzzz Error RC=nnnn
Explanation:
A dynamic allocation failure occurred. Register 15 is xxxx. The return code is yyyy, the information
reason code is zzzz, the error code is nnnn. The associated error message, if any, will be issued with
PGTM7224E.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
146
Correct the problem and re-submit the transfer.
●
PGTM7226E DYNALLOC failed due to invalid xxxx “yyyy”
Explanation:
An invalid parameter was passed to dynamic allocation where xxxx is the name of the parameter
and yyyy is that parameter.
Correct the error and re-submit the transfer.
●
PGTM7227E Generation of GDG is invalid for Activity xxxx
Explanation:
The generation of GDG was invalid.
Make sure that it is a valid number.
●
PGTM7231E Error xxxx writing for Activity yyyy to DSN: zzzz
Explanation:
An error occurred for activity yyyy writing to data set name zzzz. The error code is the system abend
issued during the write.
Correct the error and re-submit the transfer.
●
PGTM7232E Error xxxx reading for Activity yyyy to DSN: zzzz
Explanation:
An error occurred for activity yyyy reading from data set name zzzz. The error code is the system
abend issued during the read.
Correct the error and re-submit the transfer.
●
PGTM7233E Error Determining JOBID for Activity xxxx
Explanation:
The system was having trouble determining the JOBID for the job that was submitted to the system
from a Platform Server file to job transfer.
●
PGTM7234E Data would be Truncated: xxxx Canceled DSN: yyyy
Explanation:
The file being transferred had a larger record length then the record length specified in the transfer.
If no record length was specified in the transfer, then the default was used from the global.
Add or increase the record length and re-submit the transfer.
●
PGTM7235E E37 Out of Space Condition see message IEC032I, DSN: xxxx
Explanation:
There was not enough space on the specified volume for the data set being transferred. If no volume
was specified in the transfer, then the default was used from the global.
Add or change the volume parameter in the transfer to a volume with more space and re-submit the
transfer.
●
PGTM7236E B37 Out of Space Condition see message IEC030I, DSN: xxxx
Explanation:
The space parameter was too small for the data set that was being transferred. The file being
transferred was larger than the space specified in the transfer. If no space was specified in the
transfer, then the default was used from the global.
Add or increase the ALLOC_PRI and ALLOC_SEC parameters in the transfer and re-submit.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
147
●
PGTM7237E xxxx B14 abend on CLOSE of PDS member yyyy
Explanation:
Activity xxxx attempted to CLOSE data set yyyy when a SB14 abend occurred.
See the accompanying IEC217I message for more details. Correct the problem and re-submit the
transfer
●
PGTM7238E Activity xxxx Data set not found in catalog: yyyy
Explanation:
Check the name of the data set used in the transfer. It may be incorrect or misspelled.
●
PGTM7239E Activity xxxx Absolute track request: yyyy
Explanation:
During an MVS to MVS transfer the data set yyyy was found to be allocated with an absolute track
address. As the physical positioning of these type of data sets can be critical, the transfer was
canceled.
●
PGTM7240E Activity xxxx Unrecognized allocation type: yyyy
Explanation:
The valid Allocation Types are Cylinders, Tracks, Blocks, Megabytes and Kilobytes.
●
PGTM7241E PDS file selected without member name - remote does not support library
transfers
Explanation:
The remote system supports the transfer of a PDS member and not the entire PDS.
●
PGTM7242E PDS file selected without member name - Remote File is not a PDS
Explanation:
The remote system supports the transfer of a PDS member and not the entire PDS. The member
name should be entered in the following format: PDS.LIBRARY.NAME(MEMBER).
●
PGTM7243E Member name not allowed for a sequential file
Explanation:
The system had determined that the dataset specified for the transfer was a sequential file, and it
should not contain a member name in parenthesis.
If you wish to send a member of a PDS, make sure that it exists on the system.
●
PGTM7244E Generic member invalid when remote does not support library transfers
Explanation:
The remote system supported the transfer of a PDS member and not the entire PDS. A specific
member name should be specified in the following format: PDS.LIBRARY.NAME(MEMBER)
●
PGTM7245E Generic member invalid when remote file is not a library
Explanation:
A PDS member name cannot be specified when the remote file is not a library.
●
PGTM7246E DCB field xxxxxxxx required when Allocation type is K(ilo) or M(eg)
Explanation:
The Platform Server was about to create a new file and was validating the DCB information. The
user requested an allocation type of K(ilo) or M(eg). When allocating files in this manner, DCB
parameter xxxxxxxx must be defined. This message will be displayed and the transfer request will
fail.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
148
●
PGTM7247EMember xxxx not found in PDS file (RC=S013) for DSN yyy - Activity zzz
Explanation:
The member name specified was not found in the PDS file or it may be misspelled.
●
PGTM7248E Open error for PDS directory (RC=0254) for DSN xxxx - Activity yyyy
Explanation:
An error occurred opening the directory for PDS yyyy for activity xxxx.
Review the system log for associated system messages. Correct the error and re-submit the transfer.
●
PGTM7249E Not authorized to open file (RC=S913) for DSN xxxx - Activity yyyy
Explanation:
The userid specified does not have access to the file specified in the transfer.
●
PGTM7250E DSN does not match Tape label (RC=0813) for DSN xxxx - Activity yyyy
Explanation:
The data set name specified in the transfer does not match what is on the tape.
●
PGTM7251E Volume out of space or no extents available (RC=SB37) - DSN xxxx
Activity yyyy
Explanation:
There was not enough space on the volume specified to complete this transfer. If no volume was
specified in the transfer, the volume specified in the Global is used.
●
PGTM7252E Out of space on Primary and no secondary allocation (RC=SD37) - DSN
xxxx Activity yyyy
Explanation:
There was not enough space specified to complete this transfer.
Increase the value for the ALLOC_PRI parameter. You can also add the ALLOC_SEC parameter. If these
parameters were not specified in the transfer, the defaults specified in the Global is used.
●
PGTM7253E Volume out of space or no extents available (RC=SE37) - DSN xxxx
Activity yyyy
Explanation:
There was not enough space on the volume specified to complete this transfer. If no volume was
specified in the transfer, the volume specified in the Globals will be used.
●
PGTM7254E SYNAD routine entered for file (RC=100C) - DSN xxxx Activity yyyy
Explanation:
An internal error occurred opening data set yyyy for activity xxxx.
Contact TIBCO Technical Support.
●
PGTM7255E File open Failed (RC=1004) - DSN xxxx Activity yyyy
Explanation:
An open error occurred on data set yyyy for activity xxxx.
Check the system log for further information.
●
PGTM7256E Getmain for IO buffers failed (RC=1020) - DSN xxxx Activity yyyy
Explanation:
The Platform Server had insufficient storage to obtain buffers for I/O to data set yyyy for activity
xxxx.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
149
Increase the region size for the Platform Server or reduce the number of concurrent transfers.
●
PGTM7257EWrong length record found on RECFM=F file (RC=1024) DSN xxxx Activity
yyyy
Explanation:
An I/O error occurred on data set yyyy for activity xxxx. The most likely cause is data corruption.
Rebuild the data set and re-submit the transfer.
●
PGTM7258E Invalid blocking on RECFM=V file (RC=1028) DSN xxxx Activity yyyy
Explanation:
The block size of variable blocked data set yyyy for activity xxxx was invalid.
Correct the dataset attributes and re-submit the transfer.
●
PGTM7259E Restart requested for QSAM file (RC=1030) DSN xxxx Activity yyyy
Explanation:
An internal error occurred.
Contact TIBCO Technical Support.
●
PGTM7260E Checksum error on restart (RC=1040) DSN xxxx Activity yyyyy
Explanation:
An error occurred when attempting to do a check point restart on data set yyyy for activity xxxx.
Re-submit the transfer.
●
PGTM7261EMember xxxx not found in Library yyyy (RC=1304) Activity zzzz
Explanation:
When attempting to transfer member xxxx from data set yyyy for activity zzzz, the member was not
found.
Change the member name and re-submit the transfer.
●
PGTM7262E I/O error or Insufficient Storage on FIND macro (RC=1308) DSN xxxx
Activity yyyy
Explanation:
When attempting to FIND a member in data set xxxx for activity yyyy an error occurred. The error is
either an I/O error, or there is insufficient storage in the region.
If an I/O error occurred, the data set could be corrupted, re-build the data set. If there is insufficient
storage, reduce the number of concurrent transfers or increase the region size.
●
PGTM7263E Directory already contains member xxxx (RC=1404) DSN yyyy Activity zzzz
Explanation:
An attempt to write member xxxx to data set yyyy for activity zzzz found that the member already
existed.
Either change the member name on the transfer, or delete the current member.
●
PGTM7264E No space in directory for member xxxx (RC=140C) DSN yyyy Activity zzzz
Explanation:
When attempting to update the directory of data set yyyy with member xxxx for activity zzzz, there
was insufficient space to add the entry.
Rebuild the data set with more directory blocks and re-submit the transfer.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
150
●
PGTM7265E I/O error processing member xxxx on STOW (RC=1410) DSN yyyy Activity
zzzz
Explanation:
When attempting to add member xxxx to data set yyyy for activity zzzz an I/O error occurred. The
likely cause is data set corruption.
Re-build the data set and re-submit the transfer.
●
PGTM7266E Insufficient virtual storage on STOW macro (RC=1418) DSN xxxx Activity
yyyy
Explanation:
When attempting to add a member to data set xxxx for activity yyyy, the STOW failed due to
insufficient storage.
Reduce the number of concurrent transfers or increase the region size for the Platform Server and
re-submit the transfer.
●
PGTM7267E Unable to store data into PDSE program library (RC=141C) DSN xxxx
Activity yyyy
Explanation:
An attempt to store data in data set xxxx for activity yyyy failed because this data set was a program
library which the Platform Server does not support.
Change the target data set to a non-program library and re-submit the transfer.
●
PGTM7268E Alias xxxx contains invalid TTR on STOW (RC=1424) DSN yyyy Activity
zzzz
Explanation:
When attempting to update the directory of data set yyyy with alias xxxx, the directory entry
contained an invalid TTR. The alias entry is not inserted.
●
PGTM7269E PDSE directory cannot contain user data TTRs (RC=1428) DSN xxxx
Activity yyyy
Explanation:
During transfer of dataset xxxx from a PDS to a PDSE, user data in the directory entry from the PDS
is not supported by the PDSE format. The member is not saved.
●
PGTM7270E PDSE STOW failed - File opened for update (RC=1428) DSN xxxx Activity
yyyy
Explanation:
During transfer yyyy to PDSE xxxx the update of the directory failed because the data set was
already opened for update.
Make sure that the Platform Server has exclusive control of the PDSE and re-submit the transfer.
●
PGTM7271E Actual member not found sending alias xxxx (RC=1500) DSN yyyy Activity
zzzz
Explanation:
When attempting to transfer alias xxxx from data set yyyy for activity zzzz, the alias had become
disconnected from the actual member.
Either restore the member or remove the alias and re-submit the transfer.
●
PGTM7272EMember xxxx not found on PDS BLDL while processing alias (RC=1604) DSN
yyyy Activity zzzz
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
151
While transferring an alias of member xxxx in data set yyyy for activity zzzz, the actual member
could not be found. The alias had become disconnected from the member.
Either restore the member or remove the alias and re-submit the transfer.
●
PGTM7273E I/O error or Insufficient Storage on FIND macro (RC=1308) DSN xxxx
Activity yyyy
Explanation:
When attempting to do a FIND on data set xxxx for activity yyyy, there was insufficient storage to
complete the request.
Either increase the region size of the Platform Server region or reduce the number of simultaneous
transfers.
●
PGTM7274E I/O Retcode xxxx processing DSN yyyy Transaction zzzz
Explanation:
An unexpected condition occurred.
Check the console log for related messages. Contact Platform Technical support if the error is not
apparent.
●
PGTM7275E Out of space in directory on CLOSE (RC=SB14) DSN xxxx Activity yyyy
Explanation:
The number of directory blocks specified for the library was exceeded.
Increase the number of directory blocks and try the transfer again.
●
PGTM7276E Specific transfer of RECFM=U Alias not supported (RC=1501) DSN xxxx
Activity yyyy
Explanation:
The record format of undefined is not supported for this transfer.
●
PGTM7277E Abend xxxx received reading directory of DSN yyyy Activity zzzz
Explanation:
An error occurred while reading the directory that contained the data set specified in the transfer.
●
PGTM7278E Abend 213-xx opening DSN dddddddddddd: mmmmmmmmm - Activity tttttttttt
Explanation:
The Platform Server received abend 213 reason code xx processing dataset dddddddddd. mmmmmmm
describes the error. The file transfer request was terminated with errors.
●
PGTM7279E Spanned records not supported by Checkpoint Restart: DSN ddddddd
Activity ttttttttt
Explanation:
A file transfer request was made that involved variable spanned records. The Platform Server
supports variable spanned records, but it does not support variable spanned records when
restarting a file transfer request. When processing variable spanned records, the user must not use
checkpoint restart. The file transfer is terminated and a message is sent to the transfer partner.
●
PGTM7280E PDS/E program Object libraries not supported for Send or Receive
Explanation:
The Platform Server attempted to process a PDS/E program object library. The Platform Server does
not support processing of program objects. The file transfer is terminated, and this message is sent
to the Platform Server system.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
152
●
PGTM7282E tttttttttt DBCS data invalid: Transfer terminated - DBCS Data=xxyy
Explanation:
The Platform Server was performing DBCS conversion. The Platform Server detected a ShiftOut
character and was attempting to perform DBCS conversion for the characters following the ShiftOut,
but the data following the ShiftOut was invalid. The invalid data characters are displayed. The
transfer request is terminated with errors.
Make sure that the file to be converted contains valid DBCS characters.
●
PGTM7283E tttttttttt DBCS data invalid: Transfer terminated - Not enough data
left to complete DBCS Translation
Explanation:
The Platform Server was performing DBCS conversion. The Platform Server detected that DBCS
conversion must be performed but there was not enough data left in the record to convert the
necessary characters. For data that uses SOSI characters, it means that there were not at least three
characters left (two for the DBCS and one for the SI character). For data that does not use SOSI
characters, it means that there are less then two characters left. The transfer request is terminated
with errors.
Make sure that the file to be converted contains valid DBCS characters.
●
PGTM7284E tttttttttt DSN=dddddddddd Transfer not allowed for ALIAS with 1
qualifier
Explanation:
The user executed a transfer that attempted to update a file. The file had only one qualifier, and that
qualifier was a z/OS alias. The request was rejected because this alias typically points to a user
catalog. The transfer is terminated with errors and the dataset defined by the DSN in this message is
not updated.
●
PGTM7286E tttttttttt File Delete initiated by DISP=DNEW Failed - Transfer
terminated: dddddddddd
Explanation:
Platform Server attempted to delete file dddddddd due to the LDISP=DNEW or RDISP=DNEW parameter,
but the delete failed. The OSIMSG log should have more information about the reason why the file
DELETE failed. The transfer is terminated.
●
PGTM7287E tttttttttt DISP=DNEW not supported for VSAM file - Transfer terminated:
dddddddddd
Explanation:
Platform Server attempted to delete file dddddddd due to the LDISP=DNEW or RDISP=DNEW parameter,
but the delete failed because the DNEW parameter cannot be used for VSAM files. The transfer is
terminated with an error.
●
PGTM7288E tttttttttt Security Authorization failed for DISP=DNEW Delete: Transfer
termninated: dddddddddd
Explanation:
Platform Server attempted to delete file dddddddd due to the LDISP=DNEW or RDISP=DNEW parameter.
The security authorization check failed, possibly because the user was not authorized to delete the
file. The OSIMSG log should have more information about the reason why the authorization check
failed. The transfer is terminated with an error.
●
PGTM7289E tttttttttt OBTAIN for DSCB3 Failed RC=rr Proceeding without DSCB3:
dddddddddd
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
153
Platform Server was sending a dataset and was attempting to extract the space allocation values for
the dataset. An attempt was made to execute the OBTAIN macro to read DSCB3 and get information
on secondary extents, but it received an error. The return code for the OBTAIN was rr. The file
transfer is completed and the space allocation values are computed without using the DSCB3.
●
PGTM7290E tttttttttt UCBSCAN Failed for Volser=vvvvvv: R15=rr R0=rr: dddddddddd
Explanation:
Platform Server was sending a dataset and was attempting to extract the space allocation values for
the dataset. An attempt was made to execute the UCBSCAN macro to get information on device, but
it received an error. The return code for the UCBSCAN was rr (R15 and R0). The file transfer is
completed, and the space allocation values are computed by using default values.
●
PGTM7291E tttttttttt DEVTYPE Failed for Volser=vvvvvv: R15=rr R0=rr: dddddddddd
Explanation:
Platform Server was sending a dataset and was attempting to extract the space allocation values for
the dataset. An attempt was made to execute the DEVTYPE macro to get information on device, but
it received an error. The return code for the DEVTYPE was rr (R15 and R0). The file transfer is
completed, and the space allocation values are computed by using default values.
●
PGTM7292E tttttttttt TRKCALC Failed R15=rr BLKSIZE=bbbbb BlocksPerTrack=nn:
dddddddddd
Explanation:
Platform Server was sending a dataset and was attempting to extract the space allocation values for
the dataset. An attempt was made to execute the TRKCALC macro to determine the number of
blocks in a track, but it received an error. The return code for the TRKCALC was rr. The file transfer
is completed, and the space allocation values are computed by using default values.
●
PGTM7296E tttttttttt Transfer failed: ddddddd will not expire until yyyy.ddd
Explanation:
A transfer receive request was made for file dddddddd. An expiration date was specified for this file,
but the file had not expired. The transfer terminates with a permanent error.
To transfer data to this file, either wait for the file expiration date to expire or realloacte the file
without an expiration date.
●
PGTM7298E tttttttttt LBI supports only RECFM=U when CKPT enabled: dddddddddd
Explanation:
A transfer was initiated with for a tape file that supported the LBI (Large Block Interface) and
checkpoint restart was specified. For LBI files, only RECFM=U files are supported using checkpoint
restart.
Change the transfer so that checkpoint restart is not used and resubmit the transfer.
●
PGTM7299E tttttttttt Transfer failed: dddddd File Expiration is Permanent
Explanation:
The transfer failed for transaction tttttttttt. Dataset dddddddd was defined as a permanent dataset
with no expiration. The GLOBAL parameter UNEXPIRED_DISK_FILE_DELETE or
UNEXPIRED_DISK_FILE_UPDATE was set to No and delete or update was requested.
If you want to update the file, either change the expiration date for the file, or set the GLOBAL
parameter to allow a delete or updated of an unexpired file.
●
PGTM7301E Error Obtaining Storage RC=xxxx in yyyy
Explanation:
A STORAGE OBTAIN macro failed with the return codes indicated in the message.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
154
●
PGTM7310E HFS File create failed - Directory xxxxxxxxxxxx does not exist for
Activity tttttttttt
Explanation:
The user attempted to create a file because there was a forward slash (/) in the file name. The
Platform Server processed this as a USS (Unix Systems Services) file. A check if the directory
associated with the file existed found that the directory did not exist. The Platform Server therefore
cannot create a file in a directory that does not exist. The transfer terminates with an error.
Either create the directory where the file can be stored, or change the directory name within the file
transfer request.
●
PGTM7317E Tape Open xxx abend: Unable to extract DCB information
Explanation:
The Platform Server attempted to open a tape file for input in order to extract the DCB information
from the tape. The open failed with abend code xxx.The transfer is terminated with errors. The
Platform Server will continue processing, but it will use the default DCB information.
Make sure that the Platform Server has read authorization for any tapes that are used.
●
PGTM7318E Tape Open Failed: Unable to extract DCB information
Explanation:
The Platform Server attempted to open a tape file for input in order to extract the DCB information
from the tape. The open failed. The transfer is terminated with errors. The Platform Server will
continue processing but will use default DCB information.
Make sure that the Platform Server has read authorization for any tapes that are used.
●
PGTM7319E EDTINFO Request failed for unit xxxxxxxx : RetCode=yyyyyyyy
Reason=zzzzzzzz
Explanation:
During new data set allocation, the Platform Server issued an EDTINFO call to validate the device
type specified by the user but device type xxxxxxxx was found to be invalid for the system. When
the EDTINFO fails, it is assumed that the request is for a disk resource. No special tape processing is
performed. The request continues processing.
See the RetCode yyyyyyyy and Reason zzzzzzzz in the IBM MVS Programming: Assembler Services
Reference, Volume 1 (ABE-HSP) manual.
●
PGTM7320E UCBLOOK Request failed for Device ddd: RetCode=rr Reason=ss
Explanation:
The Platform Server was processing a z/OS UCBLOOK request for device ddd, but it received an
error. The return code was rr and the reason code was ss. When the UCBLOOK failed, it is assumed
that the request was for a disk resource. No special tape processing was performed. The request
continues processing.
●
PGTM7322E tttttttttt Permanent error returned from HSM exit for DSN=dddddddddd:
Request will be purged
Explanation:
The HSM user exit (turned on by setting the GLOBAL EXIT03=YES and EXIT_MIGRATE_VOLUME
parameters) returned an error indicating that a permanent error occurred processing the recall
request. The Platform Server will notify the remote system of the error, and will purge the request
from its transaction queue.
●
PGTM7323E tttttttttt Dataset not found after HSM exit returned: DSN=dddddddddd:
Request will be purged
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
155
The HSM user exit (turned on by setting the GLOBAL EXIT03=YES and EXIT_MIGRATE_VOLUME
parameters) returned a code indicating that the dataset RECALL was successful. The Platform
Server issued a LOCATE to find the dataset, but the dataset was not found. This is treated as a
permanent file error. The Platform Server will notify the remote system of the error, and it will
purge the request from its transaction queue.
●
PGTM7324E tttttttttt LOCATE returned MIGRATION volume after HSM exit:
DSN=dddddddddd: Request will be purged
Explanation:
The HSM user exit (turned on by setting the GLOBAL EXIT03=YES and EXIT_MIGRATE_VOLUME
parameters) returned a code indicating that the dataset RECALL was successful. The Platform
Server has issued a LOCATE to find the dataset. The dataset was found, but the volume that was
returned was the same as the volume before the RECALL was performed. This indicates that the
RECALL was not successful. This is treated as a permanent file error. The remote system is notified
of the error, and the request is purged from its transaction queue.
●
PGTM7325E tttttttttt Match on GLOBAL EXIT_MIGRATE_VOLUME but EXIT03 is inactive:
Request will be purged
Explanation:
The Platform Server found a match on the GLOBAL EXIT_MIGRATE_VOLUME. This means that a
dataset was processed that required HSM exit processing. However, the user did not set the
EXIT03=ON parameter. Therefore, the Platform Server was unable to branch to an exit to process the
request. This is treated as a permanent file error. The remote system is notified of the error, and the
request is purged from its transaction queue.
If the EXIT_MIGRATE_VOLUME parameter is defined, set the GLOBAL EXIT03=YES parameter also.
Additionally, assemble the FUSEX03 module and link-edit into the Platform Server STEPLIB.
●
PGTM7326E tttttttttt Wait time for HSM Exit exceeds GLOBAL
EXIT_MIGRATE_WAIT_TIME: Request will be retried
Explanation:
The HSM user exit (turned on by setting the GLOBAL EXIT03=YES and EXIT_MIGRATE_VOLUME
parameters) returned a code indicating that the dataset RECALL was in process and that
CyberFusion should wait for it to complete. The Platform Server waited the amount of seconds
defined in the GLOBAL EXIT_MIGRATE_WAIT_TIME, and the request was not completed. The
Platform Server will mark the request as a temporary error and will retry the request when the
GLOBAL FILE_ERROR_RETRY_INTERVAL expires.
If the recall requests are taking too long, increase the number of seconds specified in the GLOBAL
parameter.
EXIT_MIGRATE_WAIT_TIME
●
PGTM7327E tttttttttt Dataset not found after HSM Recall: DSN=dddddddddd: Request
will be purged
Explanation:
A dataset migrated by HSM was detected. The volume associated with the dataset matched the
GLOBAL HSM_MIGRATE_VOLUME parameters. The dataset was successfully recalled. A LOCATE
command was issued to find the dataset, but the dataset was not found. This is treated as a
permanent file error. The Platform Server will notify the remote system of the error and will purge
the request from its transaction queue.
●
PGTM7328E tttttttttt LOCATE returned MIGRATION volume after HSM recall: DSN=@2:
Request will be purged
Explanation:
A dataset migrated by HSM was detected. The volume associated with the dataset matched the
GLOBAL HSM_MIGRATE_VOLUME parameters. The dataset was successfully recalled. A LOCATE
command was issued to find the dataset. The volume returned by the LOCATE command matched
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
156
the GLOBALHSM_MIGRATE_VOLUME. This means that the recall was not successful. This is treated as
a permanent file error. The Platform Server will notify the remote system of the error and will purge
the request from its transaction queue.
●
PGTM7329E tttttttttt HSM RECALL Permanent error for DSN=dddddddddd: Detailed
message follows
Explanation:
The Platform Server issued a recall for migrated HSM dataset ddddd. The request failed with a
permanent error. A more detailed message follows with information about the error. This is treated
as a permanent file error. The Platform Server will notify the remote system of the error and will
purge the request from its transaction queue.
●
PGTM7330E HSM RECALL failed with RC=rr: ttttttttttttttttttttttttttttttttt
Explanation:
The Platform Server issued a recall for migrated HSM dataset ddddd. The request failed with error
code rr. A description of the error is also displayed. Based on the error code, this may be treated as a
retry-able or permanent error. Additional messages that are displayed indicate if the error is
permanent or can be retried.
●
PGTM7331E tttttttttt HSM RECALL Retryable error for DSN=dddddddddd: Detailed
message follows
Explanation:
The Platform Server issued a recall for migrated HSM dataset ddddd. The request failed with a
temporary error. A more detailed message follows with information about the error. The Platform
Server will mark the request as a temporary error and will retry the request when the GLOBAL
FILE_ERROR_RETRY_INTERVAL expires.
●
PGTM7333E Activity tttttttttt DSN=dddddddddd HFS create requires USER Read/Write
permissions
Explanation:
The user attempted to create an HFS dataset on the Platform Server for z/OS. The user entered the
UNIXPERM parameter to define the UNIX file permissions, but the user permissions were
inadequate. When creating an HFS file, the file permissions muse be at least READ and WRITE.
Without these permissions, a file cannot be written. The file transfer is terminated, and this error
message is sent back to the remote system.
●
PGTM7334E Activity tttttttttt Userid not defined: Transfer terminated
Explanation:
A file transfer was attempted, but the Platform Server detected that the userid was not entered. The
userid was either all nulls or all blanks. This message is displayed and sent to the remote system.
The transfer is terminated with errors.
Make sure that the userid and password parameters are defined correctly before attempting the
transfer again.
●
PGTM7341E Activity tttttttttt PDSE Program objects cannot be sent to Non "PDSE
Program Libraries”
Explanation:
The Platform Server attempted to transfer PDSE members. There are two types of PDSE files: Data
libraries and Program libraries. PDSE Data libraries can transfer information with any other file
type. PDSE Program libraries can transfer information only with other PDSE program libraries. This
message indicates that one of the files to be transferred was a PDSE program library, while the other
file was not a PDSE program library. The file transfer request terminates and this message is sent to
the remote end. If you with to transfer PDS loadlib members, the remote file must be a PDS loadlib.
If you wish to transfer PDSE Program objects, the remote file must be a PDSE program library.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
157
●
PGTM7343E Activity tttttttttt Conversion Table cccccccccc not found: Transfer
terminating with errors
Explanation:
The Platform Server for z/OS attempted to perform data conversion using a Conversion Table Entry
(XLATE), but the Platform Server could not find an enabled XLATE entry with the same name. The
XLATE entry must be in the CONFIG DD statement, and must be enabled through the CONFIG
member at startup or through the ENABLE operator command. The file transfer request terminates
with errors and this message is sent to the conversation partner.
Make sure that the conversion table entry is defined and enabled correctly.
●
PGTM7344E tttttttttt Local User=uuuuuuuuuu VERIFY failed R15/R0=rr ss: tttttttttt
Explanation:
The Platform Server user entered the LUSER and LPASS parameters to enable a user to submit a file
transfer request under a different userid. The Platform Server was validating the userid and
password combination and received an error. The return codes (rr ss) and a description of the error
was displayed. The transfer terminates with errors. Check the LUSER and LPASS parameters to
make sure that the information is correct.
●
PGTM7347E tttttttttt Transfer failed for DSN dddddddddd: MAINTAINRDW only
supported for RECFM V/VB
Explanation:
The user attempted to perform a transfer for file dddddddddd and specified the MAINTAINBDW or
MAINTAINRDW parameter. These parameters are only supported when RECFM=V/VB is defined. The
transfer is terminated with an error.
Make sure that if you specify MAINTAINBDW or MAINTAINRDW that the file has RECFM=V/VB.
●
PGTM7350E Failed to delete VSAM File dddddddddd RC=xx: See OSIMSG output for more
details
Explanation:
The user entered a disposition of DNEW. It indicates that if a file exists, it should be deleted and reallocated before the file transfer is started. The zOS IDCAMS utility is used to delete the file, but
IDCAMS returned an error. The IDCAMS output is displayed in the started task OSIMSGS output.
●
PGTM7351E Call to IDCAMS failed with RETCODE=xx
Explanation:
The user entered a function to call the zOS IDCAMS utility. IDCAMS failed with a return code of
XX. Generally, other messages are displayed with more detailed information about the cause of the
error.
●
PGTM7352E Obtain Failed - R15=xx for DSN dddddddd: record returned without file
size
Explanation:
MFT was responding to an MFT Internet Server request for information about a file. MFT issued the
OBTAIN macro for file dddddddd but the request failed with return code xx. The request will
complete, but MFT will not return the file size to the caller.
●
PGTM7353E UCBSCAN Failed - R15=xx R0=yy for DSN dddddddddd: record returned
without file size
Explanation:
MFT was responding to an MFT Internet Server request for information about a file. MFT issued the
UCBSCAN macro for file dddddddd but the request failed with return code xx yy. The request will
complete, but MFT will not return the file size to the caller.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
158
●
PGTM7354E TRKCALC Failed - R15=xx R0=yy for DSN dddddddddd: record returned
without file size
Explanation:
MFT was responding to an MFT Internet Server request for information about a file. MFT issued the
TRKCALC macro for file dddddddd but the request failed with return code xx yy. The request will
complete, but MFT will not return the file size to the caller.
●
PGTM7355E Dataset dddddddddd migrated: Record will be returned without file size
Explanation:
MFT was responding to an MFT Internet Server request for information about a file. MFT detected
that the file was migrated; MFT will not get the file size for a migrated dataset. The request will
complete, but MFT will not return the file size to the caller.
●
PGTM7358E tttttttttt CISIZE for VSAM LDS file must be 28672 or less: Transfer
terminated
Explanation:
A transfer attempted to read or write data to a VSAM LDS file. MFT supports CISize of 28672 or less
for linear datasets, but the CISize was greater than 28672. The transfer is terminated with an error.
●
PGTM7359E tttttttttt Block Allocation not allowed for LDS file: Transfer
terminated
Explanation:
A transfer attempted to create a VSAM LDS file and was using block allocation. MFT only supports
Cylinder or Track allocation when creating a VSAM LDS file. The transfer is terminated with an
error.
●
PGTM7360E tttttttttt Failed to DEFINE VSAM Cluster dddddddddd RC=xx: See OSIMSGS
output for more details
Explanation:
A transfer attempted to create VSAM LDS file dddddddddd. MFT passed the necessary parameters to
the zOS IDCAMS utility, but the IDCAMS request failed with RC xx. The MFT Started task
OSIMSGS file contains more details about the cause of the error. The transfer is terminated with an
error.
●
PGTM7361E tttttttttt Invalid MAINTAINRDW data received for DSN: ddddddddddd
Explanation:
A receive transfer was initiated and the MAINTAINRDW or MAINTAINBDW parameter was defined. MFT
detected that the incoming data was not formatted with correct BDW (Block Descriptor Word) or
RDW (Record Descriptor Word) and therefore could not be parsed and written to a file. The transfer
terminates with an error.
Make sure that the remote file is formatted correctly and that ASCII-EBDCIC conversion is NOT
defined because ASCII-EBCDIC conversion is not supported when MAINTAINBDW or MAINTAINRDW is
defined.
●
PGTM7362E tttttttttt Invalid MAINTAINBDW record received for DSN: @2
Explanation:
A Receive Transfer was initiated and the MAINTAINRDW or MAINTAINBDW parameter was
defined. MFT detected that the incoming data was not formatted with correct BDW (Block
Descriptor Word) or RDW (Record Descriptor Word) and therefore could not be parsed and written
to a file. The transfer terminates with an error. Make sure that the remote file is formatted correctly
and that ASCII-EBDCIC conversion if NOT defined, since ASCII-EBCDIC conversion is not
supported when MAINTAINBDW or MAINTAINRDW is defined.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
159
●
PGTM7369E tttttttttt Abend 413-nn Error opening Tape or DASD file ffffffffff
Explanation:
Platform Server attempted to open file ffffffff but received an abend 413. nn defines the return
code of the abend. When this error is displayed, z/OS will display message IEC145I. See the return
code in the IBM z/OS MVS System Messages Volume 7 (IEB -IEE) manual.
●
PGTM7370E CCS: Conversion Error: Retcode=xx Reason=yy: Transfer Terminated
Explanation:
The LCT (LOCALCTFILE) parameter was defined with a code conversion starting with "CC:" The
CUNLCNV program returned an error processing the code conversion request. Return code xx and
reason code yy were returned. The transfer is terminated.
See the IBM manual z/OS Unicode Services User's Guide and Reference for more information on this
error.
●
PGTM7371E CCS: Conversion Error: Record Length of converted data(lllll) > 32760:
Transfer Terminated
Explanation:
The UNICODE conversion routine was called to convert data from one format to another. The
output of the conversion had a length greater than 32760. Since 32760 is the max allowed, the
transfer request fails with an error.
●
PGTM7372E CCS: Conversion Error: Record Length of converted data(lllll) >
LRECL(lllll): Transfer Terminated
Explanation:
The UNICODE conversion routine was called to convert data from one format to another. The
output of the conversion had a length greater than the LRECL of the output file. The transfer request
fails with an error.
●
PGTM7500E CIO Routine Error xxxx
Explanation:
An internal error occurred.
Contact TIBCO Technical Support.
●
PGTS7950E ERROR CREATING OSIQUEUE DATASPACE
Explanation:
An error occurred creating the OSIQUEUE dataspace. Accompanying messages should show the
return codes received while trying to create the dataspace.
●
PGTS9210E ERROR SETTING UP XMS ENVIRONMENT
Explanation:
An error occurred trying to setup the cross memory environment. Previous errors should give more
information about the exact cause of the error.
●
PGTS9220E ERROR ISSUING LXREX MACRO
Explanation:
An error occurred executing the LXREX macro to create the cross memory environment.
Contact TIBCO Technical Support for assistance.
●
PGTS9230E ERROR ISSUING AXSET MACRO
Explanation:
An error occurred executing the AXSET macro to create the cross memory environment.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
160
Contact TIBCO Technical Support for assistance.
●
PGTS9240E ERROR ISSUING [ ETCRE | ETCON ] MACRO
Explanation:
An error occurred executing the ETCRE/ETCON macros to create the cross memory environment.
Contact TIBCO Technical Support for assistance.
●
PGTS9245E ERROR LOADING OSISX00x PROGRAM
Explanation:
An error occurred loading one of the platform cross memory programs (OSISX000 through
OSISX00F). An z/OS CSV error should also be displayed. The CSV message should indicate the
cause of the load failure.
●
PGTS9300E ERROR LOADING MODULE [ OSISANK0 | OSISDDC0 | OSISSNP0 ]
Explanation:
There was a problem loading the module specified.
Contact TIBCO Technical Support if you receive this error.
●
PGTS9314E ERROR LOADING MODULE xxxx
Explanation:
There was a problem loading the module specified.
Contact TIBCO Technical Support if you receive this error.
●
PGTS9315E Module CEEPIPI Not loaded: CEE.SCEERUN must be added to the STEPLIB:
Started Task Terminating
Explanation:
During startup, an error was received when loading module CEEPIPI. Because the module is
required for ZLIB and LZ compression, MFT is shut down.
Add library CEE.SCEERUN to the MFT started task STEPLIB. Make sure that CEE.SCEERUN is
authorized before starting the MFT started task.
●
PGTS9921E ERROR UNSUCCESSFUL ALESERV
Explanation:
An error occurred executing the ALESRV macros to create a dataspace.
Contact TIBCO Technical Support for assistance.
●
PGTS9922E ERROR UNSUCCESSFUL DSPSERV
Explanation:
An error occurred executing the DSPSRV macros to create a dataspace.
Contact TIBCO Technical Support for assistance.
●
PGTSS9923E ERROR UNSUCCESSFUL DIV
Explanation:
The Platform Server received an error executing a DIV macro which writes changed pages of a
dataspace to the VSAM linear file. Contact TIBCO Technical Support for assistance.
●
PGTN9999E Catastrophic Error in xxxx Terminating System
Explanation:
A problem occurred when attempting to shutdown the Platform Server.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
161
Contact TIBCO Technical Support if you receive this message and have your OSIMSG log file
available.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
162
Warning Messages
This section is a complete listing of all the warning messages.
●
PGTS0104W Server Not authorized to purge MSGQ qqqqqqqq: Purging all records in
Queue
Explanation:
The Platform Server was configured to use SSL. GLOBAL SSL_MESSAGE_QUEUE_NUMBER parameter
defines the message queue number qqqqqqqq that is used. At the start of the Platform Server, the
message queue is purged and then recreated.
This message indicates that the Platform Server cannot purge the message queue. Instead, the
Platform Server purges each record in the queue. This can happen because a message queue is
created by a different started task. Each started task has to use a unique message queue.
●
PGTS0833W GET for Audit xxxxx Failed: Alternate Index does not point to base
record - Record bypassed
Explanation:
The Platform Server was reading an alternate index (AIX) for the path defined by xxxxx and
received RPLTNCD error x’90’. This means that AIX was pointing to a record in the base cluster
that did not exist or indicates that the alternate index was corrupted. The Platform Server bypasses
this record and attempts to read the next record in the path.
●
PGTS0834W GET for Audit xxxxx Failed: Alternate Index should be rebuilt using
IDCAMS
Explanation:
The Platform Server read an alternate index (AIX) for the path defined by xxxxx and received
This means that AIX pointed to a record in the base cluster that did not
exist or that the alternate index was corrupted.
RPLTNCD error x’90’.
This error occurs on 10 consecutive readings so the Platform Server terminates the inquiry request.
When this message is displayed, it typically means that the alternate index has become corrupted,
and must be rebuilt using the IDCAMS utility.
●
PGTS1025W Initiator ACBNAME same as responder ACBNAME - they should be different
Explanation:
Check your GLOBAL definitions and correct the error.
●
PGTS1027W Responder GATELU not specified - please use format DEFAULT_GATELU=(INITLU,RESPLU)
Explanation:
Check your GLOBAL definitions and correct the error.
●
PGTN1350W No xxxx received in request.
Explanation:
Contact TIBCO Technical Support if you receive this message.
●
PGTN1351W No Default xxxx specified in the Global Entry
Explanation:
The default packet size or window size is not specified in the GLOBAL parameters.
●
PGTN1352W Defaulting xxxx to a system default of yyyy
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
163
Because the default parameter mentioned in this message was not coded in the GLOBAL
parameters, the system default value is applied.
●
PGTT1751W TCPTRAC ALREADY TURNED ON
Explanation:
The TCPTRON operator command was entered to start a TCP trace, but TCP tracing is already
enabled.
●
PGTT1752W TCP Trace already on for: nnnnnnnnnn
Explanation:
The TCPTRON operator command was entered to start a TCP trace for a particular node, IPv4 or IPv6
address, but tracing is already enabled for that node or IP address.
●
PGTT1763W DNS Address lookup failed for IP Address=iiiiiiiiii: No host name
returned on DNS lookup
Explanation:
A DNS request was executed for IP address iiiiiiii. The address lookup failed to find a host name.
Because the IP name was not found, the IP name was not used to identify the node definition
associated with the incoming request.
●
PGTE1911W Activity tttttttttt FUSEX06 set invalid value xxxx for parameter yyyy:
using original value
Explanation:
The user exit FUSEX06 was invoked and an attempt was made to set an invalid value xxxx for the
parameter yyyy. This is a warning message and the original value is used.
●
PGTF3111W Activity xxxx Delete Failed to: yyyy of zzzz
Explanation:
Delete failed to remote system.
See previous diagnostic messages for the possible cause.
●
PGTF3508W Error=nn on gsk_fips_state_set "ON": SSL/TLS FIPS not enabled
Explanation:
Error code nn was detected when setting the TLS/SSL "gsk_fips_state_set" on.
See the TLS/SSL error codes defined in Chapter 13: Messages and codes of the z/OS Cryptographic
Services System Secure Sockets Layer Programming manual.
●
PGTB4111W REMOTE SYSTEM IS UNAVAILABLE
Explanation:
The Platform Server on the remote side is down.
●
PGTB4124W PARM STRING PARAMETER
Explanation:
A Platform Server parameter specified in the PARM statement of the EXEC JCL card overrides a
parameter specified in the SYSIN file.
●
PGTB4125W ACTIVITY SUCCESSFULLY QUEUED AND WILL BE ELIGIBLE WHEN SERVER xxxx IS
ACTIVE
Explanation:
This is a normal message that is displayed when a transfer is queued to a server that is not currently
active.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
164
●
PGTB4189W NODE, IPADDR, IPNAME and RUSER parameters ignored for transfer type:
xxxxxxxx
Explanation:
The user performed a SCRIPT, REXX, or SUBMIT function and specified the NODE, IPADDR, IPNAME,
or RUSER parameters. This is a warning message that indicates that these parameters are not used for
a SCRIPT, RESS, or SUBMIT function. The transfer continues to execute, and these parameters are
ignored.
●
PGTB4195W SCRIPT will not be throttled: Use NODE parameter to throttle execution
Explanation:
The user was queuing a SCRIPT, SUBMIT, or REXX EXEC to the Platform Server started task. The
user did not specify the NODE parameter. When the NODE parameter is not defined, no throttling of
transfers occurs. On a heavily utilized system, this can cause transfers to fail due to lack of available
memory.
Specify the NODE parameter, particularly when submitting scripts to execute. The Platform Server
then uses the NODE CONTENTION_WINNERS parameter to throttle the number of transfers of this type
that can be executed simultaneously.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
165
Information Messages
This section is a complete listing of all the information messages.
●
PGTS0000I Another Server with the name: xxxx is active
Explanation:
Another Platform Server with the same name is already active. The second server automatically
shuts down.
●
PGTCB001I Activity Queued to Server: xxxxxxxxx with the following Transaction ID:
tttttttttt
Explanation:
This message is displayed in the batch interface when a transfer is queued to the started task.
xxxxxxxxx defines the STC name, LU name or IP address/IP name of the started task. tttttttttt defines
the transaction ID associated with the transfer.
●
PGTS000I Platform Server xxxx INITIALIZED
Explanation:
The Platform Server signified by the xxxx has started.
●
PGTS0012I OSIMSGS LOG File Freed
Explanation:
This is an informational message that is issued in response to the RELEASE,LOG Platform Server
operator command.
●
PGTS0022I CPU Information: Version Code=xxxx Id Number=yyyy Model Number=zzzz
Explanation:
WTO to issue CPU information from the Platform Server.
●
PGTS0024I Message xxxx not found
Explanation:
If you receive this message, contact TIBCO Technical Support. Supply the message number that you
receive as indicated by xxxx.
●
PGTS0026I Platform Server Suite xxxx initialized
Explanation:
The Platform Server started task is starting.
●
PGTS0029I Platform Advanced SNA services being [loaded | stopped]
Explanation:
This informational message is issued at startup and shutdown.
●
PGTS0031I Platform Advanced TCP services xxxx
Explanation:
This message states if the TCP services is loaded or not and the reason.
●
PGTS0032I [ FUSIONSNA | FUSIONTCP ] request by xxxx Denied - Application NOT
authorized by GLOBAL key
Explanation:
This application must be authorized by applying the correct licensing key for the product in the
GLOBAL member.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
166
●
PGTS0033I xxxx Locally initiated request Terminated - yyyy NOT authorized by
GLOBAL key
Explanation:
This application must be authorized by applying the correct licensing key to the GLOBAL member.
●
PGTS0034I xxxxxxxx request by yyyyyyyy Denied - Temporary key has expired
Explanation:
A Platform Server request was initiated by node yyyyyyyy. The request type 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.
●
PGTS0037I Another Server with the name xxxx is active
Explanation:
You attempted to bring up two Platform Server started tasks, each with the same name. This is not
supported, and so the second server shuts itself down immediately.
●
PGTS0038I Platform Server xxxx Shutting Down
Explanation:
The Platform Server started task is in the process of termination. This is a normal message.
●
PGTS0039I RDJFCB failed - Audit DSN not found
Explanation:
The audit 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.
●
PGTS0040I Platform Server xxxxxxxxxxxx processing stopped: Retry later
Explanation:
An initiator or responder request xxxxxxxx was detected by the Platform Server, but processing was
quiesced by the INITIATORSTOP or RESPONDERSTOP commands.
This message is meant to notify the user why a file transfer request is not processed.
●
PGTS0042I Platform Server request from node nnnnnnnn exceeded contention loser
max of xx: Try request later
Explanation:
A request was received from node nnnnnnnn. The Platform Server detected that the number of
responder tasks associated with this node exceeded the LOSERS parameter defined in the node
definition.
The Platform Server sends this message back to the system that initiated the request. The request is
terminated, but it can be retried at a later time.
●
PGTS0047I Error opening TCPTRAC - tracing terminated
Explanation:
The Platform Server encountered an error trying to open the file specified in the TCPTRAC DD
statement specified in the startup PROC.
Check the contents of the DD statement to verify that they are specified correctly.
●
PGTS0048I TCPTRAC DD statement opened successfully
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
167
The tracing for TCP/IP is started successfully.
●
PGTS0049I TCPTRAC DD statement closed successfully
Explanation:
The tracing for TCP/IP is stopped successfully.
●
PGTS0050I Work Queue Entry for Activity xxxx purged.
Explanation:
The work queue contains a transaction request that was purged. This is a normal message.
●
PGTS0051I Invalid slot number for PURGEQ - xxxx
Explanation:
Contact TIBCO Technical Support if you receive this message.
●
PGTS0052I PURGEQ option xxxx not supported
Explanation:
Contact TIBCO Technical Support if you receive this message.
●
PGTS0053I Work Queue Entry address for PURGEQ is Invalid -xxxx
Explanation:
Contact TIBCO Technical Support if you receive this message.
●
PGTS0054I Activity xxxx for yyyy queued successfully zzzzzzzz
Explanation:
Activity for transaction xxxx for IP address or node yyyy was successfully queued to the started task.
Parameter zzzzzzzz gives additional information about the source of the request.
For example, on a request queued as a result of the EVERY command, by
displayed.
●
EVERY request
is
PGTS0055I Queue Entry for Activity xxxx Already in Purge KILL State - waiting for
TASK termination
Explanation:
Someone attempted to purge activity xxxx that was already marked for purge from the work queue.
No further action is necessary.
●
PGTS0062I Resetting any nodes with errors
Explanation:
The RESETINTERVAL parameter was reached, and any nodes that were in error are now reset for
transfers to be retried. This is an informational message. No action is required.
●
PGTS0063I STARTTCP command issued - TCP Already started: You must use TERMTCP
command before restarting TCP interface
Explanation:
The STARTTCP operator command was issued, but the TCP interface was not stopped. No action
takes place on the TCP interface.
If you want to refresh the TCP interface, you have to issue the TERMTCP command before issuing the
STARTTCP command.
●
PGTS0064I GLOBALREFRESH command completed {Successfully | with errors
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
168
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.
●
PGTS0067I Detail for xxx node nnnnnnnn
Explanation:
The NODE operator command is issued, and the node name to be displayed is specified as nnnnnnnn.
xxxx indicates if the display is for an SNA or TCP. This message is followed with detailed
information about the node.
●
PGTS0068I iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
Explanation:
The NODE operator command was issued. This message is used to display detailed information
about the node that was displayed.
●
PGTS0069I Error in DISABLE command syntax xxxx
Explanation:
An operator entered a modify DISABLE command that did not conform to the proper syntax. The
correct syntax is F servername,DISABLE,nnnnnn, where nnnnnn is the member name in the CONFIG
library.
●
PGTS0070I Error in ENABLE command syntax xxxx
Explanation:
An operator entered a modify ENABLE command that did not conform to the proper syntax. The
correct syntax is F servername,DISABLE,nnnnnn, where nnnnnn is the member name in the CONFIG
library.
●
PGTS0071I Node xxxx enabled successfully
Explanation:
A dynamic enable command entered by the console modify command is successfully processed.
●
PGTS0072I Enable for node xxxx failed. Node already active
Explanation:
This message is informational only. No action is necessary.
●
PGTS0073I Node xxxx not defined in Nodes PDS
Explanation:
There was no member xxxx in the CONFIG library.
Verify that the node is properly defined and that you spelled the member name correctly.
●
PGTS0075I Nodes entry for Remote system xxxx was not found
Explanation:
ContactTIBCO Technical Support if you receive this message.
●
PGTS0076I Nodes entry for Remote system xxxx was found
Explanation:
This message is informational only.
●
PGTS0077I Select code xxxx invalid for NODEOP
Explanation:
Contact TIBCO Technical Support if you receive this message.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
169
●
PGTS0085I AUTHKEY file does not contain valid Authentication key: Recreating the
key
Explanation:
The Platform Server read the data in the AUTHKEY DD statement and determined that it was not a
valid authentication key. The Platform Server creates a new authentication key and 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
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.
●
PGTS0090I Node nnnnnnnn has been reset successfully
Explanation:
Node nnnnnnnn was reset by the RESET command. Additionally, any transfer request for this node
was reset as well.
●
PGTS0091I Node nnnnnnnn not enabled: License Key Max Nodes of xxx exceeded
Explanation:
The user attempted to enable node nnnnnnnn either at startup or through the ENABLE operator
command but enabling this node exceeds the defined maximum number of nodes. Some companies
purchase the Platform Server with a license key that defines the maximum number of node entries
that can be enabled.
If you wish to enable more nodes, contact TIBCO Technical Support.
●
PGTS0092I Queue Lookaside Initialization Found Knetwork Fusion Responder Activity
xxxx. Entry is purged.
Explanation:
A responder entry, xxxx, was found for a Knetwork protocol transfer. These entries are not required
and are therefore purged to save space.
●
PGTS0093I Queue Lookaside Dataspace Being Built
Explanation:
This message is normal and is displayed when the Platform Server is being initialized. It means that
the work queue index is built. The index is used to hasten queue searches and reduce paging.
●
PGTS0094I Queue Lookaside Initialization Found Activity xxxx active. Entry is
Reset to Inactive.
Explanation:
A transfer was in progress when the Platform Server was last shut down. At startup time the
transfer status was reset to inactive so that it can be retried.
●
PGTS0095I Queue Lookaside Initialization Found Activity xxxx Marked for purge.
Entry is purged.
Explanation:
When the server was last shut down, it was in the process of purging a transaction from the work
queue. At startup time, the initiation code found an entry that is still on the queue but marked to be
removed. The initialization code completes the purge.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
170
●
PGTS0096I Queue Lookaside Initialization Found Activity xxxx Has Invalid Status
Explanation:
The Platform Server startup routines found an integrity error on the work queue and corrected it.
●
PGTS0097I Queue Lookaside Initialization Maximum Slot number is xxxx
Explanation:
This message is informational only. The message is normal at startup time.
●
PGTS0098I Nodes Lookaside Dataspace Being Built
Explanation:
The Platform Server initialization routines are building the index for the nodes topology dataspace.
This is a normal message at startup time.
●
PGTS0099I Queue Lookaside Initialization Found Activity xxxx Logically purged.
Audit record written.
Explanation:
This is an 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.
●
PGTS0100I Product xxxxxxxx will expire in nn days: Contact TIBCO Technical
Support for a new Product License key
Explanation:
The product xxxxxxxx license key expires in nn days. This message is displayed once per day until
the product license expires.
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
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.
●
PGTS0102I Product xxxxxxxx expires today: Contact TIBCO Technical Support for a
new Product License Key
Explanation:
The product xxxxxxxx license key expires today. Product xxxxxxxx will continue to run until the
started task is brought down. If the product is started with an expired license key, the software will
not run.
Contact TIBCO Technical Support to receive a new product license key.
●
PGTS0103I Queue Lookaside Initialization Found Activity tttttttttt SAPI Request
Purged: Audit record written
Explanation:
The Platform Server 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.
●
PGTS0106I Starting TLS Task using IPPORT nnnnn
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
171
The Platform Server is configured to use TLS/SSL. This message shows the IPPORT that the
Platform Server listens on for incoming TLS/SSL requests.
●
PGTS0107I Purge SAPI Transaction tttttttttt for Node nnnnnnnn: Node entry not
found - Transaction purged
Explanation:
The Platform Server has completed a SAPI request and is attempting to find the node definition to
notify it that the SAPI request is completed. The Platform Server is unable to find the node
definition associated with the request.
The transfer request continues, but the node definition is not found. This message is displayed for
informational purposes only.
●
PGTS0108I Purge SAPI Transaction tttttttttt for Node nnnnnnnn: SAPI Request not
pending - Transaction purged
Explanation:
The Platform Server has completed a SAPI request and is attempting to find the node definition to
notify it that the SAPI request is completed. The Platform Server finds the node definition associated
with the request, but the node definition does not indicate that a SAPI request is pending.
The transfer request continues, but the node definition is not posted. This message is displayed for
informational purposes only.
●
PGTS0109I Starting Platform Server SAPI Interface
Explanation:
This message indicates that the Platform Server SAPI interface is starting as a result of the GLOBAL
parameter being set to YES.
SAPI_INTERFACE
●
PGTS0110I Platform Server SAPI Interface Terminating
Explanation:
This message indicates that the Platform Server SAPI interface is terminating. Termination is done
only when the Platform Server is terminated.
●
PGTS0112I Platform Server COLD start: All requests on the WORKQ will be purged
Explanation:
The START=COLD option is entered on the Platform Server started task EXEC PARM JCL statement.
This is an informational message that tells the user that all requests on the WORKQ are deleted
because of the cold start request.
●
PGTS0113I Platform Server COLD start: Activity tttttttttt purged from the Work
Queue
Explanation:
The START=COLD option is entered on the Platform Server started task EXEC PARM JCL statement.
This is an informational message that tells the user that transaction tttttttttt has been purged form
the WORKQ because of the cold start request.
●
PGTS0114I COS Display Summary: nn entries displayed
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.
●
PGTS0116I COS Name=cccccccc SBUFSIZE=ssss RBUFSIZE=rrrr
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
172
This message shows the summary information for COS entry cccccccc. It shows the SBUFSIZE and
values entered for the COS entry.
RBUFSIZE
●
PGTS0117I aa bb cc dd ee ff gg hh
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.
●
PGTS0119I ttttt member nnnnnnnn: not enabled due to AUTOENABLE=NO
Explanation:
The CONFIG DD in the startup JCL points to member nnnnnnnn in the node configuration library.
But member nnnnnnnn is not activated because it is defined with AUTOENABLE=NO.
This message is for information purposes only. ttttt defines the type of member that is not enabled.
●
PGTS0122I Hardware Encryption support: mmmmmmmmmmmmmm
Explanation:
This message is displayed at startup 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.
●
PGTS0123I Queue Lookaside Initialization Found Activity with invalid TransId:
Record purged and audit not written
Explanation:
During the Platform Server started task initialization, it detects a request in its WORKQ that does
not have a valid initiator or responder transaction ID. The request is removed from the WORKQ.
Because the request is not formatted properly, a record is not written to the audit log.
●
PGTS0125I TLS Interface Terminating
Explanation:
This is an information message that is displayed when the TLS Interface is terminating.
●
PGTS0126I TLS Initialize Successful: Accepting TLS/SSL Requests
Explanation:
This is an information message that is displayed when the TLS interface initialization completes
successfully and accepts TLS connections.
●
PGTS0127I ZLIB/TLS Start Failed: Service already started
Explanation:
This is an information message that is displayed when the ZLIB/TLS environment is starting, but the
Platform Server code detected that the interface has already started.
●
PGTS0129I TLS Interface Shutdown complete
Explanation:
This is an information message that is displayed when the TLS Interface has terminated successfully.
●
PGTS0131I ZLIB/TLS Shutdown Failed: Environment not started
Explanation:
Platform Server attempted to stop the ZLIB/TLS environment, but the shutdown failed because the
ZLIB/SSL environment was already stopped.
●
PGTS0132I ZLIB Compression/TLS Interface started successfully
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
173
This is an information message that is displayed when the ZLIB/TLS environment has started
successfully.
●
PGTS0133I ZLIB Compression/TLS interface starting
Explanation:
This is an information message that is displayed when the ZLIB/TLS environment is initializing.
●
PGTS0147I Queue is Full, Transfer Request Denied
Explanation:
The work queue is full and cannot accept any more requests. The server must be stopped. The work
queue VSAM file must be backed up, deleted, and redefined with more space.
●
PGTS0148I Activity xxxx Expired and will be deleted from work queue
Explanation:
This message indicates that a work queue item has an expiration date that is earlier then the current
date. Therefore the Platform Server dispatcher purges it from the work queue.
●
PGTS0149I Platform Server Initiator Dispatcher Active
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.
●
PGTS0150I Beginning Scan of Work Queue for Initiator Activities
Explanation:
The Platform Server dispatcher is beginning to look at the work queue entries for work to initialize.
●
PGTS0151I Max Retries Exceeded - Deleting Activity xxxx from work queue
Explanation:
An activity has been queued with a non-zero limit specified for the number of retries. This limit is
reached so the dispatcher purges the activity from the work queue rather than dispatch it.
●
PGTS0152I Initiator Now Waiting after scan of Work Queue
Explanation:
The Platform Server dispatcher completes its scan of the work queue and becomes dormant until the
new cycle time expires or until new entries are queued.
●
PGTS0153I Wake up and scan initiator Work Queue again
Explanation:
The new cycle timer has popped, and the dispatcher resumes looking for work items to dispatch.
●
PGTS0155I Platform Server Initiator Dispatcher shutting down normally
Explanation:
This message indicates that the Platform Server is being shut down. This is a normal message.
●
PGTS0173I PURGE command successful for Activity xxxx
Explanation:
The purge command is successfully executed to remove an activity from the work queue.
●
PGTS0174I DELETE command successful for Activity xxxx
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
174
The delete command is successfully executed to remove an activity from the work queue.
●
PGTS0175I HOLD command successful for Activity xxxx
Explanation:
The console hold command places an activity to hold status on the work queue.
●
PGTS0176I RELEASE command successful for Activity xxxx
Explanation:
The console release command moves an activity on hold to release status on the work queue.
●
PGTS0177I SUSPEND command successful for Activity xxxx
Explanation:
The console suspend command puts an activity to suspend status on the work queue.
●
PGTS0178I Activity tttttttttt purged: Platform Server EVERY request has exceeded
parameter EVERY_COUNT=ccccc
Explanation:
A Platform Server request was queued that used the EVERY parameter and the EVERY_COUNT
parameter to limit the number of requests that could be scheduled. This message indicates that the
EVERY_COUNT limit is reached. The EVERY request is purged from the queue.
●
PGTS0181I Activity xxxx has completed
Explanation:
The Platform Server finished processing an activity from the work queue.
●
PGTS0187I SECAUDIT command successful
Explanation:
The SECAUDIT modify command was issued and processed successfully.
●
PGTS0189I SECADMIN command successful
Explanation:
The SECADMIN modify command was issued and processed successfully.
●
PGTS0191I SECLOGV command successful
Explanation:
The SECLOGV modify command was issued and processed successfully.
●
PGTS0192I Responder Activity xxxx purged from Queue
Explanation:
The indicated transaction is deleted from the queue. This is a normal message.
●
PGTS0193I Responder Activity xxxx remains in Queue awaiting Checkpoint restart
Explanation:
This transaction which was set up using checkpoint restart was interrupted. It starts again from the
last checkpoint and puts back on the queue awaiting restart.
●
PGTS0199I Activity tttttttttt Transfer Nodeclass (nn) exceeds NODE WINNERS (ww):
Request set to error
Explanation:
The NODECLASS parameter entered exceeds the NODE WINNERS parameter. The transfer can never
run successfully. The transfer request is set to an error state.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
175
Either change the transfer NODECLASS to a number less than or equal to the NODE WINNERS
parameter, or increase the WINNERS parameter to be as large as the transfer NODECLASS.
●
PGTS0205I Platform Server xxxxxxxxxx processing has been stopped
Explanation:
xxxxxxxxxx represents either an INITIATORSTOP or RESPONDERSTOP command that the Platform
Server received. This message indicates that processing is stopped.
●
PGTS0206I Platform Server xxxxxxxxxx processing has been started
Explanation:
xxxxxxxxxx represents either an INITIATORSTOP or RESPONDERSTOP command that the Platform
Server received. This message indicates that processing is started.
●
PGTF0207I MQ Load Error on module xxxxxxxx: MQ SCSQLOAD/SCSQAUTH must be in
STEPLIB - MQ processing disabled
Explanation:
The Platform Server is attempting to load MQ module xxxxxxxx, but it received a load error. This is
typically because the MQ SCSQLOAD and SCSQAUTH libraries are not in the Platform Server STEPLIB.
This is an 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.
●
PGTF0208I Load Error on module mmmmmmmm: SYS1.CSSLIB must be in STEPLIB when
using UNICODE services: Services disabled
Explanation:
Platform Server attempted to load code conversion module mmmmmmmm but the load failed. Any
UNICODE code conversion performed by specifying a local conversion table starting with "CC:"
fails.
Make sure that SYS1.CSSLIB is in the STC
●
STEPLIB
or in the MVS
LNKLST
module.
PGTF0212I tttttttttt Transfer set to Inactive state due to COS cccccccc
priority=yy
Explanation:
The Platform Server is scanning WORKQ to find transfers to run and finds transfer tttttttttt ready to
run. However, when checking its COS entry cccccccc, the Platform Server dispatcher finds that the
priority for this transfer is 0 or 1. In this case, the Platform Server cannot start the transfer. The
transfer is put in an inactive error state so that the transfer is not checked again until the errors are
reset.
●
PGTF0213I tttttttttt Transfer held due to NODE nnnnnnnn INITHOLD=YES: Use the
INITREL command to release the HOLD
Explanation:
A transfer is ready to be initiated for node nnnnnnnn. However the node has been placed in an
status, so no transfers can be initiated to this node.
INITHOLD
You can issue the INITREL operator command or the ISPF panels to release the hold and make
transfers can be initiated to this node.
This message is displayed approximately every minute as a reminder that the node is in hold state.
●
PGTF0214I INITHOLD complete for Node nnnnnnnn: Initiator requests will be
stopped: uuuuuuuu
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
176
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.
●
PGTF0215I INITREL complete for Node nnnnnnnn: Initiator requests will start and
the error count has been reset: uuuuuuuu
Explanation:
An INITREL request was received for node nnnnnnnn. uuuuuuuu defines whether this request is
initiated through an operator command or through the ISPF panels. INITHOLD is cleared and
transfers can be initiated to this node.
●
PGTF0216I RESPHOLD complete for Node nnnnnnnn: Responder requests will be
rejected: nnnnnnnn
Explanation:
A RESPHOLD request was received for node nnnnnnnn. uuuuuuuu defines whether this request is
initiated through an operator command or through the ISPF panels. No transfers are responded
from this node. Responder requests from this node 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.
●
PGTF0217I RESPREL complete for Node nnnnnnnn: Responder requests will be
accepted: uuuuuuuu
Explanation:
A RESPREL has been received for node nnnnnnnn. uuuuuuuu defines whether this request is
initiated through an operator command, or through the ISPF panels. RESPHOLD is cleared and
transfers can be accepted from this node.
●
PGTF0218I TLSSTOP Completed
Explanation:
The operator executed the TLSSTOP command to stop the TLS services. The TLS service is stopped
successfully.
●
PGTF0223I MODVER: Module: mmmmmmmm Date: MM/DD/YY Time: HH:MM Level: LLLLLLL
Explanation:
The user entered the MODVER operator command for module mmmmmmmm. This message shows the
date and time when the module was compiled along with the hotfix level.
●
PGTF0228I ZEDCSTAT: ZEDC Interface is mmmmmmmm: TLS Interface is nnnnnnnn
Explanation:
The operator entered the ZEDCSTAT command. This message shows the status of the ZEDC interface
and the TLS interface. Status is either Active or Inactive.
●
PGTS0234I Message data set closed
Explanation:
This is a normal message that is displayed during shut down of the started task.
●
PGTS0235I Audit data set closed
Explanation:
This is a normal message that is displayed during shut down of the started task.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
177
●
PGTS0252I User Profile for local user: uuuuuuuu node: nnnnnnnn changed to remote
user: rrrrrrrr
Explanation:
User uuuuuuuu queues a transfer and specifies that user profiles must be used. The Platform Server
started task substitutes user ID rrrrrrrr for the request to node nnnnnnnn. This message is displayed
for information reason only.
●
PGTS0258I Local user uuuuuuuu tttttttt PROFILE for node: nnnnnnnn remote user:
rrrrrrrr successful
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.
●
PGTS0259E Local user uuuuuuuu ADD PROFILE for node: nnnnnnnn failed - no slots
left on dataspace
Explanation:
The FUSPROF utility attempts to add a user profile to the profile dataspace, but no space is left on the
user profile dataspace.
Use the PROFILEQ parameter of the started task PARM statement to add more slots on the
dataspace.
●
PGTS0260I Local user uuuuuuuu DELETE PROFILE for node: nnnnnnnn successful
Explanation:
The FUSPROF utility successfully deleted the user/node combination from the profile dataspace.
uuuuuuuu defines the user ID while nnnnnnnn defines the node name.
●
PGTS0262I User Profile for Remote user: rrrrrrrr xxxxxx: iiiiiiiiii changed to
local user: llllllll
Explanation:
A remote user profile was detected for remote user rrrrrrrr. xxxxxx: iiiiiiii shows the node
information. The user is changed to user ID llllllll. The file transfer request runs under the
authorization of local user ID llllllll. This message is for information purposes only to show that a
remote user profile is used.
●
PGTS0263I Remote user rrrrrrrr DELETE PROFILE for node: nnnnnnnn successful
Explanation:
The FUSPROF utility successfully deleted a profile for remote user rrrrrrrr and node nnnnnnnn. This
message is displayed only when RESPONDER=YES is entered on the FUSPROF DELETE parameter
statements.
●
PGTS0269I Activity tttttttttt has been purged by user exit FUSEX06
Explanation:
User exit FUSEX06 is invoked and has purged the activity tttttttt. Return code of 8 upon return from
the exit indicates that the activity is to be purged.
●
PGTS0802I SMF Record Type xxxx written for Activity yyyy
Explanation:
This message simply informs you that an SMF record is written for the indicated activity.
●
PGTS0818I AUDIT file is now 80 percent full
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
178
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.
●
PGTS0819I AUDIT file exceeds max slots of xxxx - wrapping to the start of the
AUDIT file
Explanation:
The audit data set is already filled and audit records are now being written to the start of the data
set.
●
PGTS0820I Performing LOGSNAP to DD SNAPLOG
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.
●
PGTS0821I LOGSNAP Dump Complete
Explanation:
A snap dump has been taken and is now complete.
●
PGTS0823I LOGSNAP Log address range: xxxx Vector address range: yyyy Log
STOKEN=zzzz
Explanation:
This is an informational message used for debugging purposes.
●
PGTS0825I Audit File full - Wrapping to record 1
Explanation:
The audit file is full and wraps around to record 1 to start overwriting the file.
●
PGTS0826I Audit File full - Unable to wrap to record 1 - no additional records
will be written
Explanation:
The audit file is full and unable to wrap around to overwrite the file. Auditing is stopped.
●
PGTS0930I NodeName | LUName/IPAddr/IPName | Mode/Port | ParSess | Winners/Losers
| State
Explanation:
The node operator command was entered to display summary information about enabled node
definitions. This is a heading message and is accompanied by message PGTS0931I to display the
summary information about each enabled node.
●
PGTS0931I nnnnnnnn | iiiiiiii | mmmmmmmm | ppp | www/lll | sss
Explanation:
The node operator command was entered to display summary information about enabled node
definitions. This message is displayed for each node that is enabled and shows the summary
information about the node.
Where:
nnnnnnnn defines the node name.
iiiiiiii defines the LU name, IP name or IP address.
mmmmmmmm defines the SNA mode or IP port.
ppp, www and lll define parallel sessions parameters.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
179
sss defines current state of the node.
●
PGTS0978I Platform Server dispatcher shutting down
Explanation:
This is a normal message that appears during shut down of the started task.
●
PGTS0979I Active transmissions detected during dispatcher shutdown
Explanation:
This message is displayed when some transfers are currently active during shutdown of the started
task.
●
PGTS0980I Max Retries of xxxx Exceeded - Activity yyyy to be Deleted
Explanation:
This message indicates that an initiator transfer request was terminated because the max try count
of xxxx was exceeded. The transfer is terminated with an error and a failure audit record is written.
●
PGTS0982I Initiator Dispatcher Starting to Scan the Work Queue
Explanation:
The Platform Server is initialized and is scanning the work queue to check if there are any activities
to process. Transactions set to active are released.
●
PGTS0983I Console Display Command to Server xxxx is yyyy (zzzz)
Explanation:
This message is displayed after the modify display command is issued correctly.
●
PGTS0984I Console Display Command Processor Completed Successfully
Explanation:
This message is displayed upon successful completion of the modify command.
●
PGTS0986I There are xxxx Activities in the Work Queue for Server yyyy
Explanation:
This message is displayed when the modify display command is issued. xxxx is the number (in hex)
of activities in the work queue for the Platform Server specified.
●
PGTS0987I Process==Activity==Status==Node==UserId==Start Date==Start Time
Explanation:
This is a header message with column titles. It is issued along with message PGTS0986I and
PGTS0988I.
●
PGTS0988I xxxx yyyy zzzz aaaa bbbb
Explanation:
This message is issued along with message PGTS0986I and PGTS0987I. It displays the specific
information about each entry in the work queue.
●
PGTS0989I Console Node Query to Server xxxx is yyyy (zzzz)
Explanation:
This message is received when a modify query is done on a node.
●
PGTS0990I Console Node Query Processor Completed Successfully
Explanation:
This message is received when a modify query is done on a node and is completed successfully.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
180
●
PGTS0995I Ambiguous command received, please re-enter
Explanation:
This command is not acceptable to the remote system. Check with the support staff of that computer
to determine a valid command to use.
●
PGTS0996I Stop command being processed
Explanation:
This is a normal message that is displayed during the shutdown of the started task.
●
PGTS0997I Platform Server Suite dataspace initialization complete
Explanation:
This is a normal message that is displayed during the startup of the started task.
●
PGTS0998I Platform Server Suite Cross Memory Services environment setup
successfully completed
Explanation:
This is a normal message that is displayed during the startup the started task.
●
PGTS0999I Platform Server Suite deleting dataspaces
Explanation:
This is a normal message that is displayed during the shutdown of the started task.
●
PGT1002I TLV VARIABLE XXXX NOT FOUND IN TLV TABLE
Explanation:
Platform Server was validating incoming control information and found an unexpected parameter.
This could be caused by a partner Platform Server running a different release.
If this affects the execution of a Platform Server transfer, contact TIBCO Technical Support.
●
PGTS1047I xxxx key validated - expiration date is YYYYDDD
Explanation:
This is a normal message. It is displayed at startup.
●
PGTB1099I INVALID/MISSING SERVER PARM DEFAULT USED
Explanation:
Check your GLOBAL definitions and correct the error.
●
PGTA1101I Transmission subtask terminating due to shutdown
Explanation:
If the shutdown command is entered when a transmission is in progress, this message is displayed.
●
PGTS1132I xxxx member activated successfully
Explanation:
This is an informational message that is displayed when a node definition is enabled successfully.
●
PGTS1148I xxxx disabled successfully
Explanation:
The modify command disables the member specified successfully.
●
PGTS1161I LIST xxxx ACTIVATES SUCCESSFULLY WITH yyyy ENTRIES
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
181
List xxxx is activated successfully. yyyy indicates how many NODE, IPADDR, or IPNAME
definitions are associated with the list.
●
PGTA1200I Purging Queue Entry xxxx
Explanation:
The queue entry xxxx is marked for termination.
●
PGTA1201I Activity xxxx not processed
Explanation:
The activity xxxx cannot be processed at this time. It is marked inactive and placed back on the work
queue.
●
PGTA1202I Transmission Subtask Processing Initiator for Transaction xxxx - Remote
System yyyy
Explanation:
The dispatcher has successfully attached an MVS subtask to initiate the xxxx activity. This is a
normal message that is displayed when a file transfer is dispatched.
●
PGTS1203I Invalid xxxx:yyyy for Activity: zzzz Purging Queue Entry
Explanation:
Contact TIBCO Technical Support if you receive this message.
●
PGTA1209I tttttttttt Writing Audit record for Temporary error
Explanation:
A file transfer completed with a recoverable error and is retried at a later time. The GLOBAL
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.
AUDIT_TEMP_ERRORS
●
PGTA1215I xxxx
Explanation:
Contact TIBCO Technical Support if you receive this message.
●
PGTA1216I Maximum number of concurrent Activities reached - No blocks available
Explanation:
The Platform Server has reached the maximum number of concurrent transactions. Some
transactions cannot start until others end.
●
PGTA1217I VTAM Control blocks not deleted - address not found
Explanation:
An error occurs when trying to delete the VTAM control block.
●
PGTA1218I xxxx yyyy zzzz - Activity will placed on HOLD
Explanation:
Transaction xxxx is placed on hold because action yyyy is in zzzz status.
●
PGTS1300I Requested Access function xxxx not supported
Explanation:
Contact TIBCO Technical Support if you receive this message.
●
PGTS1376I REQUIRE_NODE_DEFINITON set to YES,YES due to License Key Max Node=yyyy
Explanation:
The Platform Server automatically set the GLOBAL REQUIRE_NODE_DEFINITION parameter to YES
because the license key indicated a limited version of the Platform Server, thus limiting the number
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
182
of NODE definitions. In this case, the Platform Server requires that NODE definitions are defined
for both initiator and responder requests.
Correct this parameter and restart the Platform Server started task.
●
PGTS1377I DEFAULT_COSNAME must be 1 to 8 characters
Explanation:
The value entered for the DEFAULT_COSNAME parameter in the GLOBAL member was incorrect. The
valid values must be between 1 and 8 characters.
Correct this parameter and restart the Platform Server started task.
●
PGTS1378I PDS_SPACE_RELEASE must be YES or NO
Explanation:
The value entered for the PDS_SPACE_RELEASE parameter in the GLOBAL member was incorrect.
The valid values are YES and NO.
Correct this parameter and restart the Platform Server started task.
●
PGTS1379I DEFAULT_RECEIVE_DISP must be CREATE, CREATE_REPLACE, CREATE_APPEND,
REPLACE, or APPEND
Explanation:
The value entered for the DEFAULT_RECEIVE_DISP parameter in the GLOBAL members was
incorrect. The valid values are CREATE, CREATE_REPLACE, CREATE_APPEND, REPLACE, and APPEND.
Correct this parameter and restart the Platform Server started task.
●
PGTS1380I EXTENDED_SECURITY_RESOURCE must be from 1 to 8 characters
Explanation:
The value entered for the EXTENDED_SECURITY_RESOURCE parameter in the GLOBAL member is
incorrect. The valid values must be between 1 and 8 characters long. Correct this parameter and
restart the Platform Server started task.
●
PGTS1381I EXTENDED_SECURITY_CHECK must be ENFORCE/WARN/NO,ENFORCE/WARN/NO
Explanation:
The value entered for the EXTENDED_SECURITY_RESOURCE parameter in the GLOBAL member was
incorrect. This parameter has two sub-parameters. The first sub-parameter defines whether to check
if the user is authorized to use the Platform Server, while the second parameter determines if the
user is authorized to access the node definition or IP address. The valid values for each subparameter are ENFORCE, WARN, or NO.
Correct this parameter and restart the Platform Server started task.
●
PGTS1394I MFT Platform Server for zOS running in FIPS140 mode
Explanation:
The GLOBAL_ENFORCE_SECURITY_POLICY parameter was set to FIPS140 or TLSFIPS. This message
indicates that the necessary crytographic hardware is installed and FIPS mode is enabled. This
message is for information purposes only.
●
PGTS1406I XXXXXXXX Marked as Pending Disable: Disable will complete when SAPI
request terminates
Explanation:
The Platform Server does not disable the node when a SAPI request is pending. When the SAPI
request is completed, either successfully or unsuccessfully, the node is disabled.
●
PGTS1530I SSL_MESSAGE_QUEUE_NUMBER is no longer used - Ignored
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
183
The GLOBAL parameter SSL_MESSAGE_QUEUE_NUMBER is no longer used. This is an
information message indicating that the parameter is ignored.
●
PGTT1601I LOGON exit entered for LU xxxx Mode yyyy
Explanation:
This message is an informational message. It is issued at the start of a LU 6.2 transaction.
●
PGTT1602I TPEND exit entered
Explanation:
This is an informational message.
●
PGTT1603I Bind Received for Independent LU=xxxx MODE=yyyy
Explanation:
This message is issued when the Platform Server receives a bind from the LU specified in the
message.
●
PGTT1604I ATTN exit entered TYPE=xxxx LU=yyyy MODE=zzzz
Explanation:
The Platform Server VTAM attention exit is driven for attention type xxxx for logical unit yyyy using
mode name zzzz.
●
PGTT1605I ATTN exit entered for unknown type=xxxx
Explanation:
The Platform Server VTAM attention exit is driven for an unknown attention type xxxx.
●
PGTT1609I xxxx ACB opened successfully - executing on VxRyMz
Explanation:
This is an 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.
●
PGTT1612I ACB xxxx closed successfully
Explanation:
This is an informational message that indicates that the ACB was closed successfully.
●
PGTT1624I Non-LU6.2 CINIT Received for LU:xxxx MODE:yyyy - Changing Bind to LU
6.2 - zzzz
Explanation:
A CINIT is received from VTAM that is a non-LU 6.2 CINIT. The Platform Server changes the bind
to specify LU 6.2.
●
PGTT1625I Non LU 6.2 BIND Received for LU:xxxx MODE:yyyy - Terminating Session
Request
Explanation:
A non-LU 6.2 bind is received. The Platform Server is terminating the session.
●
PGTT1632I ACB xxxx Open failed ACBERFLG=yyyy Continuing without VTAM due to
Operator request
Explanation:
There is a failure opening the ACB for this started task.
Make sure the ACB listed here is varied active.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
184
●
PGTT1633I ACB xxxx Open failed ACBERFLG=yyyy Ending started task due to Operator
request
Explanation:
There is a failure opening the ACB for this started task.
Make sure the ACB listed here is varied active.
●
PGTT1634I Bind Image Sent: iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
Explanation:
The VTAM LOGON exit is invoked. After scanning the CINIT request, it is detected that the bind
image in the CINIT is not an LU6.2 bind. This message indicates that the bind image is overridden
and displays the bind image that is sent to the session partner. This message is displayed along with
message PGTT1624I.
●
PGTT1663I CNOS Winner/Loser/Total sessions defined as xx/xx/xx - negotiated to
yy/yy/yy for LU xxxx yyyy'
Explanation:
During the session negotiation, the number of contention winners, contention losers, and the total
sessions defined in the remote node definition (indicated by xx/xx/xx) are negotiated to yy/yy/yy
with the partner LU xxxx and mode name yyyy.
●
PGTT1664I tttttttttt SNA COSNAME=cccccccc SendBuffSize=xxxx RecvBuffSize=yyyyy
Explanation:
This message is displayed at the start of the Platform Server file transfer when SNA 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.
●
PGTT1665I tttttttttt Send RUSize=xxxxx Receive RUSize=yyyyy mmmmmmmm
Explanation:
This message is displayed at the start of the Platform Server file transfer when SNA 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.
●
PGTV1697I xxxx
Explanation:
Debug message for internal use.
●
PGTV1700I Error in FUSVTAM - Transfer Terminating
Explanation:
The program FUSVTAM has encountered a problem which causes the transaction to terminate.
●
PGTV1701I Contents of FUS_RC_Return Code: xxxx
Explanation:
This message is used for debugging purposes.
●
PGTV1702I Contents of FVCOMM_Return_Code: xxxx
Explanation:
This message is used for debugging purposes.
●
PGTV1703I Contents of FUS_RC_Status: xxxx
Explanation:
This message is used for debugging purposes.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
185
●
PGTV1704I Contents of FUS_RC_VTAM: xxxx
Explanation:
This message is used for debugging purposes.
●
PGTV1705I Contents of FUS-RC_Storage: xxxx
Explanation:
This message is used for debugging purposes.
●
PGTV1712I TCP INITAPI successful for TCP STC xxxx - ASID yyyy
Explanation:
This is an informational message that can also be used for debugging purposes.
●
PGTT1717I TCP Responder Terminated for TCP Job xxxx in ASID yyyy
Explanation:
This is a normal termination message.
●
PGTT1719I TCP ASID xxxx now Listening on Port yyyy to TCP job zzzz
Explanation:
This is a normal message that is displayed when the started task is set up to use TCP/IP. It states the
started task name, the port it is listening on, and the name of the TCP/IP job running on the system.
●
PGTT1721I TCP ASID xxxx NOT Listening on Port yyyy to TCP job zzzz
Explanation:
This message is displayed when the started task is not set up to use TCP/IP. It states the started task
name, the port, and the name of the TCP/IP job running on the system.
●
PGTT1722I IP request received from IP Addr: xxxx
Explanation:
A request is received for a transfer using the IP address xxxx.
●
PGTS1733I TCP RESPONDER WAITING FOR SUBTASKS TO END BEFORE QUIESCE
Explanation:
This message is displayed when there is a request to shut down the Platform Server while
transactions using TCP/IP that are still active. When the transactions are completed, the Platform
Server shuts down.
●
PGTT1731I TCP Responder Program Terminating
Explanation:
This is a normal message that is displayed when the started task is brought down.
●
PGTT1736I SNMP TRAP errors exceed xxxx: TRAP processing disabled
Explanation:
The Platform Server receives an error continuously for 10 times during sending a TRAP. The TRAP
feature becomes disabled, and no more TRAPs is sent.
●
PGTT1737I TCP IUCV interface used: TCP version V3R1
Explanation:
When the Platform Server comes up, it dynamically determines the version of TCP that is running.
This is done because the interface changes between TCP version 3.1 and 3.2. This message indicates
that the started task has detected that TCP 3.1 is running, and therefore, the IUCV interface is used.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
186
●
PGTT1738I TCP HPNS interface used: TCP version V3R2 or greater
Explanation:
When the Platform Server comes up, it dynamically determines the version of TCP that is running.
This is done because the interface changes between TCP version 3.1 and 3.2. This message indicates
that the started task has detected that TCP 3.2 is running, and therefore, the HPNS interface is used.
●
PGTT1740I TCPIP STC xxxxxxxx has been restarted: You must enter TERMTCP/STARTTCP
commands to activate the TCP interface
Explanation:
The started task has determined that the TCP/IP started task xxxxxxxx has been restarted. The TCP
interface must be restarted by using the TERMTCP and STARTTCP operator commands, or by
restarting the started task.
●
PGTT1743I tttttttttt TCP COSNAME=cccccccc SendBuffSize=xxxx RecvBuffSize=yyyy
Explanation:
This message is displayed at the start of the Platform Server file transfer when TCP communications
detects a COS entry for a file transfer request. It is displayed for informational purposes only and
displays the size of the SEND and RECEIVE buffers associated with the file transfer request.
●
PGTT1744I tttttttttt TCP Node=nnnnnnnn Total=xxxx Send=yyyy Recv=zzzz Init=aaaa
Resp=bbbb Bytes Per Second(BPS)
Explanation:
A Platform Server transfer is being performed for a node. The BPS_xxxx parameters are set within
the node definition to throttle the throughput of file transfers. This message displays the different
values that are defined to limit throughput. This message is displayed for information purposes
only.
●
PGTT1745I tttttttttt TCP xxxxxx COSNAME=cccccccc PacketSize=yyyy MAXBPS=mmmm
Prty=zz
Explanation:
A Platform Server transfer is being performed for a node. The BPS_xxxx parameters were set within
the node definition to throttle the throughput of file transfers. This message displays the packet size
that is being used, and the maximum BPS that is used for this request. If the number of concurrent
transfers with a node changes, this message is displayed again, because the MAXBPS value is recomputed when the concurrent number of transfers with a node changes. This message is displayed
for information purposes only.
●
PGTT1746I Executing the following command to ssssssss the TCP interface:
ccccccccccccccc
Explanation:
The Platform Server detects that the TCP/IP started task has changed. Most likely this is because the
TCP/IP started task has been brought down and up again. The Platform Server automatically stops
and starts its TCP/IP interface by executing a Platform Server operator command. The command
that is executed is displayed as ccccccc.
●
PGTT1750I TCP TRACE Enabled for: nnnnnnnnnn
Explanation:
A TCP trace is enabled for a node, IPv4 address or IPv6 address.
●
PGTT1756I TCPTRAC ALREADY TURNED OFF
Explanation:
The TCPTROFF command is entered to turn off tracing for a node or IP address. However, tracing is
already turned off.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
187
●
PGTT1757I TCP TRACE FACILITY CLOSED
Explanation:
The trace file is closed as a result of the TCPTROFF command.
●
PGTT1758I TCP TRACE FACILITY ENABLED
Explanation:
TCP tracing is enabled because of the TCPTRON command or the TRACE parameter on a batch request.
●
PGTT1760I TCPTRAC turned off for: nnnnnnnnnn
Explanation:
Because of the execution of the TCPTROFF operator command, tracing is turned off for a node or IP
address.
●
PGTT1761I DNS Name lookup: IP Name=nnnnnnnnn IP Address=iiiiiiiiiii
Explanation:
A DNS request is executed for IP name nnnnnnnn. The name is resolved to IP address iiiiiiii. Note
that the IP address can be an IPv4 or IPv6 address.
●
PGTT1762I DNS Address lookup: IP Address= IPV6 or IPV6 address IP Name=nnnnnnnnnn
Explanation:
A DNS request is executed for IP address iiiiiiii. The address is resolved to IP name nnnnnnnn. All
responder requests attempt to resolve the IP name from the incoming IP address. This IP name is
used to identify the node definition associated with the incoming request.
●
PGTE1912I Activity tttttttttt has been updated by user exit FUSEX06
Explanation:
The user exit FUSEX06 is invoked and updates parameters in the queue entry for the activity tttttttt.
The return code 1 upon return from the exit indicates the activity is updated.
●
PGTF2105I Activity xxxx failed due to Unknown error on transfer with remote
system: yyyy
Explanation:
The activity xxxx fails because of an unknown error with the remote system. yyyy denotes the
remote system.
●
PGTS2127I Activity xxxx with Node yyyy purged due to Security Error on FMH5
Explanation:
The transfer request is purged because of a security error.
Check the user ID and password used for this transfer.
●
PGTF2128I Command Activity xxxx successfully executed on Remote system: yyyy
Explanation:
The xxxx command is successfully executed on the remote systems denoted by yyyy.
●
PGTF2129I Connection terminated with Node xxxx Request purged from queue
Explanation:
The transfer request is purged because the connection to the remote system is terminated.
●
PGTF2130I Premature Termination with Node xxxx Activity yyyy Purged from Queue
Explanation:
The transfer request is purged because the connection to the remote system is terminated.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
188
●
PGTF2131I Activity xxxx Fusion connection failure - Attempting connection with
KNFusion application
Explanation:
If no APPLICATION parameter is stated in the transfer job or the node definition, then Fusion FTMS
attempts a connection with the Fusion FTMS protocol. If this fails, then the KNFusion protocol is
attempted.
●
PGTF2132I Activity xxxx failed with Remote node yyyy record would be truncated
Explanation:
The record length of the file is larger than the record length stated in the transfer job. Therefore, if
the file is transferred, the records are truncated.
●
PGTE2199I xxxx
Explanation:
This is a debug message for platform internal use.
●
PGTE2212I Activity tttttttttt REXX exec: eeeeeeee RC: nn purged from Queue
Explanation:
REXX exec eeeeeeee is run in the Platform Server address space. It is assigned activity number tttttttt
and completed with a return code of nn. This is the standard message that is displayed when a
REQEUT type of REXX is initiated.
●
PGTE2217I FUSION REXX EXEC waiting for prior EXEC to complete
Explanation:
Only one REXX exec can run at a time within the Platform Server started task. Because one is
currently running, this request has to wait until the active request is completed.
●
PGTE2221I Data: dddddddd returned by REXX exec: eeeeeeee
Explanation:
The Platform Server executes REXX exec eeeeeeee from within the Platform Server address space. The
exec returns data dddddddd to the Platform Server started task.
●
PGTE2222I REXX Exec: eeeeeeee completed successfully - no data returned by REXX
exec
Explanation:
The Platform Server executes REXX exec eeeeeeee from within the Platform Server address space. The
exec is completed successfully, but no data is returned by the exec to the Platform Server started
task.
●
PGTE2223I REXX exec failed with return code xx from IRXEXEC processor
Explanation:
The Platform Server tries to run a REXX exec from within the Platform Server address space, but the
program is terminated with return code xx. If this problem persists, contact TIBCO
Technical Support.
IRXEXEC
●
PGTB2243I User not Authorized to use Platform Server: Request allowed due to WARN
mode
Explanation:
The Platform Server is defined to restrict its usage to a limited group of users. The user that
submitted the file transfer request is not authorized to use the Platform Server. The Platform Server
GLOBAL EXTENDED_SECURITY_RESOURCE parameter is set to WARN. Therefore, the file transfer
continues after displaying this message.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
189
●
PGTB2245I User not Authorized to use Node xxxxxxxx: Request allowed due to WARN
mode
Explanation:
The Platform Server is defined to restrict the usage of the Platform Server nodes to a limited group
of users. The user that submitted the file transfer request is not authorized to use the Platform
Server node xxxxxxxx. The second parameter of the Platform Server GLOBAL
EXTENDED_SECURITY_RESOURCE parameter is set to WARN. Therefore, the file transfer continues after
displaying this message.
●
PGTE2298I xxxx
Explanation:
Debug message for platform internal use.
●
PGTE2299I xxxx
Explanation:
Debug message for platform internal use.
●
PGTE2310I text message from user exit
Explanation:
This message displays the text message returned by the user exit.
●
PGTS2404I The Platform Server Node=nnnnnnnn successfully enabled by user=uuuuuuuu
Explanation:
A Platform Server Command Center NODE ADD request is received for node nnnnnnnn by user
uuuuuuuu. The request is successful and the node is successfully enabled.
●
PGTS2405I The Platform Server Node=nnnnnnnn successfully deleted by user=uuuuuuuu
Explanation:
A Platform Server Command Center NODE DELETE request is received for node nnnnnnnn by user
uuuuuuuu. The request is successful and the node is successfully deleted.
●
PGTS2420I Node Disable request pending for Node=nnnnnnnn: SAPI Request currently
active
Explanation:
A Platform Server Command Center NODE DELETE request is received. But NODE nnnnnnnn is
currently executing a SAPI request. The node is disabled when the SAPI request is complete.
●
PGTS2426I CCC BROWSE request failed - Not Authorized: Access limited to
Userid=uuuuuuuu
Explanation:
A Command Center user tries to browse the Platform Server AUDIT file. The Platform Server
performs the necessary checks, and finds that the user is not authorized for the
CCC_BROWSE_FACILITY or the CCC_ADMIN_FACILITY resource. As a result, the user can only view
audit records for his or her own user ID. This is an information message that shows the user is
limited to viewing transfers for user uuuuuuuu. To enable the user to view more messages, you must
give the user read authorization for the GLOBAL CCC_BROWSE_FACLITY resource.
●
PGTS2428I CCC nn: MFTNQ returned @2 records
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.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
190
●
PGTS2459I FUSPING xxxxxxxx yyyyyyyy
Explanation:
The Platform Server CFPING request is executed. This is an informational message that displays
version information about the Platform Server system.
●
PGTS2460I FUSPING Packet nnnn Bytes=xxxx yyyy milliseconds
Explanation:
The Platform Server CFPING DATA request is executed. This is an informational message that
displays the packet number, packet size, and the time taken to get a response from the remote
system.
●
PGTS2570I cccccccc MFT Platform Server STC Name: Version: vvv Maint: mmm mmm
Explanation:
This message gives the name of the started task, the version, and the maintenance level of the
Platform Server. This is the result of the VER modify command (F servername,VER).
●
PGTS2574I DATASPACE: xxxx HAS AN STOKEN OF yyyy
Explanation:
The user entered the F server_name,STK command. The output of this command is the STOKEN
of the Queue Data In Virtual (DIV) data space STOKEN.
●
PGTS2575I Modify command received
Explanation:
This is a normal message that is displayed after any valid modify command is entered.
●
PGTS2576I Command not supported: xxxx
Explanation:
This is an informational message that is displayed after a unsupported modify command is entered.
●
PGTS2579I Modify STOP command received, shutting down server: xxxx
Explanation:
This is a normal message that is displayed when the STOP modify command is used to shut down
server xxxx.
●
PGTS2580I PROCESSING SNAP
Explanation:
The Platform Server is processing the snap dump that is taken.
●
PGTS2582I Modify RESET command received
Explanation:
This is an informational message.
●
PGTS2583I Modify QUIESCE command received: xxxx
Explanation:
This is a normal message that is displayed when the QUIESCE modify command is used to shut
down server xxxx.
●
PGTE2600I Command cccccccc not supported: Platform Server DNI not activated
Explanation:
The Platform Server DNI operator command cccccccc is executed, but DNI is not activated. This is
typically because the GLOBAL DNIKEY parameter specified is invalid.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
191
●
PGTE2623I DNI member mmmmmmmm ENABLED: DNIENA command successful
Explanation:
The DNIENA operator command was entered to enable a DNICFG entry, and the entry was enabled
successfully.
●
PGTE2643I DNI Updated request with new xxxxxxxx: yyyyyyyy replaces old xxxxxxxx
value
Explanation:
DNI is processing a 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.
●
PGTE2647I DNI Transid tttttttt Deleted: DNIPURGE command successful
Explanation:
The DNIPURGE command for DNI transfer ID tttttttt is entered. The command is executed
successfully and the request is purged from the DNIACT queue.
●
PGTE2650I DNI TRN=tttttttt DSN=dddddddd
Explanation:
This message is displayed as a result of the DNIDISP command entered without a transfer ID. It
displays a summary list of DNI transfer IDs and the DSN associated with them.
●
PGTE2651I DNI xxxxxxxx: yyyyyyyy
Explanation:
This message is displayed as the result of the DNIDISP command specified with a transfer ID.
xxxxxxxx defines the field and yyyyyyyy defines the data associated with the field. This message is
displayed multiple times for each detail display: once for each field that is displayed.
●
PGTE2652I DNI nn requests found on the DNIACT queue
Explanation:
This is a summary message that is displayed as the result of the DNIDISP command entered without
a transfer ID. It shows the number of messages (nn) that are on the DNIACT queue.
●
PGTE2656I DNI Locate for DNICFG=mmmmmmmm DSN=dddddddd exceeds max count of nn
entries
Explanation:
DNI is processing a catalog locate request for 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.
●
PGTE2671I DNI Member=mmmmmmmm DSN=ddddddddd
Explanation:
This message is displayed when the user enters the DNINODE command without specifying any
additional parameters. This message shows the DNI member name and the data set filter used. This
message is displayed once for each enabled DNI definition.
●
PGTE2672I DNI xxxxxxxx = yyyyyyyy
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
192
This message is displayed when the user enters the DNINODE command and specifies the DNI node
name. This message shows the detailed information displayed about the DNI node. This message is
displayed once for each DNI node field displayed.
●
PGTE2674I DNINODE No DNI members are enabled
Explanation:
The user enters the DNINODE command without specifying a DNI node name. No DNI nodes are
currently enabled.
●
PGTE2704I PPASCRPT: Script request scheduled successfully
Explanation:
A PPA CALLJCL request was executed for program PPASCRPT. This is an information message that
indicates that the script request was submitted successfully to the started task.
●
PGTT2803I Activity tttttttttt Job jjjjjjjj iiiiiiii has been dddddddd due to
rrrrrrrr
Explanation:
This message indicates that request tttttttttt for job jjjjjjjj with job ID iiiiiiii has been completed. This
message indicates whether the Sysout file has been kept, deleted, or held, based on the NODE LDISP
parameter. It also indicates whether the transfer request was successful, or failed with a permanent
network error or permanent error.
●
PGTT2804I Activity tttttttttt FUSSAPIP Attempting restart, but SAPI DSN changed:
Starting from beginning
Explanation:
SAPI request tttttttttt was being restarted. Before restarting the request, the Platform Server checks
that the JES 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.
●
PGTF3100I xxxx Activity yyyy started to Remote System: zzzz [ SNA | TCP ]
Explanation:
The server transmission subtask has commenced processing the file transfer named in the message
text.
●
PGTF3101I Activity xxxx successfully transferred yyyy records with node zzzz
Explanation:
This is a normal message that is displayed at the end of a successful transfer. The number of records
that were transferred is also reported in this message.
●
PGTF3102I Activity xxxx started to Remote Open System: yyyy
Explanation:
The activity referenced in the message text has been commenced by the transmission subtask.
●
PGTF3103I Activity xxxx successful with node yyyy
Explanation:
The activity xxxx requested to the remote system is completed successfully.
●
PGTF3104I Activity xxxx successfully received yyyy records from remote system:
zzzz
Explanation:
The Platform Server has successfully retrieved the target file from the remote computer.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
193
●
PGTF3105I Remote system: xxxx sent F-Close-Request prior to F-Read-Request - No
records sent for activity yyyy
Explanation:
When you receive this message, contact TIBCO Technical Support.
●
PGTF3106I Activity xxxx failed with Remote Open System: yyyy
Explanation:
Activity failed to the remote system.
See previous diagnostic messages for the possible cause of failure.
●
PGTF3107I Activity xxxx successfully send yyyy records to remote system: zzzz
Explanation:
This is a normal message that is displayed at the end of a successful transfer. The number of records
that were transferred are also reported in this message.
●
PGTF3108I xxxx RC=yyyy zzzzz Record Count=nnnn
Explanation:
This is a variable message that includes the transaction number for the transfer, the return code, the
node, the name of the file being transferred, the number of records transferred, the transfer type
(send or receive), and a description of the transfer.
●
PGTF3110I Activity xxxx Delete Successful to: yyyy of: zzzz
Explanation:
The remote file is deleted successfully.
●
PGTF3113I Activity xxxx compression type=yyyy compressed bytes=zzzz compression
ratio=nnnn:1
Explanation:
This message is displayed when compression is used to show the number of bytes that were
compressed and the compression ratio.
●
PGTF3114I Activity xxxx with Node yyyy suspended - Activity put on hold
Explanation:
Transfer xxxx with node yyyy is suspended using the F
●
server_name,SUSPEND
command.
PGTF3115I Responder Activity xxxx with Node yyyy suspended - Activity [NOT]
purged from queue
Explanation:
Activity xxxx with node yyyy is suspended. The transfer was either purged or not purged
depending on the checkpoint setting for the transfer.
●
PGTF3116I Initiator Submit for activity xxxx successful - job yyyy (zzzz records)
submitted to internal reader
Explanation:
This message is displayed when a File to Job transfer is submitted to the JES internal reader. xxxx is
the activity number, yyyy is the job name, and zzzz is the number of records in the job.
●
PGTF3117I Initiator Submit for activity xxxx failed - Queue entry purged
Explanation:
This message is displayed when a Platform Server file to job transfer is submitted to the JES internal
reader and the transfer fails. In this case, activity xxxx is deleted from the queue.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
194
●
PGTF3118I Network error on activity xxxx node: yyyy - activity will be retried at
next retry interval
Explanation:
An error was detected when processing transfer activity xxxxxxxxxx to node yyyy. The error is
retried at the next retry interval. This is an informational message.
●
PGTF3119I Network error on activity xxxx node: yyyy - retry count exceeds maximum
- activity purged
Explanation:
The transfer has exceeded the number of retries as stated in the Try parameter and is now purged.
●
PGTF3133I xxxxxxxx Activity tttttttt started to Backup Node aaaaaaa bbbbbbb
ccccccc dddddddd eeeeeeee ffffff
Explanation:
A file transfer request has failed with a network error. The NODE definition had been defined with
one or more BACKUPLUNAME, BACKIPIPNAME, or BACKUPIPADDR parameters. This message indicates
that the SEND or RECEIVE request (xxxxxxxx) for activity tttttttttt is retried to back up node
aaaaaaaa. It also defines whether the transport is TCP or SNA and the level of encryption configured.
●
PGTF3135I rrrrrrrr Activitytttttttttt: Processing TLS ttttt request with node
nnnnnnnn
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.
●
PGTF3138I SSL Debug aaaaaaaa bbbbbbbb ccccccc dddddddd eeeeeeee
Explanation:
A user requested the Platform Server to display DEBUG output when SSL requests are executed.
This is only done at the request of TIBCO Technical Support. To turn off the SSL Debug messages,
issue the Platform Server SSLDEBUG=NO operator command.
●
PGTF3139I SSL Debug dddddddd: RC=xx Sense=yy
Explanation:
A user requested the Platform Server to display DEBUG output when SSL requests are executed.
This is only done at the request of TIBCO Technical Support. To turn off the SSL Debug messages,
issue the Platform Server SSLDEBUG=NO operator command.
●
PGTF3152I Activity tttttttttt Encrypt changed to NONE due to NODE ENCRYPT=NEVER
parameter
Explanation:
The user submitted a request that utilizes data encryption. However, the NODE definition defined
for the request contains the ENCRYPT=NEVER parameter. This indicates that encryption should never
take place for transfers to this node. This message indicates that the encryption defined is
overridden to no encryption. The transfer request continues, and no data encryption takes place.
●
PGTF3155I xxxxxxxx error on activity: tttttttt node: nnnnnnnn - Error will be
retried in yy seconds
Explanation:
The Platform Server 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.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
195
●
PGTF3156I tttttttt CALL to program pppppppp Successful: Return code=nn
Explanation:
The Platform Server has received a CALLPROG or CALLJCL request from a remote system. The
Platform Server has called program pppppppp. The call was successful, and the program passed a
return code of nn (this should be zero) back to the Platform Server. This message indicates that the
CALLPROG or CALLJCL request was successful.
●
PGTF3183I Activty tttttttttt ENCRYPT changed from xxxxx to yyyyy due to HIPAA
Regulations
Explanation:
The Platform Server was executing initiator activity tttttttttt and detected that the HIPAA parameter
was defined as YES for either the GLOBAL or NODE definition. The Platform Server determined
that the encryption level was less than 112 bits. Because of this, the Platform Server changed the
encryption type to one that supported at least 112 bits. This is an informational message only. No
action is required. The transfer continues normally with the new encryption type.
●
PGTF3187I tttttttttt CFACCESS changed DSN from dddddddddd to eeeeeeeeee
Explanation:
The Platform Server responder transaction tttttttttt was running. The Platform Server CFACCESS
processing changed the 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.
●
PGTF3190I tttttttttt CFALIAS changed DSN from dddddddddd to eeeeeeeeee
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.
●
PGTE3196I $CFDIR Error loading IGGCSI00: Using DNICSI00 module for LOCATE
requests SMS Version: xx
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.
●
PGTE3202I tttttttttt Failed due to COSNAME=nnnnnnn Priority=xx: Transfer will be
retried at next interval
Explanation:
The Platform Server was processing transaction tttttttttt using COS name nnnnnnnn. The COS entry
defined the priority as xx (either 00 or 01). When a priority of 00 or 01 is received, the Platform
Server does not allow that transfer to start. The transfer is terminated and this message is sent back
to the Platform Server system. Because this is a retryable error, the Platform Server might retry the
request at a later time, depending on the number of tries defined for the transfer request.
●
PGTE3203I tttttttttt COSNAME=cccccccc not found: COS processing will not be
performed
Explanation:
The Platform Server was processing transaction tttttttttt using COS name nnnnnnnn. The Platform
Server looked through the list of enabled COS names, but it could not find name nnnnnnnn. In this
case, the transfer continues and no COS processing is performed.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
196
Make sure that COS name nnnnnnnn is defined in the CONFIG DD statement and activated at
startup or through the Platform Server ENA operator command. To get a list of enabled COS entries,
use the Platform Server COS operator command without any additional parameters.
●
PGTF3210I tttttttttt Starting xxxx Directory request LF=llllllllllll
RF=rrrrrrrrrrrrrr
Explanation:
The Platform Server 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.
●
PGTF3211I tttttttttt Directory transaction uuuuuuuuuu completed with Code=@4
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.
●
PGTF3218I tttttttttt Directory Transfer: xxxxxxxx Success=nn Failure=nn
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.
●
PGTF3222I tttttttttt DIRTEST=YES Directory Transfer: xxxxxxxx Files=nn
Explanation:
The Platform Server was performing a directory transfer send or receive (xxxxxxxx). The user
specified the DIRTEST=YES. The number of files that were extracted is displayed. No transfers were
actually performed because the DIRTEST=YES setting.
●
PGTF3223I tttttttttt Checkpoint Restart not supported for DBCS Translation:
Checkpoint Restart turned off
Explanation:
The Platform Server was performing a file transfer request with DBCS turned on. The user specified
that checkpoint restart should be allowed for this file transfer, but checkpoint restart is not
supported when DBCS conversion is turned on. Checkpoint restart is turned off for this file transfer
request.
●
PGTF3227I aaaaaaaaaa: Request sent to RocketStream Server: iiiiiiii: pppp
Explanation:
The Platform Server was initiating a request and detected that this request was defined as a
RocketStream request. It notifies the user that the request 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.
●
PGTF3231I aaaaaaaaaa: xxxxxxxx Directory transaction aaaaaaaaaa scheduled with
Code=nn
Explanation:
A directory transfer request was scheduled. The activity number (aaaaaaaaaa) of the directory
transfer, whether the transfer is a send or receive (xxxxxxxx), the activity number of the file transfer
request being queued, and the return code of the request being queued are displayed.
●
PGTF3232I Activty aaaaaaaaaa ENCRYPT changed to AES due to GLOBAL FIPS140 Setting
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
197
A request was initiated on the Platform Server for z/OS system. The request must be run as a FIPS
140 request because of the setting of the GLOBAL or NODE ENFORCE_SECURITY_POLICY parameter.
The transfer request was not configured with AES encryption. The Platform Server automatically
changed the request to use AES encryption to comply with FIPS regulations.
●
PGTF3238I tttttttttt ASYNCWAIT transfers exceed max of nn: Subsequent transfers
will be executed with WAIT=YES
Explanation:
The user executed a directory transfer with WAIT=ASYNCWAIT. While executing the directory transfer,
the number of transfers exceeded the maximum number of transfers allowed to be executed
asynchronously. Transfers scheduled after this message is displayed is executed with WAIT=YES.
●
PGTF3239I tttttttttt ASYNCWAIT transfer completed with RC=nn
Explanation:
The completion return code for a transfer submitted with WAIT=ASYNCWAIT
message is not written to the console; it is only written to the OSIMSGS log.
●
is displayed.
This
PGTF3240I tttttttt Transfer terminated: NODE nnnnnnnn has RESPHOLD=YES: Transfer
can be retried at a later time
Explanation:
A transfer request was received for node nnnnnnnn. However, the node is in a Responder Hold
state. The transfer request is terminated with a recoverable network error.
Issue the RESPREL operator command or use the ISPF panels to release the hold and allow transfers
to be accepted from this node.
●
PGTF3241I Node nnnnnnnn set to INITHOLD=YES: Remote error exceeded the Node
INITIATOR_ERROR_HOLD limit of xxx
Explanation:
An initiator transfer request was performed with node nnnnnnnn. The transfer partner reported an
unrecoverable error. When this error occurs, a count of consecutive remote errors is incremented.
The error count exceeds the NODE INITIATOR_HOLD_ERROR limit of xxx; the node is placed in
INITHOLD state, so that no initiator requests can be initiated to this node.
When the problem causing the remote errors is resolved, issue the INITREL operator command or
use the ISPF panels to release the hold and allow transfers to be initiated to this node.
●
PGTE3247I tttttttttt: CRC=cccccccc: Partner does not support CRCCHECK
Explanation:
Platform Server is configured to perform CRC checking. However the transfer partner does not
support CRC processing, so MFT cannot validate the partner's CRC. This message is displayed for
information purposes only.
●
PGTE3249I ttttttttt: CRC=cc: Local and Partner CRC match
Explanation:
Platform Server is configured to perform CRC checking. The CRC computed by the sender matches
the CRC computed by the receiver. This message is displayed for information purposes only.
●
PGTE3250I ttttttttt: Local CRC=cccccccc
Explanation:
Platform Server is configured to perform CRC checking. This message is displayed when Platform
Server for z/OS is the sender.
●
PGTE3251I tttttttttt: Checkpoint Restart turned off because TRUNCATE=YES was
defined
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
198
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.
●
PGTE3252I tttttttttt: TRUNCATE=YES turned off because CCSID translation table
defined
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.
●
PGTE3253I tttttttttt: Checkpoint Restart turned off because multi-byte conversion
table was defined
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.
●
PGTE3257I tttttttttt: TRUNCATE=YES not supported for zOS to zOS transfers:
Truncate turned off
Explanation:
The TRUNCATE=YES parameter was specified for a zOS to zOS file transfer, but Truncate is not
supported for zOS to zOS transfers. TRUNCATE=YES is turned off and the transfer continues.
●
PGTF3502I SSL Request accepted from node nnnnnnnn by default: No match on SSLAUTH
config was found
Explanation:
An SSL request was received from node nnnnnnnn. The Platform Server scanned its SSLAUTH file
for a match on the components of the certificate distinguished name, but could not find a match.
This message indicates that by default, the Platform Server accepts the SSL request. Processing of
the request continues.
●
PGTF3503I SSL Request accepted from node nnnnnnnn: Match on SSLAUTH entry:
eeeeeeee
Explanation:
An SSL request was received from node nnnnnnnn. The Platform Server scanned its SSLAUTH file
for a match on the components of the certificate distinguished name and found a match. The
SSLAUTH entry indicated that the request should be accepted. This message indicates that the
Platform Server accepts the SSL request. The SSL entry that detected the match is also displayed as
eeeeeeee. Processing of the request continues.
●
PGTF3504I SSL Request rejected from node nnnnnnnn: Match on SSLAUTH entry:
eeeeeeee
Explanation:
An SSL request was received from node nnnnnnnn. The Platform Server scanned its SSLAUTH file
for a match on the components of the certificate distinguished name, and found a match. The
SSLAUTH entry indicated that the request should be rejected. This message indicates that the
Platform Server rejects the SSL request. The SSL entry that detects the match is also displayed as
eeeeeeee. Processing of the request is terminated.
●
PGTS3509I gsk_fips_state_set "ON": SSL/TLS running in FIPS Mode
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
199
TLS FIPS mode is successfully activated. This message is for informational purposes only.
●
PGTF3510I tttttttttt: TLS (xxxxxxx) Negotiation complete using Cipher: cccc:
( ddddddd)
Explanation:
This message is displayed when a successful TLS negotiation is completed for transaction tttttttttt.
xxxxxxxx defines the TLS protocol used, 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.
●
PGTE3520I SSLAUTH Processing complete - Good records: xxxx Error records: yyyy
Explanation:
The SSLAUTH program completed processing. This is a summary record to display the number of
good records and the number of error records. This message is displayed at startup and when the
SSLAUTHREFRESH command is executed.
●
PGTE3522I SSLAUTH Error: Invalid character following / on Record xxxx - Must be
CN L S C OU O SN SDATE STIME EDATE ETIME: Record follows
Explanation:
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.
●
PGTE3523I SSLAUTH Error: Expecting = after DN component on Record xxxx: Record
follows
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.
●
PGTE3524I SSLAUTH Error: Received EOF when waiting for continuation on Record
xxxx: Record follows
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.
●
PGTE3525I SSLAUTH Error: Request type must ACCEPT or REVOKE on Record nnnn:
Record follows
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.
●
PGTE3526I SSLAUTH Error: DN exceeds max of 256 bytes on Record xxxx: Record
follows
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.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
200
The record in error will be displayed following this message. This entry in the SSLAUTH file will
not be enabled.
●
PGTE3527I SSLAUTH Error: Invalid xxxxxxxx parameter on record nnnn Must be
yyyyyyyy: Record follows
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.
●
PGTE3528I iiiiiiiiiiiiiiiiiiiiiiiiiiiii’
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.
●
PGTE3529I SSLAUTH Internal error: FINDVECT failed with RC=xx: Contact Platform
technical Support
Explanation:
The Platform Server was processing the SSLAUTH data, and received an internal error.
Contact TIBCO Technical Support if this error re-occurs.
●
PGTE3530I SSLAUTH DD has invalid DCB: Must be RECFM=FB,LRECL=80: SSLAUTH
Processing terminated
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.
●
PGTE3531I SSLAUTH DD not defined: SSLAUTH processing terminated
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.
●
PGTE3532I SSLAUTH DD OPEN failed: SSLAUTH processing terminated
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.
●
PGTE3800I Activity tttttttttt xxxx_ACTION has submitted jjjjjjjj JCL=ddddddddddd
Explanation:
The Platform Server transfer action processing has submitted job number jjjjjjjj for activity tttttttttt.
The JCL used to submit this job was defined as dddddddddd. This is an informational message only.
No action is required.
●
PGTE3812I Activity tttttttttt PPA RC=rr xxxxxx: cccccccccc
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
201
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.
●
PGTE 3816I Activity tttttttttt xxxx_ACTION CFACCESS SUBMIT_OPTION=ROOT changed
SUBMIT DSN to dddddddddd
Explanation:
The Platform Server was executing a PPA (Post Processing Action) SUBMIT request. PPA was
checking the CFACCESS configuration file and detected a match. The entry was defined with
SUBMIT_OPTION=ROOT which means that the transfer file name is actually the member name. The
member name was enclosed in parentheses and appended to the SUBMID_HLQ name. The resulting
DSN is displayed as dddddddd. This message is displayed for informational purposes only.
●
PGTE3840I FUSUTIL RENAME ddddddd to nnnnnnn
Explanation:
The Platform Server was processing the Platform Server for z/OS FUSUTIL utility. The Platform
Server displays this message when it is about to rename a data set. The data set that is to be
renamed is ddddddd. This message is displayed for informational purposes only.
●
PGTE3850I CFACCESS Processing complete - Good records: nnnn Error records: eeee
Explanation:
The Platform Server completed processing the CFACCESS configuration file. This is an
informational message that shows the number of successful and unsuccessful entries processed.
●
PGTE3858I CFACCESS DD not defined: Bypassing CFACCESS processing
Explanation:
The Platform Server was attempting to process the CFACCESS DD statement, but detected that the
CFACCESS DD statement was not defined. The CFACCESS parameter file is not processed, and as
such no CFACCESS checking is performed. This is an informational message only.
Review the accompanying z/OS messages to determine the cause of the failure.
●
PGTE3880I CFALIAS Processing complete - Good records: xx Error records: yy
Explanation:
The Platform Server had completed processing the CFALIAS configuration file, either at startup or
when the Platform Server CFALIASREFRESH operator command was executed. This message is an
informational message and shows how many good and error records were processed.
●
PGTE3888I CFALIAS DD not defined: Bypassing CFALIAS processing
Explanation:
The Platform Server was processing the CFALIAS configuration file. The Platform Server detected
that the CFALIAS DD statement was not defined in the startup JCL. CFALIAS processing is
bypassed. No CFALIAS processing is performed for any transfers. To use CFALIAS, you must add
the CFALIAS DD statement to the Platform Server started task startup JCL, and then bring the
Platform Server down and up.
●
PGTE3900I SUBJCL Processing complete - Good records: nn Error records: ee
Explanation:
The SUBJCL configuration program has completed processing. This informational message
indicates that nn good records and ee error records have been processed.
●
PGTE3908I SUBJCL DD not defined: Bypassing SUBJCL processing
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
202
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.
●
PGTE3920I TRCLASS Processing complete - Good records: nn Error records: nn
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.
●
PGTE3922I TRCLASS DD not defined: Bypassing TRCLASS processing
Explanation:
An attempt was made to open the TRCLASS DD statement, but the DD Statement was not defined.
In this case, TRCLASS processing is disabled.
To enable TRCLASS processing, add the DD statement to the MFT started task JCL and point it to a
valid TRCLASS configuration file. The MFT SAMPLIB member TRCLASS shows an example of how
the TRCLASS parameters are defined.
●
PGTE3928I TRCLASS Num=xx Name=nnnnn MAX=yy Current=zz
Explanation:
This message is displayed when the TRCLASSDISP operator command is executed. One message is
displayed for each TRCLASS defined. It displays the TRCLASS number, name, maximum number
of transfers, and the current number of transfers for each transfer class.
●
PGTE3932I tttttttttt TRCLASS "nnnnnnnnnn" changed to TRCLASS NUM xx
Explanation:
A transfer that defined a transfer class was submitted. Transfer class nnnnnnnnnn was found in the
TRCLASS table and was converted to transfer class xx.
This is an informational message; no action is required.
●
PGTE3950I Activity tttttttttt SUBJCL has submitted JOBxxxxx JCL=jjjjjjjj
Explanation:
Activity tttttttttt was completed. The SUBJCL processing has submitted JCL jjjjjjjj. Job xxxxx is the
job that was submitted into the internal reader. This message is displayed for informational
purposes only.
●
PGTB4119I INVALID/MISSING SERVER PARM - DEFAULT USED
Explanation:
The name of the Platform Server used in the EXEC card of the Platform Server batch job is invalid or
missing.
Correct the error and re-submit the transfer.
●
PGTB4120I INVALID QUEUE EFFECT FOR ACTIVITY
Explanation:
This message is displayed for a RECEIVE operation under any of the following three circumstances:
●
was specified, but the file already exists.
●
EFFECT=CREATE
●
EFFECT=REPLACE
●
EFFECT=APPEND
was specified, but the file does not exist.
was specified, but the file does not exist.
PGTB4140I LIST xxxx SUCCESSFULLY QUEUED yyyy ACTIVITIES
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
203
Explanation:
The LIST parameter was used to distribute the file to several remote locations. This message reflects
how many activities were queued based on the LIST parameter that was specified.
●
PGTB4142I Schedule Request has completed with return code xxxxxxxx
Explanation:
This message is displayed after a request has been scheduled. It shows the return code associated
with a schedule request. A return code of zero indicates that the request was scheduled successfully,
while a non-zero return code indicates that the schedule request failed. This message is displayed
under the following two conditions:
●
●
When a schedule request fails
●
When a schedule request is successful and the user specified WAIT=NO
PGTB4143I Request has completed with return code xxxxxxxx
Explanation:
This message is displayed after a request specified with WAIT=YES has been completed. It shows the
return code associated with the request. A return code of zero indicates that the request has been
completed successfully, while a non-zero return code indicates that the request failed.
This message is only displayed after a request defined with WAIT=YES has been completed.
●
PGTB4193I IPADDR and IPNAME parameters ignored for transfer type: SCRIPT
Explanation:
The user was queuing a SCRIPT, SUBMIT, or REXX EXEC to the Platform Server started task. The
user specified the IPADDOR or IPNAME parameters. This message indicates that these parameters are
ignored during this type of transfer. This is an informational message. No action is required.
●
PGTB4194I NODE parameter ignored for SCRIPT Transfers: NODE CONTENTION_WINNERS
will be used to throttle transfers
Explanation:
The user was queuing a SCRIPT, SUBMIT, or REXX EXEC to the Platform Server started task. The
user specified the NODE parameter. This message indicates that the NODE parameter 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.
●
PGTE4230I Activity tttttttttt Script execution started: Output will be in ddname
dddddddd Explanation:
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.
●
PGTE4231I Activity tttttttttt Script execution successful: Script output is in
ddname dddddddd
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.
●
PGTE4234I Activity tttttttttt Script purged: Script output is in ddname dddddddd
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
204
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.
●
PGTE4235I Activity tttttttttt Script ended with retryable error: Request will be
retried at next error interval
Explanation:
The Platform Server was running a script. This is an 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 nonzero return code yy, but the user specified a try count of more than 1. The script is tried again at the
next error interval.
●
PGTE4239I tttttttttt INDIRECT=DELETE specified: DSN=dddddddddd will be deleted
Explanation:
The user was executing a script defined with the INDIRECT parameter set to DELETE. This is an
informational message that indicates the indirect file is deleted.
●
PGTE4240I tttttttttt INDIRECT parameter invalid: Must be YES, NO or DELETE:
Script terminated
Explanation:
The user executed a script defined with the INDIRECT parameter. The user specified a value for the
parameter other than YES or DELETE. The only valid values for this parameter are YES and
DELETE. The script is terminated with errors.
INDIRECT
●
PGTE4243I tttttttttt Script mmmmmmmmmm found in SCRIPT DD DSN=ddddd
Explanation:
The user scheduled a SCRIPT to execute in the started task. The script was defined with only a
member name. The STC looked up the member in the SCRIPT DD. The DSN that contained the
member name is defined in this message. This message is for information purposes only.
●
PGTN4505I Connection Identifier: xxxx Resource Identifier: yyyy - Activity: zzzz
Rmt Sys: nnnn
Explanation:
This is a normal informational message issued by the NPSI GATE drivers. It provides the NPSI
resource ID which is useful in interpreting VTAM buffer traces.
●
PGTN4506I Called DTE Addr: xxxx Calling DTE Addr: yyyy Facilities: zzzz Activity:
aaaa Remote Sys: bbbb
Explanation:
This is a normal message issued by the NPSI GATE drivers which provides some information about
the contents of an X.25 virtual call.
●
PGTX4510I Successful Requests=nn Failed Requests=ff Timeout Requests=tt
Explanation:
This message is displayed at the end of the FUSXJOB program. It indicates the number of successful
requests (nn), the number of failed requests (ff), and the number of requests that timed out (tt). This
message is for informational purposes only.
●
PGTX4511I FUSXJOB ending with Return code rr
Explanation:
This message is displayed at the end of the FUSXJOB program. It indicates the return code (rr) that
FUSXJOB returns to the operating system. This message is for informational purposes only.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
205
●
PGTX4512I Activity tttttttttt Queued to Platform Server started task
Explanation:
The user executed the Fusion XCOM interface and specified TYPE=EXECUTE or TYPE=SCHEDULE. This
message shows the activity number (tttttttttt) that was associated with the file transfer request. This
message is displayed for informational purposes only.
●
PGTX4514I PARM pppppppp Ignored within Platform Server
Explanation:
The user executed the Platform Server XCOM interface and specified the PARM parameter
pppppppp. Parameter pppppppp is ignored within FUSXJOB. This message is displayed for
informational purposes only.
●
PGTX4516I SYSIN01 Parameter pppppppp not supported by Platform Server: Transfer
continues
Explanation:
The user executed the Platform Server XCOM interface and specified the SYSIN01 parameter
pppppppp. Parameter pppppppp is not supported by FUSXJOB. Because this parameter is not critical to
the completion of the transfer request, it is ignored. This message is displayed for informational
purposes only.
●
PGTX4517I SYSIN01 Parameter pppppppp Option oooooooo not supported by Platform
Server: Transfer continues
Explanation:
The user executed the Platform Server XCOM interface and specified the SYSIN01 parameter
pppppppp. Some values of parameter pppppppp are supported, but the option specified (oooooooo) is
not supported by FUSXJOB. Because this parameter is not critical to the completion of the transfer
request, it is ignored. This message is displayed for informational purposes only.
●
PGTF4685I xxxxxxxx VSAM Invalid Record Length on CLOSE Error processing: Transfer
can only be restarted from beginning
Explanation:
The Platform Server was processing a file transfer request for a VSAM file. The Platform Server was
closing the file, but VSAM returned a code indicating that the record length was too small. This is
typically because a network error occurred and only a partial record was written to the VSAM file.
In this circumstance, the Platform Server detected that a checkpoint restart was not possible. The
Platform Server updated the QUEUE record to indicate that checkpoint restart should not be
attempted, and that additional processing for this transfer should start from the beginning of the
file.
●
PGTF4686I xxxxxxxx VSAM Invalid Record detected during CLOSE Error processing:
Error is ignored
Explanation:
The Platform Server was processing a file transfer request for a VSAM file. The Platform Server was
closing the file, but VSAM returned a code indicating that the record length was too small. This is
typically because a network error occurred and only a partial record was written to the VSAM file.
In this circumstance, the Platform Server ignores the error because it does not affect any future
checkpoint restart processing.
●
PGTF4687I tttttttttt VSAM RRDS Record Length=yyyy longer than MAX=zzzz: Transfer
Terminated
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
206
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.
●
PGTS5200I Platform Server Advanced xxxx initiated for Activity yyyy
Explanation:
The Platform Server is initiating the protocol to be used with this transfer.
●
PGTS5212I Error in APPC Subtask Allocating Storage for Subtask Control Blocks increase Region Parm
Explanation:
The subtask cannot allocate enough storage to do the transfer.
Increase the Region parameter in the transfer job.
●
PGTS5220I Msg from xxxx: <<Message Text>>
Explanation:
A message was received from node xxxx.
●
PGTS5221I Job Submitted as xxxx on Remote System yyyy
Explanation:
This is an informational message stating that the File to Job transfer was submitted to the remote
system.
●
PGTS5310I Network Error Received with Node xxxx Transaction Terminated
Explanation:
The session with xxxx has ended abruptly because of a network error.
●
PGTS5311I Request xxxx with Node yyyy purged due to Security Error on FMH5
Explanation:
Activity xxxx is purged for security reasons.
●
PGTS5555I APPC: <<Diagnostic message>>
Explanation:
Either debugging and/or tracing is enabled or an internal error has occurred.
If debugging or tracing is not enabled, note the full text of the message and contact TIBCO Technical
Support.
●
PGTS5556I <<Diagnostic message>>
Explanation:
Internal diagnostic messages issued during debugging and tracing.
●
PGTS5869I |TLV Contents : xxxx
Explanation:
Internal debugging message.
●
PGTS5870I Contents of FVCOMM Dsect
Explanation:
Internal debugging message.
●
PGTS5871I +-------------------------------------------------------
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
207
This message is issued to format a table in the log.
●
PGTS5872I | FVCOMM_VTAM_ADDR : xxxx
Explanation:
Internal debugging message.
●
PGTS5873I | FVCOMM_VTAM_ACBNAME : xxxx
Explanation:
Internal debugging message.
●
PGTS5874I | FVCOMM_VTAM_LUNAME : xxxx
Explanation:
Internal debugging message.
●
PGTS5875I | FVCOMM_VTAM_MODENAME : xxxx
Explanation:
Internal debugging message.
●
PGTS5876I | FVCOMM_USERID : xxxx
Explanation:
Internal debugging message.
●
PGTS5877I | FVCOMM_PASSWORD : xxxx
Explanation:
Internal debugging message.
●
PGTS5878I | FVCOMM_TPNAME : xxxx
Explanation:
Internal debugging message.
●
PGTS5879I | FVCOMM_REQ-Type : xxxx
Explanation:
Internal debugging message.
●
PGTS5880I | FVCOMM_SEND_DATA_Addr : xxxx
Explanation:
Internal debugging message.
●
PGTS5881I | FVCOMM_SEND_DATA_Len : xxxx
Explanation:
Internal debugging message.
●
PGTS5882I | FVCOMM_RECV_DATA_Addr : xxxx
Explanation:
Internal debugging message.
●
PGTS5883I | FVCOMM_RECV_DATA_Len : xxxx
Explanation:
Internal debugging message.
●
PGTS5884I | FVCOMM_RETURN_CODE : xxxx
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
208
Internal debugging message.
●
PGTS5885I | FVCOMM_Sense : xxxx
Explanation:
Internal debugging message.
●
PGTS5886I | FVCOMM_What_Received : xxxx
Explanation:
Internal debugging message.
●
PGTS5887I | FVCOMM_APPC_FLAG : xxxx
Explanation:
Internal debugging message.
●
PGTS5888I | FVCOMM_APPC_STATE : xxxx
Explanation:
Internal debugging message.
●
PGTS5889I | FVCOMM_CNOS_DATA : xxxx
Explanation:
Internal debugging message.
●
PGTS5890I _____Contents of TLVCOMM DSect_____
Explanation:
Internal debugging message.
●
PGTS6000I xxxx DATASPACE HAS BEEN CREATED
Explanation:
This is an informational message that indicates that a dataspace has been successfully created. xxxx
is the name of the dataspace that has been created.
●
PGTM7000I CPU Serial Number: nnnn Model Number: nnnn
Explanation:
Informational message.
●
PGTM7050I Loading xxxx Driver yyyy
Explanation:
An error occurred loading the transmission code.
Contact TIBCO Technical Support for assistance.
●
PGTS7100I CDE FOUND WITH CORRESPONDING FLAGS FOR THIS STARTED TASK
Explanation:
This is a normal message if the started task has been up and down since the last IPL.
●
PGTS7150I NO CDE ANCHOR FOUND, CREATING A NEW CDE ANCHOR
Explanation:
This is a normal message at startup if this is the first time the started task is brought up since the last
time there was a system IPL.
●
PGTM7202I Data set Dynamically Allocated for the Activity xxxx DDNAME: yyyy
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
209
A transmission subtask successfully issued SVC 99 to allocate an MVS file for the activity named.
This message is for informational purposes only.
●
PGTM7203I Data set Dynamically Unallocated for Activity xxxx DDNAME: yyyy
Explanation:
A transmission subtask successfully issued SVC 99 to free an MVS file for the activity named. This
message is for informational purposes only.
●
PGTM7204I Data set NOT Dynamically Allocated for Activity xxxx DDNAME: yyyy
Explanation:
An error occurred when a transmission subtask tried to allocate an MVS file using SVC 99. The file
is busy or the data set name is invalid.
See other accompanying messages for more information.
●
PGTM7205I Data set Not Dynamically Unallocated for Activity xxxx DDNAME: yyyy
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.
●
PGTM7206I Activity xxxx: Data set name not valid: yyyy
Explanation:
The local file name (initiator) or the remote file name (responder) was not a valid MVS data set
name.
●
PGTM7211I Create not allowed - File already exits for Activity xxxx
Explanation:
An attempt to create a file on the local MVS system failed because the file already exists.
●
PGTM7212I Send not allowed - File does not exist for Activity xxxx
Explanation:
An attempt to send a file on the local MVS system failed because the file did not exist.
●
PGTM7213I Append or Replace failed - File does not exist for Activity xxxx
Explanation:
An attempt to append or replace a file on the local MVS system failed because the file did not exist.
●
PGTM7214I Invalid Queue Effect on File for Activity xxxx
Explanation:
An invalid effect on the local MVS file was filled in the queue entry. Valid effects are: create, replace,
append, create or replace, and create or append.
●
PGTM7215I Invalid Space type specified in Global for Activity xxxx
Explanation:
An invalid space allocation type was filled in the queue entry. Valid space types are tracks,
cylinders, megabytes, and kilobytes.
●
PGTM7216I xxxx not allowed - File does not exist for Activity yyyy
Explanation:
The specified action failed because the file did not exist on the local MVS system.
●
PGTM7217I xxxx not allowed - File already exists for Activity yyyy
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
210
Requested action was not allowed because the file already exists.
●
PGTM7229I Activity xxxx allocating data set DISP=yyyy
Explanation:
The transfer is allocating the data set with yyyy disposition as specified in the transfer.
●
PGTM7230I JOBID=xxxx submitted to JES Internal Reader
Explanation:
This is a normal message that is displayed when a Platform Server File to Job transfer is submitted.
●
PGTM7285I tttttttttt File Deleted due to DISP=DNEW: ddddddddd
Explanation:
This message is displayed when a file (defined as ddddd) is deleted by the LDISP=DNEW or
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.
RDISP=DNEW
●
PGTM7293I tttttttttt Secondary allocation adjusted: Input Vol count=nn New Sec.
Allo.=nn: dddddddddd
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.
●
PGTM7297I tttttttttt DNEW request failed: Exclusive ENQ failed for DSN dddddddddd
Explanation:
A transfer request was specified with a disposition of DNEW. This means that the file is deleted before
the transfer and is reallocated again when the transfer starts. The server determined that the file is in
use. The transfer terminates with a recoverable error. If the try count was not exhausted, this
transfer is retried at the next dispatch interval.
●
PGTM7302I DYREASON xxxx S99ERROR yyyy S99INFO zzzz
Explanation:
This is diagnostic information reporting SVC 99 dynamic allocation feedback. This data might be
useful in resolving dynamic allocation problems and might be requested by TIBCO Technical
Support.
●
PGTM7303I Activity tttttttttt File Create transfer failed: DSN xxxxxxxxxxxx
deleted
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.
●
PGTM7321I tttttttttt Retryable error returned from HSM exit for DSN=dddddddd:
Request marked as File error
Explanation:
The HSM user exit (turned on by setting the GLOBAL EXIT03=YES and EXIT_MIGRATE_VOLUME
parameters) returned an error indicating that a retryable error occurred processing the recall
request. The Platform Server marks the request as a temporary error and retries the request when
the GLOBAL FILE_ERROR_RETRY_INTERVAL setting expires.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
211
●
PGTM7332I Activity tttttttttt DSN=dddddddddd deleted due to DISP=DELETE on xxxxx
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.
●
PGTM7335I Activity tttttttttt Checkpoint not supported for VS/VBS/FS/FBS files:
Checkpoint turned off for fffffffff
Explanation:
The user was attempting to perform a file transfer for a variable spanned or fixed standard file 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.
●
PGTM7336I Activity tttttttttt Error on VSAM xxxxxx: Request: R15=rr R0=ss
Explanation:
The Platform Server was processing a VSAM file to extract information about the VSAM file to send
to the remote end. The Platform Server received an error on a VSAM request defined as xxxxxx. The
return and reason codes are displayed as rr and ss. If this problem persists, contact TIBCO Technical
Support.
●
PGTM7337I Activity tttttttttt Error on VSAM xxxxxx: R15=rr ACBERFLG=ss
Explanation:
The Platform Server was processing a VSAM file to extract information about the VSAM file to send
to the remote end. The Platform Server received an error on 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.
●
PGTM7338I Activity tttttttttt Invalid VSAM file type: DSN=dddddddddddd must be
KSDS/ESDS/RRDS
Explanation:
The Platform Server was processing a VSAM file to extract information about the VSAM file to send
to the remote end. The Platform Server detected that the VSAM file was not a KSDS, ESDS, or RRDS
file. Because these are the only types of VSAM files that are supported, the request terminates with
an error.
●
PGTM7339I Activity tttttttttt RESTART on empty VSAM file: Restart - turned off
for this transfer
Explanation:
The Platform Server was processing a VSAM file to extract information about the VSAM file to send
to the remote end. The Platform Server detected that a restart was requested, but the file was empty.
The Platform Server therefore turned off restart for this transfer, and the transfer request will be
started from the beginning.
●
PGTM7340I Activity tttttttttt Cannot create DSN=ddddddddddddd: Unable to create
VSAM Variable RRDS file
Explanation:
The Platform Server was processing a VSAM file, detected that the file did not exist, and was about
to create the file. However, the Platform Server was unable to create a variable length RRDS file. The
file transfer request terminates and this message is sent to the remote end. If you need to transfer a
variable length RRDS, the file must exist before it can be processed by the Platform Server.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
212
●
PGTM7342I Activity tttttttttt Restart Failed: Will start from beginning because
file dddddddd not does not exist
Explanation:
The Platform Server for z/OS was responding to a Platform Server request to restart a file transfer
request. The Platform Server detected that the file requested dddddddd did not exist and therefore,
the Platform Server 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.
●
PGTM7348I tttttttttt RECFM=VBS LRECL exceeds 32760 - Changed to 32760 for DSN:
dddddddd
Explanation:
A transfer request was received for a VBS file and the LRECL for this file was greater than the
maximum LRECL supported by MFT. This is an informational message that indicates the LRECL
was changed to the maximum LRECL supported (32760). No action is required.
●
PGTM7349I Restart on RECFM=VB file detected: Repositioning to next block
Explanation:
A restart request was received by MFT. This is an information message that is displayed under the
following circumstances:
●
The file transfer was for a file receive (that is to say, MFT was writing data)
●
The RECFM was VB
The restart was positioned to the block after the checkpoint was taken
No action is required by the user when this message is displayed.
●
●
PGTM7356I tttttttttt RESTART not supported on MAINTAINRDW - Restart turned off
for file dddddddddd
Explanation:
The user specified the MAINTAINBDW or MAINTAINRDW parameter, but the transfer was defined to use
checkpoint restart. The transfer will continue without checkpoint restart support.
Checkpoint restart is not supported when the MAINTAINBDW or MAINTAINRDW parameter is defined.
●
PGTM7357I tttttttttt RESTART not supported on TAPE LBI files - Restart turned off
for file dddddddddd
Explanation:
The user was transferring 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.
●
PGTM7363I tttttttttt Unable to send VSAM file properties to the remote system
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.
●
PGTM7400I Physical Record Larger than Logical Record for Activity xxxx
Explanation:
This message is issued when the record being written is larger than the logical record length of the
MVS data set. Make sure that the maximum string length is less than or equal to the logical record
length.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
213
●
PGTM7401I Invalid Record Separator xxxx found for Activity yyyy
Explanation:
Contact TIBCO Technical Support.
●
PGTM7402I tttttttttt Invalid $SYSOUT field - must be CLASS/DEST/WRITER/FCB/FORM:
xxxxxxxxxxxxxxxxxxxxxx
Explanation:
The user was performing a file to file transfer, and specified the Platform Server for z/OS file name
as $SYSOUT. This indicates to the Platform Server that the request is actually a file to print request.
The data following $SYSOUT describes the z/OS fields that 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.
●
PGTM7403I tttttttttt Invalid $SYSOUT field value for parameter: xxxxxxxx
Explanation:
The user was performing a file to file transfer and specified the Platform Server for z/OS file name as
$SYSOUT. This indicates to the Platform Server that the request is actually a file to print request. The
data following $SYSOUT describe the z/OS fields that 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.
●
PGTM7450I Abort Requested for Activity xxxx
Explanation:
Abort was requested for the specified transfer.
●
PGTS7500I xxxx WILL USE A SYSTEM LINKAGE INDEX OF xxxx FOR ENHANCED CROSS MEMORY
SERVICES
Explanation:
This is an informational message.
●
PGTS7650I CREATING TABLE ENTRY FOR XMS SERVICES
Explanation:
This is an informational message.
●
PGTS7700I CONNECTION TO XMS ENTRY TABLE SUCCESSFUL XMS SERVICES ARE NOW ENABLED
Explanation:
This is an informational message.
●
PGTS8763D REPLY -T- to Terminate not waiting for subtasks to end - otherwise
shutdown will wait for them to end
Explanation:
Currently some subtasks are active for this started task. You might choose to end the started task
without waiting for the subtasks to end.
●
PGTS9001I STOP command being processed
Explanation:
This is a normal informational message that is displayed when the STOP command is issued to bring
the started task down.
●
PGTS9100I ALET NUMBER CREATED: xxxx DSPTOKEN yyyy
Explanation:
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual
214
This is an informational message which shows the STOKEN that is returned when a dataspace is
created.
●
PGTS9438I Detaching dispatcher subtask
Explanation:
Informational message issued at shutdown.
●
PGTS9450I SNAP DUMP PROCESSING HAS COMPLETED
Explanation:
The snap dump that was taken has finished.
●
PGTN9777D xxxx
Explanation:
This is a detail diagnostic message for use by platform field engineering staff only.
●
PGTN9998I Detail MSG: xxxx
Explanation:
This is a diagnostic message used by platform field engineering staff only. It displays information
from the Platform Servers internal control blocks.
TIBCO® Managed File Transfer Platform Server for z/OS Message Manual