Regarding: CPF37AA - Information related to user profiles cannot be
saved.

IBM has suggested that clearing such locks (not being QEDD specific) can
be done by
CALL QSRCLINX

A google search on QSRCLINX shows an old (unsupported release) cover
letter with this interesting information:

<snip>
If this PTF is applied, and the problem is caused by entries that are
left in the internal index QSR.SRLOCK, enter the following command to
clear the index.

CALL QSRCLINX

The index will be cleared if no save operations are in progress, with
the result:
MSGCPC3725 Save file QSR.SRLOCK in library QSYS cleared.

If another job is performing a save operation, the index will not be
cleared, and the result will be:
MSGMCH5804 Lock space location operation not satisfied in specified
time interval.
MSGCPF385B Object in use.
MSGCPF3812 Save file QSR.SRLOCK in QSYS in use.

MSGMCH5804 will identify a job that is performing a save operation.
MSGCPF385B will identify an object that is being saved.
</snip>


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.