Re: Programmatically disable SysReq key

Finucci,

In the user profile there is a value for attention (SysReq) program.

Ours is set for *SYSVAL and that points to IBM's ASSIST menu.

I'm not connected to an AS/400 now, but there may be a value of *NONE.  If not,
you could write a CL program that just sends back a "key not valid" message and
point to that program.

Now, if you are talking about a user doing a ALT/SYSRQS and starting a second
signon session at the same job (user/job/job# combination that is displayed by
WRKACTJOB + F14), that's a different animal.

Now we are talking about shared/locked objects.

I have users that will run multiple sessions to perform separate tasks, like
"add an accounting entry", and in another signon(same user, different
job(workstation), different job#) session they have the "edit an accounting
entry" program running.  Most people just know that they made a mistake right
after they pressed ENTER.  So they swap to the EDIT session to correct their
mistake.

Then there are the dual session users (S/36) that have the ENTRY program in one
side of the coin and the EDIT session on the flip side. Same user, same
job(workstation), different job#.

Under the S/36 OCL it was determined by // IF INQUIRY-YES statement.

What we did was attempt an exclusive lock. If it failed, sent a message back to
the user (S/36 habit) to F3 their other session.  (a CLRPFM on the batch file
would fail if the file was still open)

AFAIK, there is no system level value to prevent someone from starting a duel
session.  Maybe in their job description or class?


hth

Finucci Domenico wrote:
>
> Good morning, sirs. Is it possible to programmaticaly disable SysReq key ?
> This is to avoid object locking during critical operations.