Success at last! I had not included the filedef for LPRXFORM in RSCS's profile gcs. Once I did that it worked beautifully. I was never able to get the trace function working though. That may come in handy in the future, so any advice on that would be welcome. Also, the ability to dynamically refresh the LPRXFORM CONFIG would be useful because this attempt was only one of several printers with several features to support.
Thanks for all the help and patience.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Bob Henry * Mgr., Rochester IT * SunGard Higher Education * 3000 Ridge Rd. E., Rochester, NY 14622
Tel 585-339-2366 * Mobile 585-330-5240 * Fax 610-578-3014 * [EMAIL PROTECTED] * www.sungardhe.com
CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you
| Bob Henry <[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System <[email protected]> 03/21/2006 10:44 AM
|
|
Sorry to seem so helpless, but, I defined EXIT 0 & 1 in RSCS CONFIG to initiate LPRXFORM exit. I created LPRXFORM CONFIG on RSCS 401 disk (accessible to RSCS at startup). I included PSCRIPT form entry with:
FORM=PSCRIPT
FORMSUB=P-SCRIPT
PREFIX=2521
PREFIX=50532D41646F62650D0A
PREFIX=7374617475736469637420626567696E2066616C736520
PREFIX=7365746475706C65786D6F646520302073657470617065
PREFIX=727472617920656E640D0A
PREFIX=FF04
PREFIX=2521
PREFIX=50532D41646F62650D0A
PREFIX=7374617475736469637420626567696E2066616C736520
PREFIX=7365746475706C65786D6F646520302073657470617065
PREFIX=727472617920656E640D0A
My link definition includes SYS=YES to invoke LPRXFORM exit:
sm rscs q link name roc815wp show parmf
Ready; T=0.01/0.01 10:38:35
Full Parm Text
EXIT=LPRXPSE ITO=0 SEC=NO HOST=149.24.xx.xx PRINTER=RAW USER=YES SYS=YES
1 link found
I'm sending PS formatted file from z/OS to link ROC815WP with form name PSCRIPT but still don't seem to be able to get it to kick into PS mode.
I have a couple of questions:
1) I'm trying to activate a trace on ROC815WP to see what is sent but when I enter TRACE ROC815WP I get "DMTCMY303E Link ROC815WP is not active". How do I start/stop/display a trace on that link?
2) If I want to make changes to the LPRXFORM CONFIG, can it be refreshed dynamically or do I have to stop/start RSCS?
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Bob Henry * Mgr., Rochester IT * SunGard Higher Education * 3000 Ridge Rd. E., Rochester, NY 14622
Tel 585-339-2366 * Mobile 585-330-5240 * Fax 610-578-3014 * [EMAIL PROTECTED] * www.sungardhe.com
CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you
| "Les Geer (607-429-3580)"
<[EMAIL PROTECTED]> Sent by: The IBM z/VM Operating System <[email protected]> 03/20/2006 04:32 PM
|
|
>Yes, I'm sending output to RSCS via SNANJE so I don't need the LPD. I can
>separate the files (JES output components) and assign form names to each.
>I direct the PS output to a specific RSCS link name via the JES DEST name
>but it doesn't pick it up as a PS file. From what I can tell, there's no
>%!PS command in the file. Does that need to be supplied by the "PREFIX"
>parm in the LPRXPSE parm?
There is no %!PS in the first four bytes of the file, even in ASCII?
Or %! in the first two?
The printer usually keys of this to tell whether to be in postscript
or PCL interpretive mode.
You should trace the RSCS link to see what RSCS is actually sending
down. To ensure the form you are supplying on the job card is
being seen by LPRXPSE and the file is sent as is in binary.
Best Regards,
Les Geer
IBM z/VM and Linux Development
