Chapter 7: Working with the PCMANASYNC Job | Contents | SCVs | Search | Glossary | Reports | XML | Index | Chapter 9: Purging Active Procedures |
Chapter 8: Working with the PCINTASYNC Job
Purpose: The Interactive PC Manifest ASYNC function updates the system files with shipment information from the PC Manifest system.
The PCINTASYNC job is used only if you are interactively communicating with PC Manifest system. PCINTASYNC system reads records in the Manifest Upload New file (FLMNUL) and Manifest Upload Extended (FLMNUE). There is one record for each pick label scanned.
PCINTASYNC performs the following functions:
• Creates Order Transaction History records for each pick label scanned. Order Transaction History records can be displayed in Order Inquiry. Information on the Order Transaction History record includes the meter charge, weight of the package, ship via that was used to actually ship the package, carrier service level, and tracking number.
• Creates Manifest Audit records for each pick label scanned. Manifest Audit records are used to be sure that every package that was scanned and uploaded was billed.
• Sends records to the Billing ASYNC function so that the items that were shipped can be billed.
• Deletes the records from the Upload New file.
If the Interactive PC Manifest ASYNC (PCINTASYNC) function is active, the records will be processed immediately. If the function is not active when the records are sent, they will be processed as soon as the PCINTASYNC function becomes active again. All records are processed in the sequence in which they were sent to the data queue.
Records in the Interactive PC Manifest data queue cannot be displayed.
In this chapter:
• Display Asynchronous Job Screen (Displaying the Interactive PC Manifest ASYNC Job)
• Changing the Status of PCINTASYNC
• Starting and Ending PCINTASYNC
• Updates During Background Processing.
Display Asynchronous Job Screen (Displaying the Interactive PC Manifest ASYNC Job)
Purpose: This screen is used to display the job attributes for each background ASYNC job. This screen displays descriptive information about the ASYNC job.
How to display this screen: Enter 5 next to the PCINTASYNC job at the Work with Background Jobs Screen.
MSR0240 DISPLAY Display Asynchronous Job 3/13/97 12:57:08 Company #1
Data queue name . . . : PCINTDATAQ Job name . . . . . . : PCINTASYNC
Description . . . . . : Interactive PC Manifest Data Queue
Data queue length . . : 24 Library . . . . . . . : CWM20DDTA Wait time . . . . . . : 0 0=No wait, -1=Wait forever
Start . . . . . . . . : 3/13/97 9:47:06 TRISH_R End . . . . . . . . . : 3/13/97 9:55:10 TRISH_R
Controlling job ? . . : N (N=No, Y=Yes) System Option ? . . . : Y (N=No, Y=Yes)
Status . . . . . . . : I *INACTIVE
F3=Exit F12=Cancel |
Field |
Description |
Data queue name |
The name of the data queue where transactions records are sent for processing by this ASYNC job. The data queue name for PCINTASYNC is PCINTDATAQ |
Job name |
The name of the ASYNC job. |
Description |
The description of the ASYNC job. Alphanumeric, 40 positions; display-only. |
Data queue length |
The length of the data queue where transactions records for this ASYNC job are processed. The length of the PCINTDATAQ is 24 positions. Alphanumeric, 3 positions; display-only. |
Library |
The library list where the ASYNC job is defined. Alphanumeric, 10 positions; display-only. |
Wait time |
The length of time the function will wait for records to be sent for processing before it times out. Valid values are: 0 - No wait. The function ends when there are no records to process. 1 - Wait forever. The function will not time out when there are no records to process. Numeric, 1 position; display-only. |
Start |
The date and time the ASYNC job was last started and the User ID of the person who started it. (Date): Numeric, 6 positions; display-only. (Time): Numeric, 6 positions; display-only. (User ID): Alphanumeric, 10 positions; display-only. |
End |
The date and time the ASYNC job was last ended and the User ID of the person who ended it. (Date): Numeric, 6 positions; display-only. (Time): Numeric, 6 positions; display-only. (User ID): Alphanumeric, 10 positions; display-only. |
Controlling job ? |
A flag indicating whether this function controls other ASYNC functions. The controlling ASYNC function starts and ends other ASYNC functions. Valid values are: Y - This is a controlling ASYNC function. N - This is not a controlling ASYNC function. The CNTL_ASYNC job is the only controlling ASYNC job. Alphanumeric, 1 position; display-only. |
System Option ? |
A flag indicating whether this function is a system function that cannot be deleted by the user. Valid values are: Y - This function cannot be deleted by the user. N - This function can be deleted by the user. Alphanumeric, 1 position; display-only. |
Status |
The current status of the function. Valid status codes are: A - *ACTIVE I - *INACTIVE E - *ENDPEND J - *JOBQ R - *REORG Alphanumeric, 1 position; display-only. |
Changing the Status of PCINTASYNC
Purpose: You can change the status of an ASYNC job if it has ended, but the status indicates that it is still active. This situation occurs if the ASYNC subsystem is brought down while the background ASYNC jobs are still active; the background ASYNC jobs have really ended, but the status indicates that they are still *ACTIVE.
If the status is *ACTIVE, the ASYNC jobs cannot be started because the system considers them to be active. To restart the background ASYNC jobs you must change the status of each job to *INACTIVE manually.
Note: You cannot use the Change Status option to start or stop an individual ASYNC job. You must use the CNTL_ASYNC job to start or stop all the asynchronous jobs simultaneously
How to change the ASYNC jobs status:
1. Enter 11 next to the PCINTASYNC job at the Display Asynchronous Job Screen (Displaying the Interactive PC Manifest ASYNC Job).
2. A pop-up window displays from which you can select the status you want to assign to the background job. Enter 1 next to.
• Select *INACTIVE if the background job is ended and the status is currently *ACTIVE.
• Select *ACTIVE if the background job is running and the status is currently *INACTIVE.
Note: The status of each background job must be changed separately. Changing the status of the CNTL_ASYNC job will not change the status of the individual background ASYNC jobs.
Starting and Ending PCINTASYNC
Starting the job: When you start the ASYNC jobs by entering 7 next to beside the CNTL_ASYNC, the Interactive PC Manifest ASYNC will become active only if one or more companies in CWDirect have the PC Manifest Tool (B81) in the System Control file set to TRACERI and Interactive Processing (E56) in the System Control file set to A (for automatic). If you are not using Tracer Interactive as your PC Manifest tool or if you are using Tracer Interactive but not performing automatic updates to billing, the PCINTASYNC job will never be active.
Ending the job: When you end the ASYNC jobs by entering 8 next to the CNTL_ASYNC, the PCINTASYNC job may not end immediately. The PCINTASYNC job will end (become inactive) after the Wait Time defined in the System Control file has been reached. For example, if the wait time is 120 seconds, it may take as long as 120 seconds before the PCINTASYNC job becomes inactive.
Updates During Background Processing
Updates: PCINTASYNC performs the following functions and file updates:
• Creates Order Transaction History records for each pick label scanned. Order Transaction History records can be displayed in Order Inquiry. Information on the Order Transaction History record includes pick control number, the meter charge, weight of the package, ship via that was used to actually ship the package, and tracking number.
• Creates Manifest Audit records for each pick label scanned. Manifest Audit records are used to be sure that every package that was scanned and uploaded was billed.
• Sends records to the Billing ASYNC function so that the items that were shipped can be billed.
• Deletes the records from the Upload New file.
Chapter 7: Working with the PCMANASYNC Job | Contents | SCVs | Search | Glossary | Reports | XML | Index | Chapter 9: Purging Active Procedures |
SO01_08 CWDirect 18.0 August 2015 OTN