Re: SQL - opening a cursor over a production file while UpdProd(*No)

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

A new-to-me trick qua technique with debug is to enter SET in the debug 
panel command line, right after you run STRDBG - this lets you set 
update production and a couple other things - just in case you forget on 
the command. Something I just learned in the last year or so - very cool!!

Vern

On 4/7/2011 7:01 AM, Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx wrote:
> Either turn off debugging or specify UPDPROD(*YES)?
>
> Thanks,
> Tommy Holden
>
>
>
> From:   Kurt Anderson<kurt.anderson@xxxxxxxxxxxxxx>
> To:     "'Midrange Systems Technical Discussion'
> (midrange-l@xxxxxxxxxxxx)"<midrange-l@xxxxxxxxxxxx>
> Date:   04/06/2011 05:05 PM
> Subject:        SQL - opening a cursor over a production file while
> UpdProd(*No)
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> I have a Declare statement with the SQL Statement "Select * from
> CalTypTIDP."  However, when I issue the Open Cursor over a production file
> while in debug mode, I get an error:
> CPF4203 - Member CALTYPTIDP cannot be opened while UPDPROD(*NO).
>
> What's happening is we have a file encapsulated service program that will
> "do everything" to a file (read, write, update, delete, etc).  When
> running with native I/O, the service program would not open the file if in
> debug mode with UPDPROD(*NO) even if the caller was only ever going to
> read the file.  What I'm shooting for is to let the service program open,
> but to monitor for any failed update/write/delete/etc I/O functions.  I
> was not expecting an open cursor to fail when "for update" wasn't
> specified on the declared statement.  The reason why I was looking for
> this type of functionality is that every new file encapsulated service
> program is requiring the programmer to copy data to their own library for
> testing when we've been using the live data for testing all along - which
> results in the data not always getting copied for a test.  And I don't
> want to exacerbate the issue with more and more service programs that
> won't open a file in debug mode.
>
> Can anyone offer any suggestions?
>
> Thanks,
> Kurt Anderson
> Sr. Programmer/Analyst