user steps away, leaving F98301LA DREAM writer file in use

Eric Lehti

VIP Member
How do you train your users?
You know the scenario where a user is in the middle of submitting a DREAM writer job, and has the DREAM writer Data selection screen up, but does not submit the job but instead, gets distracted, forgets about it and goes to lunch or to a meeting.
Others who would like to run that DREAM writer job cannot because record nnnnnnn in F98301LA is in use.
Until the first user submits the DREAM writer job, no one else can run it.
 
Great recommendation "use tough love, end his job". Sometimes that is best! For a bit of gentle user education, I have added this educational message to the I5/OS signon screen QSYS/QDSIGNON dsplay file (well, actually, a clone of QDSIGNON because we do not modify the original QDSIGNON display file. )
=====================================================
User . . . .
Password. . .[__________]

When selecting any JDE menu option that runs a DREAM writer version,
identified by video name 98302 in upper left corner of your screen,
you have an exclusive lock on that menu option until you submit the job
or back out with F3 key. Keep in mind that no one else can get to this
menu option while you have it locked.
==================================================
 
"Use tough love and end his interactive job? "

Known in Unix Land as a LART - Luser Attitude Readjustment Tool.

The real problem of course is JDE's programming. They should not hold
record locks across a 5250 write/read pair.
 
Hi Eric,

I have created a CL to create a new user. It does all of the setup on
the iSeries, enroll user, outq in the correct library, set the outq to
the outq name we use by our standards (userid *CAT prt), change the
users jobd to use this outq, remove aut and grants aut to the users jobd
and outq, changes the object owner on the putq. No need to do any
manual process.
This CL can be changed to use your libraries and naming standards. It
wa taking Cordell 30-40 minutes to add a new user to the system and
about 15 minutes to add them into JDE.

I am in the process of carrying this a step further and adding a call to
a program to create the userid in JDE and the signon list would only
have to be one entry to their main menu in the F0092 revisions screen.

There is not a need to do the action code, function key, cost center
security, command line, as it would be all based on the users
class/group (as long as you are attaching this user to a class/group
that already exists).

Jim
 
Back
Top