Skip to main content

Process Manager 9.1 jobs are in Waiting state

Issue:

We have several jobs on waiting status in IBM Platform Process Manager 9.1.

Solution:

IBM support team suggested us to add the parameter below to avoid creating new login shell for the submission users for each job triggered from PPM side:

JS_SU_NEW_LOGIN=false

You can find this configuration in js.conf file located at /pm/conf.

bash-4.1$ grep JS_SU_NEW_LOGIN js.conf
JS_SU_NEW_LOGIN=false
# Default is JS_SU_NEW_LOGIN=true

Side effects:

There is one downside of using this parameter, that it will not get user's $HOME/.profile sourced so any environment variables set there will not be seen in job execution environment. PPM submission to LSF is by default using "su - username -c 'command' " and the dash here implies user login is invoked souring the $HOME/.profile file. When we added JS_SU_NEW_LOGIN=false to our Test environment, it broke some jobs for user that depended on variables defined in user $HOME/.profile. We resolved it by sourcing those variables in application scripts.

Other symptoms for this issue:

PPM try to send the job to LSF but exits with code 125.
This code is related to when "su " command fails because of a shell issue.

Other solutions tried but failed:

Moving the flow instance from active to finished:
$ cd /pm/work/storage/flow_instance_storage/active/
$ ls -l 387532.dat
rw-r--r--. 1 sas sas 6354 Feb 16 00:00 387532.dat
$mv 387532.dat ../finished/

Comments

Post a Comment

Popular posts from this blog

Starting Gemfire in SAS

Gemfire is available in both Compute and Mid. The default port is 41415. If you have many gemfire, you may have port numbers incremented by 1, for example: 41416. Gemfire is located under Web. <SASCONFIG>/Web/gemfire. To Start: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh start To check Status: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh status To stop: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh stop If it doesn;t start check port number is occupied by any other process. lsof -i tcp:41415 If you only have one instance then 41415 will be default. If you have Lev2 then it will be 41416
Post a Comment
Read more

SAS 9.4 server startup order

In Linux / Unix OS we normally use sas.servers to start the services. The script in the background follows an order to start the services. It is important to follow the order to run the services correctly. In this post we can see what is the order to start / stop and to generate the sas.servers script. It is not really required to memorize the order because SAS provide an utility to create the sas.servers script automatically which will start / stop the service in order. Starting order SAS Metadata server Olap server SAS object spawner SAS / SHARE server SAS / connect spawner SAP table server SAP remote services SAS deployment tester server Stopping will be the same in reverse. How to create sas.server script? We can create sas.server script by using generate_boot_script.sh. if you have made any changes to your environment like adding a new server or spawner we can use the script to generate new sas.server. You can use the script even if you have removed the spanner o...
Post a Comment
Read more

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...
2 comments
Read more