When a procedure is triggered by an event, the ID of the routing event and the text of the event message are available to the procedure as the EVENT_ID and EVENT_TEXT parameters, respectively. The EVENT_TEXT parameter needs to be decrypted using the B64DECODE user subroutine. The syntax is:

-SET MyEVENT_TEXT = B64DECODE('&EVENT_TEXT', 'A200');

For the following event:

(EDA13088) rejected cmrpht000089 u=baduser (userid failure)

EVENT_ID is 13068.

EVENT_TEXT is (EDA13088) rejected cmrpht000089 u=baduser (userid failure).

For undefined events, the EVENT_ID is as follows:

• Information - 20000
• Warning - 40000
• Error - 60000

Since the Scheduler now supports trusted connections, it no longer validates the DM_USERID from the scheduled job or procedure against the admin.cfg file. The Scheduler no longer needs user/password for servers running with OPSYS or LDAP security, which support trusted connections.

The only environment that still requires user/password is a Windows server with OPSYS security and with sched_run_id=user. Unless it uses IWA connections, that type of server still requires user/password. Flows for those users will be scheduled and fail if the user is not included in the admin.cfg file. Previously, the flows were marked as failed without scheduling.

Recurring flows will be scheduled and fail as many times as they are scheduled, unless sched_restart_failed is set to 0 (the default value is -1, for an unlimited number of scheduled runs). The advantage of this change is that all failures are now recorded in the etllog file. Previously, flows that failed to match an ID against the admin.cfg file did not produce any trace in the etllog file.