Using APPC to Communicate with Other Systems › APPC Security › Conversation Level Security and NCL Procedure Environments

Conversation Level Security and NCL Procedure Environments

NCL procedures running in a signed-on user environment can issue allocation requests for secured transactions without specifying their user ID and password. If an NCL procedure is running in an environment that is not protected by a user ID and password signon, such as EASINET, it can only request allocation of secured transactions by specifying the USERID and PASSWORD operands in the allocation request.

For incoming attach requests the TCT security level determines the type of NCL environment in which the NCL procedure nominated to service the transaction is run. An attach request for an unsecured transaction results in the NCL procedure being started in the background server (BSVR) region.

If the request is for a secured transaction, a special APPC region is created (if none already exists) for the user. The user is signed on using normal security procedures. This happens before the transaction can be started.

Secured transactions require a signed-on environment before execution is permitted. An attempt to start such a transaction in some other environment fails with a security error return code.