Re: Creating multiple reports on mainframe

[Cindy Chen <sxc4@POP.CWRU.EDU>]

Steve,
       I was assuming that you ran the report from a stand alone JCL
job.  The parm member I meant is the SQRPARMS like the one you  have in
your mail.  Instead of -FDDN:SYSOUT you would have -FRPT1 -RPT2 (here RPT1
and RPT2 should match the DDNAME you have in JCL pointing to the
preallocated PDS and should match the name in your DECLARE-REPORT RPT1 in
your program).   We ended up creating one parm member which has -FP1 -FP2
-FP3 -FP4 -FP5 , and that give us the flexibility of using the same parm
member without having to recreate that for each program.  But then each of
our multiple report program need to use report name as P1, P2, etc.,  and
we don't have much choice about the report names because of the constraint
of the command line length.  if we have a program that generates only 3
reports, we would still need to define as many  (in this case, P1 - P5)
declare-report as the -F in the SQRPARMS.  Same rule applies for JCL.  ex.,
the JCL might look like :

//P1       DD DISP=SHR,DSN=PROD.UGL.REPORT(RPT01)
//P2       DD DISP=SHR,DSN=PROD.UGL.REPORT(RPT02)
//P3       DD DISP=SHR,DSN=PROD.UGL.REPORT(RPT03)
//P4       DD DUMMY
//P5       DD DUMMY

our SQR is 4.1.7.3 same as yours.  We don't have multiple report program
run from PeopleSoft , but I think you will need a special shell JCL (or
JCLs) for multiple report programs to run in MVS server.

HTH.  -Cindy
At 11:44 AM 10/3/2001 -0400, you wrote:
>Cindy,
>
>      Thank you very much for responding.  I would just like to clarify a few
>things-
>
>      -When you mention the member of your parmlib, are you referring to -
>           - the Config Manager SQR flag settings in PeopleSoft
>           - the SQRPARMS member, which in our environment looks like this -
>
>           DSN SYSTEM(DHP2)
>           RUN PROG(SQR)  -
>           PLAN(DBCALLS) -
>           LIB('SYS3.PSOFT.SQR.LOAD') -
>           PARMS('DDN:SQRIN DSN/PSOFTPRD -FDDN:SQROUT -P:HP -S -
>                 -IDDN:SQRINC( -TBZ -MDDN:MAXIN')
>           END
>
>           - something else?
>
>      - We typically run our SQR's from PeopleSoft using shell JCL, which
>defaults the print file to a DDNAME of SYSOUT.       We do have a few
>SQR's that
>we don't run from PeopleSoft.  They are run on the mainframe as stand alone
>jobs.  If        we need to use "custom" DDNAMES for the multiple reports,
>then
>I assume I will have to create a new stand         alone job, with it's
>own JCL.
>I don't see how I could do this using the shell JCL.  Is this what you had in
>mind, or am I       missing something?
>
>      Thanks again for your help.  This is the first time we have
> attempted this.
>It could be quite helpful now and in the           future.
>
>      Steve
>
>
>
>
>
>Cindy Chen <sxc4@POP.CWRU.EDU> on 10/03/2001 11:02:50 AM
>
>Please respond to sqr-users@list.iex.net
>
>To:   SQR-USERS@list.iex.net
>cc:    (bcc: Steve Rogers/North/KayBee)
>
>Subject:  Re: Creating multiple reports on mainframe
>
>
>
>Hi Steve,
>
>       You need :
>1. in the member of your parmlib, make sure you have flags:
>         -FRPT1 -FRPT2 ....
>2. then in your JCL, you will need to have ddname RPT1 and RPT2 which point
>to a pre-allocated PDS, ex.,
>       //RPT1 dd dsn=your.pds(myrpt1)...
>       //RPT2 dd dsn=your.pds(myrpt2)...
>
>HTH
>
>Cindy
>At 08:42 AM 10/3/2001 -0400, you wrote:
> >      Good morning all -
> >
> >      We are running PeopleSoft DB2 for MVS, version 7.51.  All of our
> > SQR's are
> >processed using the mainframe as our server.  I am attempting to create two
> >different reports from the same SQR.  I used the DECLARE-REPORT options
> >according to the SQR server Language Reference.  When I attempt to run the
> >SQR,
> >I am receiving the following error -
> >
> >(SQR 6002) Cannot open the printer file: DDN:SQROUT.SPF
> >(13): Improper function argument
> >
> >      It appears as if the the SQROUT DD name is automatically receiving
> > the .SPF
> >suffix, which MVS can't seem to process.
> >
> >      Does anyone know how to resolve this problem?
> >
> >      thanks,
> >      Steve