Troubleshooting

This section provides possible solutions to some issues that you might encounter when using the platform server.

Restore Not Possible

Problem: on the RECEIVE command, the following error occurs when the installation data set has been transformed to the mainframe with an LRECL that is not 80: 

Restore not possible. Input data is not complete.     
The first record is:                       
Received file appears not to be an Interactive Data Transmission Facility file.
X'00FF0000'                                  
Data set X.RECEIVE.INVALID.FILE from USERID on N1     
Enter copy parameters or 'DELETE' or 'END' +
Solution: make record length fixed block 80.

Allocation Failure

Problem: the following error occurs on the RECEIVE command if the data set received is already allocated. 

RECEIVE INDS(prkevin.test.delete.loadlib)                                 
Data set PROD.FT710.LOAD from PRKEVIN on AL     
Enter restore parameters or 'DELETE' or 'END' +         
                                 
RECEIVE command terminated. Output data set unusable. +     
Allocation failure for data set 'PROD.STABLE.IND$FILE.LOADLIB'  
DATA SET PROD.FT710.LOAD ALREADY IN USE, TRY LATER+ 
DATA SET IS ALLOCATED TO ANOTHER JOB OR USER

Solution: use a new data set for the RECEIVE command.

Rebuilding the Work Queue

Problem: errors occur when you delete and redefine the work queue file using the DEFQUEUE command.

Solution: the server must be down before you run the DEFQUEUE command.

Trouble with VSAM Files

Problem: decoding VSAM errors

The platform server keeps a machine readable log to keep a record of all past activities. This log is a key sequenced data set. If there is a problem with the audit file, the server prints a diagnostic field called the RPLFDBWD.

Solution: you must know the following logic when analyzing the VSAM errors:
  • The first byte identifies the specific IBM VSAM module (part of z/OS data facility product) which is reporting the error. This does not have meaning to you, but IBM technical staff can tell you what VSAM module this represents and what it is doing.
  • The second byte identifies the type of error. The most common user caused error type is X'08' which means logic error.
  • The third byte is not used.
  • The fourth byte is the error reason code as documented in chapter 4 of the IBM manual OS/390/DFP Macro Instructions for Data Sets.

See the following examples on how to decode the RPL feedback word.

Example 1: RPLFDBWD 47080048

This is the VSAM request parameter list from the IBM supplied RPL mapping DSECT. It is interpreted as following:
  • First byte: identifies the specific IBM VSAM module that reports the error. The X'47' identifies IDA019R8 which is a VSAM record management routine responsible for keyed I/O as per IBM technical support.
  • Second byte: X'08' means that this is a logic error. If an LERAD routine has been specified in the VSAM ACB, it can be driven; however, VSAM LERADs is not used in the platform server for z/OS.
  • Third byte: reserved.
  • Fourth byte: '48' is the logical error reason code as documented in chapter 4 of the IBM manual OS/390 DFP 3.3 Macro Instructions For Data Sets (SC26-4747). Essentially, a return code of X'48' means that the platform server tries to do indexed I/O on a non-indexed data set. For example, the platform server treats the data set as KSDS, but it is actually ESDS or RRDS. This can be the result of an installation error.
Example 2: RPLFDBWD 0A080008
  • First byte: the X'0A' identifies the IBM VSAM Module IDA019RA, which detected the error; the module does direct record locate.
  • Second byte: the value X'08" indicates a logic error.
  • Third byte: reserved.
  • Fourth byte: X'08' means the platform server tries to store a record with a duplicate key. This can be caused by the audit file and the work queue falling out of synchronization with each other.

Activating the VTAM Resources

Problem: VTAM resource does not become active.

Solution: go through the Defining the VSAM Files and verify that the VTAM resources have been defined properly.

Remote Nodes Are Not Coming Active When the Product Is Started

Problem: you receive message PGTS1131E indicating that MEMBER IS NOT ACTIVATED DUE TO ERRORS.

Solution: check the remote node configurations and verify that you have specified all of the correct information.

Transaction Does Not Start after It Is Queued.

Problem: transaction is placed on the queue as inactive.

Solution: check if the remote node became active when you start up the platform server. If not, check the remote node configurations and verify that you have specified all of the correct information. You have to check the eligible time and date to see if it is the current time and date.

Repeated Error Message for the Same Transaction

Problem: you continually receive the same error message on the system console.

Solution: check if retry limit is zero. If so, the platform server is having difficulty performing this transaction and is continually retrying. To avoid this. you can set the retry limit to a non-zero value.

Receiving a SENSE=087D0001

Problem: VTAM cannot find the LU. 
IST663I BFINIT REQUEST FROM NCP066 FAILED, SENSE=087D0001
IST664I REAL OLU=TIBCO.DANL1I2  REAL DLU=TIBCO.FUSNAPPL
IST889I SID=F2CF2303704E1476
IST894I ADJSSCPS TRIED FAILURE SENSE ADJSSCPS TRIED FAILURE SENSE
IST895I ISTAPNCP    08400007
IST314I END

Solution: the most likely cause of this is that the LU is not active. Check if the LUs are all active.

Receiving a SENSE=08570003

Problem: the session is not active. 
IST663I BFINIT REQUEST FROM NCP066 FAILED, SENSE=08570003          
IST664I REAL OLU=TIBCO.DANL1I2  REAL DLU=TIBCO.FUSNAPPL      
IST889I SID=F2CF2303704E1708                       
IST1138I REQUIRED RESOURCE TIBCO.FUSNAPPL NOT ACTIVE           
IST314I END
Solution: the probable cause is that the platform server is not up and running, therefore the APPL LU is not active. Check if the platform server address space is up and that the APPL LU is active.

Batch Job Has Been Submitted However It Has Not Been Placed on the Queue

Look in the output from the JCL for any error messages. The following table lists some of the messages that you might see:

Key Number Error Message Cause User Response
PGTB4100E Parameter not recognized in next record Most likely the cause is a typo. Verify that the specified in the line after this message is correct.
PGTB4102E Invalid parameter value in next record The value specified for this parameter is not valid. Check the valid range of values for this parameter.
PGTB4103E Data set name not cataloged The data set that is specified for this transaction is not cataloged. Verify that the data set name is specified correctly.
PGTB4105E Operand read before a PROCESS card The parsing program found parameters before your process card. Verify that you specify the process card correctly and that all parameters follow the process card.
PGTB4106E Invalid number of operands in next record The number of operands is outside the valid number. Verify that you specify this number correctly.
PGTB4107E No more room left in the server work Queue The maximum number of transactions are currently on the work queue. You can either wait for some of the transactions that are on the queue to complete and be removed, or you can re-create the work specifying a larger VSAM file.
PGTB4108E Fusion server not available The server to which you specified this transaction to be queued is not currently up and running. Start the server and re-queue.
PGTB4109E Security denied access You do not have authorization to one of the resources that you specified. Verify that you have authorization to the resources specified in the batch job.
PGTB4115E No process card in the SYSIN file The required process card is not found by the parsing routine. Verify that you correctly specified a process card for this batch job.
PGTB4116E Prior process not queued - Parameter error There is an error in one of the parameters specified for the previous process. Verify that the parameters specified are correct.
PGTB4117E Required parameter missing in next record The required parameter in the next record is missing. Check that you have specified a value in the next parameter field.
PGTB4118E Required parameter invalid in next record The required parameter in the next record is invalid. Check that the parameter is within the valid range.
PGTB4119I Invalid/Missing Server parm - Default used The server is not specified or is invalid. The default server is used to queue this transaction. To queue this transaction to a different server, you can specify the server parameter with the correct server.
PGTB4120I Invalid Queue effect for activity Queue effect is specified was invalid for this transaction type. Check that you specified a valid value.
Note: If you want further technical assistance, you can contact TIBCO technical support through the following contact information. 
Within the United States:
	TIBCO Technical Support
	200 Garden City Plaza
	Garden City, NY 11530
	USA
	Phone:	516-535-3636
	Email:	support@tibco.com
Outside of the United States:
Please contact your local TIBCO distributor.