RE: Opening system includes

I've noticed that many communications errors or abnormal terminations cause
other problems.

If CODE crashes and I go back to the recently-used list to re-open the
member, it often opens as read-only, and subsequent used of the entry on the
RUL also open the member as read-only.  Even after I go into the iSeries and
kill the server job (WRKOBJLCK is my most popular CODE command), it still
opens in the RUL as read-only.  My conclusion is that the RUL contains a
status bit indicating read-only; I have to use the command line and the "LX"
macro to open the member in update mode.  That open replaces the read-only
entry in the RUL.

-reeve

-----Original Message-----
From: wdsci-l-admin@midrange.com [mailto:wdsci-l-admin@midrange.com]On
Behalf Of Vernon Hamberg
Sent: Tuesday, October 15, 2002 11:43 AM
To: wdsci-l@midrange.com
Subject: [WDSCI-L] Opening system includes

Got a little funky behavior today. I have member filters for the system
includes, QSYSINC/H and QSYSINC/MIH. When I open a member with LPEX, I get
an error, saying it is read-only. Well, that's true, but it's disconcerting
to have it handled this way. It looks like a hard error, then it goes ahead
and opens it read-only.

This does not happen, using the opening with CODE.

Thanks

Vern Hamberg

Would you like to see a challenging little arithmetic puzzle
that might get you or your kids or grandkids more interested
in math? Go to <http://cgi.wff-n-proof.com/MSQ-Ind/I-1E.htm>

Sillygism--

Something is better than nothing.
Nothing is better than a ham sandwich.
Ergo
Something is better than a ham sandwich.

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/wdsci-l
or email: WDSCI-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.