0% found this document useful (0 votes)
40 views2 pages

Unattached Jobs

MAPICS uses unattached jobs (u-jobs) to process transactions in the background without slowing down the user. U-jobs are visible in the CAS inquiry and can be maintained to start, hold, or end them. For example, when a raw material is entered in inventory, it can generate several hundred transactions that a u-job processes to not overload the user. These u-jobs run under the QBATCH subsystem and their status can be seen cycling between DEQW and DEQA as they check for transactions to process.

Uploaded by

Varun Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
40 views2 pages

Unattached Jobs

MAPICS uses unattached jobs (u-jobs) to process transactions in the background without slowing down the user. U-jobs are visible in the CAS inquiry and can be maintained to start, hold, or end them. For example, when a raw material is entered in inventory, it can generate several hundred transactions that a u-job processes to not overload the user. These u-jobs run under the QBATCH subsystem and their status can be seen cycling between DEQW and DEQA as they check for transactions to process.

Uploaded by

Varun Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Unattached jobs:

MAPICS uses unattached job, or u-jobs, to process transactions in the background without holding up
the user. 

These ujobs are visible in CAS, inquiry, unattached jobs, and can be maintained in CAS, maintenance
change, option 12 unattached jobs. For example, when a RM is entered in INV, it can generate several
hundred transactions. If the user had to wait for all these transactions to process, he would be
unproductive for several minutes. So, the RM and generated IP transactions are sent to a data queue
until they can be processed by the ujob.

These ujobs can be recognized by looking at the jobs running under the QBATCH subsystem. The first
character of the job number will begin with a U and the third character will be the environment in which
the UJOB is running. Normally, the status of the ujob will be DEQW, but will cycle to DEQA every 5-10
seconds. When it gets to DEQA, it wakes up and checks the data queue for work. If transactions are
found, the status will go to RUN and it will process all transactions in the data queue.

Uobs are started automatically if their status is ENDED if transactions need processing. If the Ujob has a
status of HELD, it must be manually released before it will process transactions.
Ujobs can be ended with the CAS maintenance change, option 12 unattached jobs. If they are currently
processing transactions, this may take some time.`

Addional Infor

[6:58 PM] Ankush Khot

An Unattached Job (U-Job) is an application transaction processing program that is 


not attached to a work station. The transactions are 'submitted' for processing from 
one or more FEEDER programs. The U-Job is executed from the AMUJOBQ job 
queue. When submitted, a U-Job is started immediately since AMUJOBQ is created 
with maximum active jobs set to *NOMAX.
Once started, a U-Job continues to execute until the system operator shuts it down. 
When there are no transactions for a U-Job to process, the U-Job normally waits to 
receive a 'trigger' (any data) on the DTAQ. This type of wait uses minimal system 
resources. The 'trigger' indicates that there is either transactions to be processed or 
that the U-Job is to be shut down.
Associated with each U-Job is a record in a control file (UJBCTL) and a data queue 
(DQaxxxxxxx), where 'a' = application designator and 'xxxxxxx' indicates the specific 
U-Job. A one byte field (UJRST) in the control file indicates the last requested status. 
A second one byte field (UJCST) in the control file indicates the current (last posted) 
status of the U-Job. This status is accurate in most cases, and is sufficient for normal 
processing needs. The 'real' status can be determined by calling a CAS service 
program AXZUS.
Valid values for requested status are:
• 1 - START
• 3 - HOLD
• 4 - END
• 6 - RELEASE
Valid values for current status are:
• 1 - ACTIVE
• 3 - HELD
• 4 - ENDED
If the status is ACTIVE, the application feeder program may add transactions to the 
transaction file and send triggers to the DTAQ. If the status is HELD or ENDED, 
transactions can still be added to the transaction file and triggers sent to the DTAQ, 
however the transactions will not be processed until the U-Job is activated.
When a feeder is initiated, it calls AXZSR to determine the 'real' status of the U-Job 
and START the U-Job if necessary. It places the transactions to be processed into a 
transaction file (TRANS) and sends a trigger on the DTAQ. The trigger may or may 
not contain data. AXZSR calls AXZPSI to submit a U-Job. Shut down requests are 
communicated to the U-Job via the control file (UJBCTL) and a trigger sent on the 
DTAQ. The control record for a U-Job is the contention point for that U-Job. It will be 
allocated (read for update) at critical points when there must be only one program 
updating the control file. The 'maximum record wait time (WAITCD)' for the UJBCTL 
file will be the default of 60 seconds. 
It is up to the system operator to HOLD or END active u-jobs by using the Unattached 
Jobs Status (Update) menu option. Additionally, feeders may be requested to shut 
down. Feeder programs can monitor the requested status field (UJRST) for a HOLD
or END request. When detected, the user can be forced to exit the program. Any 
transaction that has been entered must be honored. They will still be sent to the u-job 
but may not be processed until the u-job is restarted. 

[6:58 PM] Ankush Khot

It is also up to the system operator to RELEASE all u-jobs that were held when 
dedicated mode was set. The Unattached Jobs Status (Update) menu option would 
be used to release held u-jobs.

You might also like