No. Here are the parm statements: LINKDEFINE VA1P8 TYPE LPR FORM * AST PARM VA1P8 EXIT=LPRXPSE HOST=192.168.101.17 PRINTER=va1p8
These worked with 4.4 on the same host, no changes in the print server or firewall settings. Will try SECURE=NO, though. I thought the PROFILE TCPIP entry was the key to not having to mess with SECURE=NO? n Db n Can you post the RSCS LINKDEFINE and PARM statements you coded? Did you specify SECURE=NO on the PARM statement? -Mike From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of David Boyes Sent: Monday, March 29, 2010 11:34 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Ok, I'm confused now... Setting up LPR support in RSCS on 5.4. I've added the 515 TCP RSCS ; RSCS line to PROFILE TCPIP, and recycled TCPIP and RSCS to ensure that they're picking up the updated PROFILE TCPIP. I've defined a LPR link in RSCSTCP CONFIG, and when I print to it, I still get: 10:26:02 DMTLPR012I Link VA1P8 exit routine LPRXPSE loaded at 01FD0470 10:26:02 DMTLPR181I Link VA1P8 ready for session initiation 10:26:02 DMTAXM109I File queue reordered 10:26:02 DMTLPR193I Link VA1P8 connecting to host 192.168.101.17 port 515 printe r va1p8 10:26:02 DMTLPR083E Socket error on link VA1P8 request=Bind 10:26:02 DMTLPR083E return code=- 1 error number=13 (Permission denied) 10:26:02 DMTLPR183I Link VA1P8 session terminated 10:26:02 DMTMAN002I Link VA1P8 deactivated 10:26:03 DMTAXM109I File queue reordered 10:26:03 DMTAXM500I 1 file(s) closed on link VA1P8 The destination host is running LPD, and I can print to it with the CMS command line LPR with no problems. What did I miss? -- db
