mainfram parmlib ?

[Keri Palko <keri.palko@UCDMC.UCDAVIS.EDU>]

I have another question. At this point, it looks like I'm going to have
lots of SQR questions and not many answers for anyone else. Hopefully I'll
work through my questions, learn more about SQR, and then be a resource for
others. Since it looks like I will be a frequent poster to this list, a
short introduction is in order.  My name is Keri Palko, and I work at UC
Davis Medical Center in Sacramento. We have recently installed PeopleSoft
HRMS 7.5 with MVS/DB2 (5.1) and are working on the implementation of it. My
only SQR experience is the SQL/SQR class that PeopleSoft puts on (I don't
think this is a good class). I have coded one small conversion program
(starting from another one) that I got to run on the client and the
mainframe.

Is there any kind of SQR for Mainframe book out there? The SQRIBE user
guide and language reference don't seem to be terribly MVS friendly.

When changing PeopleSoft delivered reports that use input data (as of date
from Process Scheduler, or reports using the oprid for security,...), what
do people normally do to get them to work on the mainframe? I got one
suggestion of writing an SQR before the report SQR to populate the process
request table. I thought maybe it would be easier to get rid of the read to
the process request table and just populate the variable another way (like
parms or input files). Which brings me to my next question...

What is the PARMLIB for (dd SYSIN)? It seems that all the delivered SQRs
use the NOPARMS member. Can you create a member and use it as you would use
parms in COBOL/DB2 programs? If so, can anyone tell me how to use the
member in the SQR? Would I treat it like any other input file? Open the
file, read it, assigning the data  to parm variables for the SQR?

Thanks,
Keri

PS. If anyone saw my mainframe printer question yesterday, I had a mistake.
Our mainframe printer isn't an impact printer. It's a OCE, Page Stream, LED
printer. It's still not coming out correctly.