MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2014

Re: CPF5090 happening with annoying frequency



fixed

CRPence wrote:
As I noted in another reply [though sometimes I wonder if anyone ever
sees or reads any of my replies; or, I suppose, people are just too
time-constrained to read stream-of-consciousness replies over some
simplistic bullet-point memos that must only *solve* their dilemma
instead of including any edification per various related details
offered, or worse, dismissing any reply that inquires more about their
particular scenario to clarify some details], if the Unique AccPth of
the LFM is required to be valid, then just like the CPF5090 suggests in
the "Recovery" section, first *OPEN* that LFM with keyed access *before*
opening the PFM with an UPDate capability; e.g. OPNDBF &7/&6 MBR(&8)
OPTION(*INP) ACCPTH(*FILE)

So, if I currently have (names changed to protect the innocent, with the specified target library in &LIBNAME):

> RSTOBJ OBJ(*ALL) SAVLIB(APPLIB) DEV(*SAVF) +
> OBJTYPE(*PGM *FILE) SAVF(UPDSAVF) +
> RSTLIB(&LIBNAME)
> CALL POPULATE

and the only unique keys are on PHYSICAL and LOGICAL01, then inserting

> OPNDBF FILE(&LIBNAME/PHYSICAL) OPTION(*INP)
> CLOF OPNID(PHYSICAL)
> OPNDBF FILE(&LIBNAME/LOGICAL01) OPTION(*INP)
> CLOF OPNID(LOGICAL01)

between the RSTOBJ and the CALL POPULATE will solve my problem?

--
JHHL





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact