Re: locked record

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Another good idea comes back - passing a data structure as a parm.

Now I can have my service program back.

Bless you.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Steve Landess" <steve_landess@hotmail.com>
Sent by: midrange-l-admin@midrange.com
10/10/2002 03:10 PM
Please respond to midrange-l


        To:     <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        Re: locked record


Rob -
I gleaned this from a JDE program...

What JDE does is IF an error occurs in the RPG program on a file
operation,
they call a program (P98RLCK) and pass the PSDS to it.

P98RLCK determines if the RPG status code is either '01218' or '01299'. If
so, it pops up a window that displays the 'Record 1 in use by job
955737/USERID/JOBNAME.' message so that the interactive user can see who
has
the record lock.


----- Original Message -----
From: <rob@dekko.com>
To: <midrange-l@midrange.com>
Sent: Thursday, October 10, 2002 3:01 PM
Subject: Re: locked record


This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Ah, there's the caveat, DIRECTLY.  So if I had a routine in a service
program to strip apart the message I would be hosed.  As much as I am
enamored with service programs, I can accept this.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Steve Landess" <steve_landess@hotmail.com>
Sent by: midrange-l-admin@midrange.com
10/10/2002 02:47 PM
Please respond to midrange-l


        To:     <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        Re: locked record


If you are trying to make this determination DIRECTLY in an RPG program,
it
is fairly simple:

1) Code an error indicator on the operation code that you are using to
read
the record (CHAIN, READ, READE, etc.).

2) AFTER executing the file operation, if the error indicator is *ON,
there
are a couple of fields in the Program Status Data Structure that have the
information that you are looking for:

Positions 91 - 170 will contain a message that looks like 'Record 1 in use
by job 955737/USERID/JOBNAME.'
Positions 201 - 208 will have the name of the file where the error
occurred
(the file name as it is known in the RPG program)
Positions 209 - 213 will have the RPG status code of either '01218'
(Record
already locked) or '01299' (Other I/O error occurred).  You can find the
status codes documented in the RPG/400 Reference

I haven't tried this in an RPGLE program, but I feel quite confident in
saving that it will work the same way when using the 'E' extender and the
%ERROR BIF to check for the error condition.

Hope this helps...


----- Original Message -----
From: <kmskeele@mail.volusia.k12.fl.us>
To: <midrange-l@midrange.com>
Sent: Thursday, October 10, 2002 9:10 AM
Subject: locked record


A somewhat newbie question.... Is there a way to display the user id that
has a specific
record locked for update ?



**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.