Re: Problems with WRKQRY command Invoked from BPCS Menu

[Al Mac <macwheel99@xxxxxxxxxxx>]

Be sure to check security for people who access BPCS from a PC since they 
have access much more powerful than command line, and also make sure they 
are able to use that power effectively ... for example, SQL/400 commands 
can be in Excel cells to get latest BPCS data at the time of opening the 
spreadsheet.  (This was topic at one of our user group meetings.)

This OVRPRTF must be a standard addition for some version of BPCS ... how 
do you compile the CL program that has WRKQRY in it?  Do you use the IBM 
PDM 14 or do you use one of the custom BPCS compilers that adds lines of 
code that may not be desired in this case?

We have on a BPCS menu a RUNQRY of the query definition of your choice, and 
access to a standard query that lists all queries alphabetically by their 
description, thanks to a nitely replacement of *OUTFILE directory.  We also 
have on a menu a RUNQRY *N dump of the BPCS file of your choice for 
selective dumps to find specific records not showing up throudh standard 
inquiry, because they messed up somehow.

This is because we want our users to be able to run any query definition 
without changing or deleting query definitions until they have had relevant 
training in query creation and management ... otherwise high risk someone 
will change some query to the detriment of other people using it.

Most popularly used queries also end up on BPCS menus in their individual 
CL programs.

> Hello Everybody,
>
> I am trying to eliminate the need for BPCS end-users to access the WRKQRY 
> command from the iSeries (AS/400) command-line. I need to have their 
> AS/400 user profiles set so that 'Limit Capabilities' is set to '*YES'. 
> For this I created a custom CL program that simply has WRKQRY command in 
> it. I stuck this CL program in a general purpose BPCS menu that is 
> available to all BPCS end users. However, when they access their queries 
> through the menu option that I set up, their reports are all messed up. 
> The outputs get truncated sometimes, or their run-time print settings 
> (such as specific printer to print to) that they specify in the query 
> itself at run-time is not honoured. I called up IBM software help-desk and 
> reported the problem. Based on their suggestion, I sent them trace and 
> debug logs by invoking WRKQRY both ways (i.e. via command line and via 
> BPCS menu). The job log showed the following override command that was in 
> the standard BPCS CL program:
>
> -----------------------------------------------------------------------------------------------------------------------------
> OVRPRTF FILE(*PRTF) PAGESIZE(66) LPI(6) CPI(10)
>                 OVRFLW(59) OUTQ(BPCSUSR64/BPCSOUTQ) FORMTYPE('*STD') 
> COPIES(01)
>                 SCHEDULE(*FILEEND) HOLD('*YES') SAVE('*NO') OUTPTY('5')
> -----------------------------------------------------------------------------------------------------------------------------
>
> Apparently, this override was messing up the WRKQRY settings when invoked 
> via BPCS menu. Hence I added the DLTOVR FILE (*PRTF) command in my CL 
> program just before the WRKQRY command and then tested it. However, it did 
> not seem to make a difference. Any ideas, anybody?
>
> Thanks in Advance!
>
> S.R. VenuGopal,
> Programming Manager,
> Information Technology,
> Haynes International, Inc,
> Phone: (765) 456-6770
> E-mail: vgopal@xxxxxxxxxxxxxx

-
Al Macintyre  http://www.ryze.com/go/Al9Mac
BPCS/400 Computer Janitor ... see
http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html