Troubleshooting
About troubleshooting polling problems
This section provides troubleshooting guidelines for polling problems.
No @I transactions are received
This may occur when a problem exists at the data collection server.
To solve this, use System Monitor to verify the communications status in case the data collection server did not properly initialize communication with the AS/400. Check the Transaction Log table in the data collection database. This database was created by your system administrator during system implementation, and resides on your database server.
Quit command
A QUIT command is received from the host at startup. An issue may arise when the host polling program does not find the Data Collection Server definition.
To solve this, review the message queue, review the conditions and take the appropriate action.
Retrieve job description information API failure
This message is followed by the message number received by the application interface call. If the job attempted to retrieve the job description through Retrieve Job Description Information application interface call, its name will also be listed. This may occur when a job description cannot be found.
To solve this, use System Monitor to verify the communications status. Check to see that agent settings match what is on the AS/400. Check the Transaction Log table in the data collection database. This is the database your system administrator created during your system implementation. The database resides on your database server.
TCP/IP polling messages
This may occur when the host Polling program cannot find the data collection server (DCS) name that was created in the DCS menu. When this occurs, the following message displays: "The data collection server is unknown."
To solve this, verify the library lists for the Interactive job and the Polling job are the same. The Polling Job Description is defined in the TranConnect SYS Parameters through the SYS menu. The Polling Job Description is typically DCLINKJBD1.
Find the TCP/IP sever job servicing this instance of the TCP/IP polling and diplay the job log. Typically, these jobs are found in the QSYSWRK subsystem and are named QZRCSRVS. Review the job log for each QZRCSRVS instance until you find the one for your TCP/IP polling process.
User shutdown
This message may display when the following message displays in the message queue: "The user requested SHUTDOWN."
To resolve this issue, verify the DCS data area for the data collection server does not contain a value of SHUTDOWN.
About troubleshooting pipeline problems
This section provides troubleshooting guidelines for polling problems.
Pipeline and interface programs
The pipeline is not running the specified interface program.
This may occur because the value in the MTD Edit program field is set to *NONE. When the value is set to *NONE, the pipeline does not run either routine.
To solve this issue, verify the MTD Edit Program field contains a valid interface program name.
Pipeline start
The pipeline does not start.
This may occur when the referenced library in SYS for the default DC subsystem is not found. The subsystem is automatically created during the software installation and must be included in your library list. Each additional environment must include the correct subsystem entry in the DCLINKSYS data area.
To solve this issue, verify your system configuration and make sure that the DC subsystem parameter and its library have been defined correctly in the System Parameters (SYS) menu. The DCLINKSYS data area must match the environment in which you are running TranConnect.
Pipeline status remains at *SHUTDOWN
In the Start/Stop Transaction Processing form, the pipeline status remains at *SHUTDOWN long after it should have changed to *OFF, or the pipeline status remains *STARTED long after it should have changed to *ACTIVE.
This issue may be caused when subsystem jobs are not running or duplicate jobs are running.
To resolve this issue, complete the following steps.
-
On a command line, enter WRKACTJOB SBS(systemname) and press Enter.
-
Check for essential jobs, the formatter job, and processor job(s).
-
If anomalies persist, continue to the next troubleshooting condition.
Pipeline transaction failure
Transactions fail in the pipeline because the data area VTTL@ is not being created.
This may be caused because the value of the enterprise system Installed Flag field in the DCLINKSYS data area is not equal to J.
To solve this issue, verify the enterprise system Installed Flag field has a value of J. Use the SYS menu to verify this flag.
Subsystem jobs
There is only one subsystem job active or there are duplicate jobs active.
This may occur when the pipeline does not complete a start or stop.
To solve this issue, complete the following steps to force the pipeline to turn off and restart.
-
On a menu selection line, enter SST and press Enter.
-
Locate the data collection server of the pipeline job, and for Opt, enter F and press Enter.
-
Press F3 until the command line displays.
-
On a command line, enter WRKACTJOB SBS(systemname) and press Enter.
-
If subsystems are running, wait 30 seconds and press F5 to refresh.
-
Press F3 until the command line displays.
-
Reenter the menu system.
-
On a menu selection line, enter SST and press Enter.
-
Locate the data collection server of the pipeline job.
-
In the Option column for the selected system, enter 1 and press Enter.
Transaction processing - no transactions are processing
No transactions are processing through the pipeline.
This issue may cause the pipeline status to not read *ACTIVE.
To resolve this issue, complete the following steps.
-
On a menu selection line, enter SST and press Enter.
-
Locate the data collection server of the pipeline job.
-
If the status is *OFF, select option 1.
Transaction processing - system message requiring a response is waiting
A system message that requires a response is waiting.
To resolve this issue, complete the following steps.
-
On a command line, enter WRKACTJOB SBS(systemname) and press Enter.
-
If any subsystem job has a status of MSGW, display the message and respond as necessary.
About troubleshooting transaction errors
You can use the following list to troubleshoot transaction errors that may occur in TranConnect.
Job Log
This error may occur when the Job Log becomes filled and the QJOBMSGQFL system value does not equal *WRAP.
Solve this issue by verifying the QJOBMSGQFS system has a value of *WRAP; however, do so only if you want all job logs in the system to wrap.
Transactions going to *ERREDT
This error may occur when transactions go to *ERREDT, but when viewed in the corrections program all that is required is an [Enter] key. The cause of this issue is the library list for the user that started the pipeline does not match the library list of the interactive session user who is accessing the server.
Solve this issue by ensuring the common library resides in both the Pipeline and Interactive Session library lists.
Transaction ID not valid
This error may occur when the formatter program reports that a transaction ID is not valid for the specified business area code (BAC). The cause of this issue happens when the formatter job (PGM-DC10FMT) cannot find the user index server program (XUIIDX).
Solve this issue by verifying the XUIIDX program is on the system and in the library list, and that the formatter job is authorized to use it. All three of these conditions must be met to resolve this issue.
Troubleshoot synchronization issues
If you suspect a problem with the polling program, check the following areas to solve the issue.
To troubleshoot synchronization issues, complete the following steps.
-
Review the message queue.
-
Review the job log.
-
Review the QPRINT spool file and refer to the spooled output for the user who started the Socket Sync program.
Loading...
There was a problem loading this topic