Unattached Jobs
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
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.