Job Management (My Jobs)

Purpose: Use the Job Management screen to work with submitted jobs that have been processed, are currently processing, or are waiting to be processed. The jobs listed at this screen include each interactive session for the user.

This topic also discusses options you can use to review the jobs currently running and correct a job’s status if it is inconsistent.

In this topic:

For more information: See:

Job Management Screen

How to display this screen: Click the My Jobs icon (

) in the upper right area of a screen), or select My Jobs from an Admin screen (such as the About

Application, Forms Management Screen, Document Management Screen, Commands, User Control, or System Messages screens). When you advance to the screen this way, it displays all jobs generated through your user ID. See the field descriptions and screen options below for information on how to filter the jobs listed on this screen.

Column sort: You can sort on any column by clicking the column heading name. When you first click, the sort is in ascending alphanumeric (A-Z) or numeric (lowest to highest) order. Click again to change the sort to descending (Z-A) or numeric (highest to lowest) order.

Information on this screen:

Field	Description
Output Queue	Provides the option for you to switch the job queue where one or more jobs should run. The system-delivered job queues are: QBATCH (default) = The default job queue for most submitted jobs, such as reports and batch updates and processing. Processes one job at a time (single-threaded queue). QSYSNOMAX = The default job queue for Generating Membership Orders (EGMO) and jobs submitted through Working with Integration Layer Processes (IJCT). Can process multiple jobs at the same time (multi-threaded queue). oms.job.queue.interactive = The job queue where interactive user sessions run. This job queue processes multiple jobs at the same time. ASYNC = The job queue where background processes, submitted through Using the ASYNC Jobs (MBJC), run. Can process multiple jobs at the same time. ECOMMERCE = The job queue where the ECOMM_CANC job and the ORDER_EDIT job (generated through the ORDER_IN job in Working with Integration Layer Processes (IJCT)) run automatically. Can process multiple jobs at the same time. PICKGEN = The default job queue for Streamlined Pick Slip Generation (WSPS), Reprocess Authorizations Screen (RPAA), and Processing Auto Deposits (SDEP). Processes one job at a time. AUTODEP = The default job queue for deposit processing. Processes one job at a time.
<- Route Job	Use this button to route a job to the queue selected in the Queue field, described above: Select one or more jobs from the Job listings area, below. Select a queue from the Output Queue field. Click this button to move the job to the selected queue. You can select a different route only if the job has not yet started to run (RDY status).
Job Listings	Default settings for jobs available for review: When you first advance to this screen, up to 200 jobs submitted by your user ID are currently available for review by scrolling up or down with the right-hand scroll bar. The jobs are listed in reverse chronological order (newest to oldest). A message displays if more that 200 jobs are available for review: `The maximum number of records was exceeded. Please refine search criteria. Showing records 1-200.` Available jobs updated when you filter: When you enter or select any search criteria and then click Filter, the screen displays up to 200 jobs that match these criteria. Example: The screen currently includes 200 jobs available for review in reverse chronological order (newest to oldest): 180 of these jobs run in QBATCH, and 20 run in ASYNC. When you select QBATCH from the Queue field and click OK, the screen displays up to 200 jobs that run in QBATCH. Available jobs restricted: If your user control record does not have All job authority selected, you cannot review jobs submitted by other users. Example: If you do not have All job authority, when you filter on a Job name of PICK_GEN, pick slip generation jobs submitted by other users are not displayed.
Action	An arrow in this field indicates an action can be performed against the job. Valid actions are: Hold = Available if the job’s status is Ready. Release = Available if the job’s status is Hold. End = Available if the job’s status is Message. Delete = Available if the job’s status is Ready, Hold, Finished, Error, or End. If you attempt to delete a job that is actually running, the screen displays an error message. See the Job Management Screen Options.
User name	The user name of the person who submitted the job, or who is using an interactive session. Defaults to your user ID. Submitted through web service request? When you use the CWProcessIn message or the ProcessIn message to start a periodic process, if the message did not indicate to wait for completion, the job is listed under the default user set up during installation; otherwise, if the message indicated to wait for completion, the job is not listed on this screen. Contact your cloud administrator or system administrator to confirm the user ID of the default user, and see Using the CWProcessIn Message to Start a Periodic Process or Using the ProcessIn REST Message to Start a Periodic Process for background. For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). Filter options: The following options are available only for users whose All Job Authority setting is selected: to display jobs submitted by another user: enter a complete, valid user ID and click OK. to display jobs regardless of the user who submitted them: clear the current entry in this field and click OK. See the Administration guide for more information on setting up users.
Job name	A code identifying the job. The job name for an interactive session has a name starting with QPADEV (for example, QPADEV0B9A). Defaults to blank. Note: The reports icon () indicates that the job has generated one or more reports. Once the job status is Finished, select the icon to advance to the Document Management (My Docs) screen, where you can review the reports generated by that job. Filter options: to display jobs based on job name: enter a full or partial job name and click OK. to display jobs regardless of name: if you have previously entered a job name, clear the entry and click OK. No report? If there was no information matching the selection criteria for the report, the system may not generate a blank report; instead, you see the reports icon () indicating that a report is available, but when you advance to the Document Management (My Docs) screen, there is no report available to review.
Job	A system-assigned identification number to track the job. Defaults to blank.
Status	The current status of the job. Defaults to all jobs regardless of status. Possible statuses are: blank (default) = Select this option to display all jobs regardless of status. Ready = The job is currently waiting in the indicated job queue for processing because another job is currently active in that job queue, and the queue is single-threaded (processes only one job at a time). Optionally, you can expedite processing by routing the job to a different job queue that does not currently have a job running, or that is multi-threaded: Select the job, select the Output Queue at the top of the screen, and click <- Route Job. Held = The job is held. Optionally, you can release the job by selecting the Action checkbox to the left of the job and selecting Release. Run = The job is currently running normally. It is not possible to hold the job or change its job queue. Finished = The job has finished running normally. If there is a reports icon () next to the job, you can click the icon to advance to the Document Management Screen and review or print the generated reports. Note: Generated forms (such as pick slips, purchase orders, or checks) are available at the Forms Management (My Forms) screen, not the Document Management (My Docs) screen.
	Message = Possible explanations: Order Administration has written a message to a log file, and the job cannot continue processing. Someone restarted Order Administration while the job was active. In this situation, you should end the job at the Job Management screen and then start it again the usual way. Occasionally, the async jobs go into Message status even though they are continuing to process records. See Troubleshooting the Async Jobs for more information. End = Someone has manually ended a job whose status was Run, but was not running normally (perhaps because the server rebooted while the job was running). In this case, use the JOBCLN periodic function. See Using the JOBCLN Function to Resolve Job Status Across Servers for more information. Error = Someone has manually ended a job that was not running normally. Integration layer jobs Jobs you start through the Working with Integration Layer Processes (IJCT) option might not display the current, correct status if they receive inbound messages and have not yet received any messages to process.
	Async jobs When the async jobs in the Background Job Control (MBJC) menu option are active, the system periodically checks the status of each async job, and changes the status to Run, if necessary. For example, if the ORDR_ASYNC job is active and you end it at this screen, the system automatically changes the status of the job back to Run. To start or stop the async jobs, use the Background Job Control (MBJC) menu option. See Working with the CNTL_ASYNC Job. Filter options: to display jobs by status: select a status from the drop-down list and click OK. to display jobs regardless of status: if you have previously selected a status, clear the entry and click OK.
Started	The date and time when the job started. Defaults to blank. NONE indicates the job has not yet finished (the status is Ready, Hold, or Run). Filter options: to display jobs started on or after a specific date: click the calendar icon (), select a date, and then click OK. to display jobs started on the current date: click the calendar icon, select Today from the bottom of the calendar, and click OK. to display jobs regardless of start date: if you have previously selected a date, clear the date and click OK.
Ended	The date and time when the job finished. Defaults to blank. NONE indicates the job has not yet finished (the status is Ready, Hold, or Run). Filter options: to display jobs ended on or before a specific date: click the calendar icon (), select a date, and then click OK. to display jobs ended on the current date: click the calendar icon, select Today from the bottom of the calendar, and click OK. to display jobs regardless of end date: if you have previously selected a date, clear the date and click OK.
Runtime	The amount of time, in seconds, that the job took to run. Set to 0 if the job has not yet completed. Display-only.
Output Queue	The job queue where the job will run, is running, or ran. Defaults to blank. See the Output Queue field above for a listing of system-delivered queues. Filter options: to display jobs by queue: select a queue from the drop-down list and click OK. to display jobs regardless of queue: if you have previously selected a queue, clear the queue and click OK.
Log	A link to a brief log file for the job; available if the job has finished running and your user ID is assigned to Rank 1. This log provides just a list of the programs called in order to complete the job. See Logs for additional logs you can use for troubleshooting.

Job Management Screen Options

Option	Procedure
Restrict or expand the list of displayed jobs based on one of the available column headings	See the Job Listings for information on how to filter the jobs displayed based on various criteria.
Refresh data listed on the screen	Click Refresh. Newly submitted jobs are added to the screen in RDY status as they are submitted, and the status of existing jobs is updated.
Sort by column	Click the column heading name. When you first click, the sort is in ascending alphanumeric (A-Z) or numeric (lowest to highest) order. Click again to change the sort to descending (Z-A) or numeric (highest to lowest) order.
Change a job’s status or queue
Hold a job	If the job has not yet processed (its status is Ready), you can hold it by selecting Hold in the Action field for the job.
Release a job	If the job is currently held (its status is Hold), you can release it by selecting Release in the Action field for the job.
End a job that is currently running	If the job’s status is Message, you can end the job by selecting End in the Action field for the job. A window opens if you have selected to end an active job: `Warning! You have chosen to end one or more active jobs. PRESS OK TO END JOB, or PRESS CANCEL TO LEAVE JOB RUNNING.` At this window, select OK to end the job and update its status to End. If a job is currently running but you suspect that the job is not running normally, use the JOBCLN periodic function. See Using the JOBCLN Function to Resolve Job Status Across Servers for more information. Note: Sometimes when you select to end a job, the job does not end and remains running. In this case, you can use the JOBCLN periodic function.
Delete an individual job	If the job’s status is Ready, Hold, Finished, Error, or End, and is not actually running, you can delete the job by selecting Delete in the Action field for the job. Note: Deleting a job also automatically deletes all generated reports for that job that would also be available under the Document Management (My Docs) screen; however, it does not delete forms that are available at the Forms Management (My Forms) screen.
Delete selected jobs	Select the check box to the left of each job you wish to delete and select Delete at the top of the screen. Note: You can delete a job only if its status is Ready, Hold, Finished, Error, or End and it is not actually running. Do not select delete for a job that is currently running. If you attempt to delete any jobs that are currently running, the screen displays an error message. Deleting a job also automatically deletes all generated reports for that job that would also be available under the Document Management (My Docs) screen; however, it does not delete forms that are available at the Forms Management (My Forms) screen.
Route one or more jobs to a different queue	If the job is currently ready for processing (its status is Ready) or is hold (its status is Hold) you can route it to a different queue by: Selecting the checkbox to the left of the job. Selecting a different queue from the Output Queue drop-down list at the top of the screen. Selecting <- Route Job at the top of the screen. Why route? You might want to route a job to a different queue to expedite processing (for example, if another job is currently running in the job’s default queue, and the queue is single-threaded, meaning that only one job at a time can run in that queue at a time).
Display additional information about a job or advance to a different screen	Note: If you advance to a different screen and then return, your filter entries are not retained. For example, if you are currently filtering on a specific queue, and you advance to the Document Management (My Docs) screen and return, the Queue column no longer filters on that queue.
Review the log for a job	Click Log file for a job to display its log. Note: A User Rank of 1 is required in order for the user to display the contents in log contents, including the logs written for the user’s own submitted jobs. Otherwise, the window displays a message: Not Available.
Display the server where a user is logged in, or display the command used to execute a job	Move your cursor over the Action icon to the left of the job entry. The Command field displays: User interactive sessions: the name and IP address of the server where the user is logged in. For example, a Command of OMS-srv/123.456.789.123 indicates that the user is logged into Order Administration on the OMS-srv server, which has an IP address of 123.456.789.123. Batch or submitted jobs: the command executed for the job, such as CALL PGM(flr2012 ) PARM(' ' x'003F' x'00055F' 'N').
Review, and optionally print, reports generated by a job	Click the reports icon () next to a job to advance to the Document Management Screen, where the reports generated by the selected job are listed. From this screen, you can print the report using the printers currently available to your local PC. Note: Forms, such as pick slips, purchase orders, or checks, are available from the Forms Management Screen rather than the Document Management Screen.
Display information about Order Administration	Select About.
Advance to the Forms Management Screen	Select My Forms.
Advance to the Document Management Screen	Select My Docs.
Advance to the Advanced Commands screen.	Select Advanced commands. This option is available only for users that have authority to the Advanced Commands option.
Return to the previous Order Administration screen	Select Exit.

Jobs Troubleshooting

Question	Possible Answer(s)
Why are the background async jobs not starting correctly?	See Troubleshooting the Async Jobs.
Why can’t I change the status of an async job?	When the async jobs in the Background Job Control (MBJC) menu option are active, the system periodically checks the status of each async job, and changes the status to RUN, if necessary. For example, if the ORDR_ASYNC job is active and you end it at this screen, the system automatically changes the status of the job back to RUN. To start or stop the async jobs, use the Background Job Control (MBJC) menu option. See Working with the CNTL_ASYNC Job. Also, to correct jobs whose statuses are incorrect, use the JOBCLN periodic function. See Using the JOBCLN Function to Resolve Job Status Across Servers for more information.
Why do I receive the error Function key not allowed when I press F5 to refresh the Job Management screen?	To refresh the Job Management screen, click Refresh.
Why does a submitted job go into Message status?	Typically, this occurs because someone has stopped and restarted Order Administration. In this case, use the JOBCLN periodic function to resolve. If this is not the reason, check the following logs to determine other possible reasons, looking for messages that were written to the log at the time when the job went into Message status. For example, an error such as `out of memory, program not found, or null pointer` might help you determine the cause of the problem. The jobs and the activities they track are: CWDirect Log: General application processing. MQ Log: XML and transactional message processing and message contents. Application Log: Order Administration application processing. Response Log: Jobs that require user intervention in order to proceed, such as authorizations and deposits, and stored value card activations, balance inquiries and authorization reversals. Trace Log: Internal activity related to Order Administration application processing. Manifest Log: Manifest processing. To Reset the Job Status Use the Display Active Batch Jobs Screen to determine if the job is actively running. To fix: If the job status is inconsistent, run the JOBCLN periodic function. See Using the JOBCLN Function to Resolve Job Status Across Servers for more information.
Are job entries automatically deleted?	Jobs older than the oms.job.purge.retain.days property in Working with Admin Properties (CPRP) are deleted when you restart Order Administration.
How can I delete a job if it’s not actually running, regardless of the displayed status?	If the screen displays an error message when you attempt to delete a job, but the job is not actually running, use the JOBCLN function, as described above.
After I deleted all of the documents for a submitted job, why does the job remain on the My Jobs screen?	Deleting all of the output for a submitted job does not delete the submitted job. You need to use the Remove option to remove the job. Note: You should remove a submitted job if it is in finished (FIN) status. Evaluate the status of a job that is in an error (ERR) or message (MSG) status before removing it.
Does deleting a job entry delete its associated documents?	Deleting a job entry automatically deletes all generated reports for that job that would also be available under the Document Management (My Docs) screen; however, it does not delete forms that are available at the Forms Management (My Forms) screen.
How can I review all of the jobs for a particular job queue?	On the Job Management screen, clear the User Name field, select the job queue from the Queue drop down box and click Filter. Note: This option is available only if you have the required authority based on your user control record. Contact your Order Administration representative if you need information on configuring user control records.
Why can’t I see jobs submitted by all users?	If your user control record does not have All job authority selected, you cannot review jobs submitted by other users. Contact your Order Administration representative if you need information on configuring user control records.
Can I choose the job queue the system uses to process a job?	When a job is first submitted to the job queue, the system automatically chooses which job queue to use to process the job, based on the type of job submitted. However, if the job has not yet processed (its status is Ready), you can route it to a different job queue by: Selecting the checkbox to the left of the job. Selecting the job queue from the drop-down box next to the <- Route Job button. Selecting Route Job. This option is useful if, for example, a large job is currently active in QBATCH, and you would like to run a report job in a separate job queue so it will process quickly.
How can I review and query batch jobs that have run?	Reviewing Job History The Display Job History (DJHY) screen displays the Job History table. You can review the data and search by server, date range, job queue, and/or job name. The Job History table in the Order Administration database lists batch jobs that have run, including batch jobs that have been removed from the Job Management Screen. These records remain in this table up to the specified purge days. The fields in this table are: Job #: The system-assigned identification number to track the job. Job Name: The name of the job, such as PICK_OUT or BILL_ASYNC. Start Date: The date the job was started. Start Time: The time the job was started. End Date: The date the job finished. Set to 0 if the job did not end. End Time: The time the job finished. Set to 0 if the job did not end. Submitted By: The user ID of the person who submitted the job. Job Queue: The job queue where the job ran, such as QSYSNOMAX or ASYNC. Server: The name and IP address of the Order Administration application server where the job ran. Purging Records in the Job History Table The oms.job.history.purge.retain.days property setting in Working with Admin Properties (CPRP) defines how long to retain a batch job in the Job History table before the system purges it automatically based on the job’s End date. The default setting is 30 days. The PURGEJH periodic function purges all records in the JOB_RUN_HISTORY table including related record in JENASYSJOB where the End Date is empty AND the job is NOT running. If the job is done and the last record didn't get any End Date populated, purge that record and any previous related records to that job. If a record is found without an End Date is not running, use the Start Date and only if that is greater than the number of days configured in oms.job.history.purge.retain.days property to determine if it will be purged.
Why can’t I see the contents of the log for a job I submitted?	A User Rank of 1 is required in order to display the contents in the Log column, including the logs written for your own submitted jobs. Otherwise, the window displays a message: Not Available.