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

How to create library for Oracle in SAS?

In this article, you will get details about creating a new library using SAS Management Console. Here, I have provided the procedure for creating library for Oracle database. However, the steps will be same for other databases like SQL server, Teradata etc. Creating connection to Oracle database: To create library, you must first create a connection to Oracle database in your host machine. Host machine is the physical location where your SAS platform is installed. Details like Oracle database hostname/IP address and DSN/SID name is needed. Those details should be entered in tsnnames.ora file. For more details check this article Creating library in SAS Management Console: The steps for creating library for Oracle using SAS Management Console (SMC) can used for other database like SQL Server, My SQL etc. New library wizard: Expand Data Library Manager plug-in, right click on the Libraries and click New Library to start library wizard. You will be asked

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login 14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi

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 file. Us

SAS Platform Admin Blog

Search This Blog