Jobs executed in the background [UNIX version]
When described to be executed as a job in the background, the job will be terminated without waiting for the background program to be completed.
Recognition of job end [Windows version]
Not only those applications registered with Systemwalker Operation Manager but all the other applications under registered applications are monitored as single jobs. For this reason, a job is recognized as having completed when the applications registered with Systemwalker Operation Manager and all the other applications under those registered applications have terminated.
For example, if Application A, which is registered with Systemwalker Operation Manager, starts a resident application called Application B and then Application A terminates, the job will not be recognized as having completed until Application B has terminated.
Example
Use the following method to avoid the need to wait for applications started from registered applications to finish:
Use the application startup command EXECASVR.EXE.
The EXECASVR.EXE application startup command does not wait for termination of the started application. For the EXECASVR.EXE application startup command, refer to the Systemwalker Operation Manager Reference Guide.
Applications for printing [Windows version]
When a printing application created with PowerCOBOL or VisualBASIC is executed as a job by Systemwalker Operation Manager and when the destination printer is set as the standard printer in the print manager, note the followings. This includes situations where the procedure for selecting a destination printer depends on the specifications of the development language function, instruction, statement or API used in the application print processing.
Log on to Windows locally with the Systemwalker MpMjes service logon account. In the Options sheet in the Define Operating Information window, if the Execute jobs under the respective job owner's authority check box is selected, log on locally to the Windows system using the job owner's user ID.
In the application, print using function, instruction, statement or API not using the standard printer registered in the print manager.
Using network drives [Windows version]
It is recommended that all resources to be used by applications started from Systemwalker Operation Manager be placed on the local drive. However, refer to the following notes when the use of resources on network drives is unavoidable:
Use the UNC path so as to enable the application to reference the network path.
For example, suppose there is a job which displays the list of directories on the network drive "z:". As the condition to execute the job, make settings for network connection by setting the computer name to "remote" and the shared name to "share" for the drive "z:". An example of using the UNC path in that job command string is as follows.
Example of drive "z": cmd.exe /c dir z:\ Example of UNC path: cmd.exe /c dir \\remote\share
For an application that cannot use the UNC path instead of the drive character, start the application from a batch file and add the command for network connection/disconnection at the beginning and at the end of the batch file.
Network connection: net use z: \\remote\share Network disconnection: net use z: /delete
While this batch file is being executed as a job, other jobs cannot assign and use the same drive character (drive "z:" in the example above) to other network paths.
Also, even if another job is connected to the network, you cannot assign the same drive letter to a job that you are about to start.
Current directory of jobs [Windows version]
When "Copy the script specified when registering jobs before execution" is checked in the Backward compatibility sheet of the Define Operation Information window, the current directory of the jobs started from Systemwalker Operation Manager is set as follows.
Systemwalker Operation Manager installation directory |
Queue name: queue name at job submission
Job number: number assigned at job submission
To specify a certain path as the current directory, carry out the following operations.
Create the following batch files and start them from Systemwalker Operation Manager. In the batch file, the current directory is changed to c:\temp by the cd command, and then the application is started.
rem Change the current directory. |
appl.exe: User application
Starting Systemwalker Operation Manager
If the commands that involve starting Systemwalker Operation Manager are executed, the operations of Systemwalker Operation Manager and Systemwalker Centric Manager cannot be guaranteed. For details, see "A.5.14 Commands that Should Not Be Executed as Jobs."
