Before You Begin
This 20-minute tutorial shows you how to run, view, resubmit, and move jobs in a virtual batch host environment with virtual batch queues enabled.
Background
Virtual batch queues will enable EnterpriseOne to meet cloud elasticity needs for batch processing. By using a virtual host name, you can tie multiple EnterpriseOne batch processing servers to that virtual host name to facilitate simple scaling of EnterpriseOne batch processing. For example, a job submitted to QBATCH on one enterprise server could be processed by any physical node on that virtual host.
What Do You Need?
You must have completed the following tasks:
- All servers must be on Tools Release 9.2.5 or higher and the latest Tools ESU must have been applied.
- All servers used in a batch cloud must be on the same operating system, database type, and on the same port.
- All servers used in a batch cloud must have the File in Database enabled.
- All servers used in a batch cloud must share the same server map, SY or SVM, and packages.
- Required print queues must be set up identically.
- Security servers must have been federated to accept the same tokens.
- Unused columns with obsolete data must be cleaned from F986110.
Submitting
Jobs and Viewing Output
- From the Batch Versions – Work with Batch Versions – Available Versions form, select the version you created in the previous OBE and click OK to submit the job.
- Click the Data Selection checkbox.
- On the Batch Versions – Version Prompting form, select Advanced from the Form menu.
- On the Batch Versions – Advanced Version Prompting form, select the Override Job Queue check box and then click OK.
- Click Submit.
- Choose QBatch 01 as the override Queue from the list of all queues on all hosts that are part of the virtual host and click OK.
- Set your Data Selection as follows:
- Left Operand = Fiscal Date Pattern (F0008) (DTPN) [BC]
- Comparison = is equal to
- Right Operand = Select Literal from the dropdown, enter J as the literal value, and click OK.
- Click OK.
- On the Printer Selection form, click OK.
- Navigate to the shortcut wsj.
- Click View Output in the grid row for the job you have submitted.
- In the Work With Server Jobs form, scroll to the right to see the Host and Actual Host columns.
- Resubmit the job a few times until the submitted job runs on a different actual host from your first run. When you achieve this result, the screen should display information similar to this:




Note that when you override the queue for a VBQ host, you are only picking a queue name, and not that specific server. The server part of the line is not used by the submission process except to ensure you see all possible available places the job could run.

Your version has been submitted to the specified queue.

The system will download the report and can open it in your system PDF viewer.


In this example, the job ran on jdeent1-2, which is used as an actual server as part of the vbqcloud virtual host.
When a host is not a virtual host, both the Host and Virtual Host columns will have the same actual host name.

Resubmitting
Jobs
In this task, you will use the new Form exit Resubmit Jobs in the Work With Server Jobs application to resubmit your version of R0008P to the Active Queue which you created in Lesson 1 , and then view the output after your version is processed. You will resubmit a job with and without setting the Data Selection values to verify that the submitted override values from the original submission applies to the new submission.
- From the Work With Server Jobs form, select Resubmit Jobs from the Form menu.
- On the Submitted Reports – Resubmit Jobs form, select Done in the Job Status section and then click Search.
- To resubmit a job to a virtual server, click the Resubmit checkbox corresponding to the job you want to resubmit.
- To change the server, click the New Host field and either type or use the QBE to select a different server. For this task, as the job is being run on the same host, press the Tab key to skip the New Host field.
- To change the queue, click the New Queue field and either type or use the QBE to select a different queue. For this task, as the job is being run on the same queue, press the TAB key to skip the New Queue field.
- Click OK to resubmit the job.
- Click Search in the Submitted Reports application to see the newly resubmitted job.
- Click View Output in the grid row for the resubmitted report.
- View the PDF file and note that the resubmission preserved the Data Selection from the previous run:





Note that the Host and Actual Host columns are updated. Verify whether your resubmitted job was processed on the same or a different actual host. Repeat the resubmission process (steps 1–6) one or more times if you want to process the job on a different host.



NOTE: Synchronous Report Interconnect jobs are not permitted to be resubmitted, as each job ran as a subreport inside the context of another parent report. These jobs will not show up as selection options in the Resubmit Jobs form.
Moving
Jobs
In this task, you will use Batch Version to submit your version of R0008P to an inactive queue on a different server, jdeent1, then use the newly added Form exit Move Jobs in the P986110B – Work With Server Jobs application to move a version of R0008P to the vbqcloud server’s active queue which you created in the first OBE of this Learning Path, and finally view the output when processing of the R0008P version is complete. You will repeat this task but will hold the job before moving it to the other server and queue. After the move, you will release the job, and see the job being processed on a different server than the one it was submitted to.
- From the Fast Path, run application BV – Batch Versions.
- From the Batch Versions – Work with Batch Versions – Available Versions form, select the version you created in the previous exercise and click OK to submit the job.
- On the Batch Versions – Version Prompting form, select Advanced from the Form menu.
- On the Batch Versions – Advanced Version Prompting form,
select the following check boxes and then click OK.
- Override Location
- Override Job Queue
- Click Submit.
- Select jdeent1 as the override location and click OK.
- On the Batch Versions – Job Queue Search & Select form, select RBATCH (note that this job queue is not active) and click OK.
- On the Printer Selection form, click OK.
- Navigate to the shortcut wsj.
- Scroll to the right of the Submitted Reports – Submitted Job Search page and find the Host and Actual Host columns.
- Now, to move the job to the vbqcloud server, select Move Jobs from the Form menu.
- On the Submitted Reports - Move Jobs form, select Wait from the Job Status section and click Find.
- To move a job to the virtual server, select the check box in the Move column next to the job you want to move.
- To move the job to a different server, click the New Host field and type or use the Visual Assist to select jdeent1-2 or jdeent1-3 as the server.
- To change the queue, click the New Queue field and type or use the Visual Assist to select your custom queue and then click OK to move the job.
- Select Find to view newly moved jobs.
- Click View Output to view the report of the moved job.
- Repeat the above steps to submit another R0008P with the version TRAIN01. Remember to use the Advanced option in the Form menu to be able to override the server to jdeent1 and job queue to RBATCH to get another job on jdeent1 in the waiting status.
- On the Submitted Reports – Submitted Job Search form, select the job that is in the waiting status and then from the Row exit select Hold to move the job to a held status.
- Now you will move the job to the vbqcloud server using your custom queue.
- From the Form exit, select Move Jobs.
- On the Submitted Reports - Move Jobs form, note that the Hold check box is already selected. Click Search.
- To move a job to the virtual server, first select the check box in the Move column next to the job that you want to resubmit.
- To move the job to a different server, click the New Host field and type or use the Visual Assist to select jdeent1-2 or jdeent1-3 as the server.
- To change the queue, click the New Queue field and type or use the Visual Assist to select your custom queue. Then, click Ok to move the job.
- Click Search now that you are back in the Submitted Reports application to see the newly moved (and still held) job.
- On the Submitted Reports – Submitted Job Search form, select the job that is in the waiting status and then click the Row exit and select Release to release the job from the W (waiting) status.
- Click Search in the Submitted Reports application. You may see the job move from W (Waiting) to S to P to D (Done) as it runs, but you are likely to see only one of the intermediate statuses . Repeat until the job is in the Done status, and again view the output.





Note that the status of the job you submitted is W (Waiting).

Note that the server is jdeent1 and the actual host has not been assigned yet, as the job is waiting.






Note that a new job number was assigned to the job when it was moved to the new server. Also note that the Host and Actual Host columns are updated. Verify on which actual host this job was processed. Repeat the submission process to move the job to the inactive queue and move the job again if you want to run the job on a different host.


The report should look like this:










In this OBE, you learned how to submit a job to a Waiting status on an inactive queue, optionally holding the job for processing later. You then learned how to move the job in the Waiting and Held statuses to another queue that was active, and, if Held, release the job to run on the other server and in the other queue.