When attempting to run an ACL, using /S sessionid ACLprog to start an ACL program I am getting an error : CAUSE: A10 IS AN UNKNOWN SESSION-ID

Products

• TPX - Session Management

Issue/Introduction

 When using the /S command to start an ACL program from the TPX main menu using :

/S sessionid ACLprog

The following error is displayed, if the session is not active:

 MSGID: TEN0001 
   CAUSE: A10      IS AN UNKNOWN SESSION-ID 
   TO PROCEED, EITHER - 
   1. HIT ENTER - TO GET RECONNECTED 
   2. RE-ENTER THE COMMAND: 
   ===> 

If the session is active, it displays "ACL" under STATUS, for the session, and when one enters the session, the terminal locks up. Hitting the reset key frees up the terminal but whatever I try after that locks up the terminal and I have to break out of the session with the ATTN key.

Then I can deactivate the session and everything is back to normal.

Below is the ACL program being used :

 ********************************************** 
 OPTION    FLOW,OFF  *** DEBUG ** 
 OPTION    TERM,OFF  *** DEBUG ** 
 WINP                WAIT FOR INPUT SEARCH   ' ENTER NEXT TASK CODE:' 
 KEY        'CSD800' 
 ENTER 
 STOP 

A simple ACL program, that keys in a task code so I get a menu in some application, but it does not seem to work.

 

 

Resolution

There are 2 aspects of running the ACL as described:

1. When application is ACTIVE
   
   
2. Then application is INACTIVE.

When an ACL is started from the command line in TPX menu with:

/S sessionid ACLprog

and the application is INACTIVE, you will get an error panel displaying,

CAUSE: A10 IS AN UNKNOWN SESSION-ID.

This is normal and how an ACL script should work.

If the session is ACTIVE and ACL starts with a WINP verb, as detailed in the example above, this forces a 'wait for INPUT' from the application, however, the session is already established and hence no input is forthcoming which results in a 'hang' status.

WINP can only be used in a startup ACL defined on application/session level.

Do not start an ACL with WINP as the first statement, using the /S command. This will result in a terminal lock or hang (input inhibited) condition.