>I have an RSCS link to an IBM 6400 dot matrix printer - > >LINKDEFINE SPSKH16 TYPE TCPASCII AST FORM * > >PARM SPSKH16 EXIT=ASCXONE EP='C=TCPASCII SEP=NO' ITO=0 # > > PORT=9100 HOST=xxx.xx.xx.xx > > >We chose to use a TCPASCII type link because that seemed to be the most >suitable, and we couldn't get an LPR type link to work at all. The >TCPASCII link works fine, until the users switch the printer off and go >home - > >09:01:16 DMTCMY700I Activating link SPSKH16 TCPASCII line=0000 = >class=* >queueing=priority >09:01:16 DMTTAP012I Link SPSKH16 exit routine ASCXONE loaded at 00BBF770 > >09:01:16 DMTTAP181I Link SPSKH16 ready for session initiation > >09:01:16 DMTAXM109I File queue reordered > >09:01:16 DMTTAP182I Link SPSKH16 session established > >09:01:16 DMTTAP146I Sending file 0184 (0184) on link SPSKH16 from >AESNEVM(SPCENTR), records 9594 >09:01:17 DMTTAP083E Socket error on link SPSKH16 request=Recv > >09:01:17 DMTTAP083E return code=- 1 error number=54 (Connection = >reset by >peer) >09:01:17 DMTTAP183I Link SPSKH16 session terminated > >09:01:17 DMTMAN002I Link SPSKH16 deactivated > >09:01:17 DMTAXM109I File queue reordered > >09:01:17 DMTAXM500I 1 file(s) closed on link SPSKH16 > >09:01:17 DMTCMY700I Activating link SPSKH16 TCPASCII line=0000 = >class=* >queueing=priority >09:01:17 DMTTAP012I Link SPSKH16 exit routine ASCXONE loaded at 00BBF770 > >09:01:17 DMTTAP181I Link SPSKH16 ready for session initiation > >09:01:17 DMTAXM109I File queue reordered > >09:01:17 DMTTAP182I Link SPSKH16 session established > >09:01:17 DMTTAP146I Sending file 0184 (0184) on link SPSKH16 from >AESNEVM(SPCENTR), records 9594 >09:01:17 DMTTAP083E Socket error on link SPSKH16 request=Recv > >09:01:17 DMTTAP083E return code=- 1 error number=54 (Connection = >reset by >peer) >09:01:17 DMTTAP183I Link SPSKH16 session terminated > >09:01:17 DMTMAN002I Link SPSKH16 deactivated > >09:01:17 DMTAXM109I File queue reordered > >09:01:17 DMTAXM500I 1 file(s) closed on link SPSKH16 > > >RSCS is restarting the link every second or so, until the users switch >their printer back on again. RSCS is probably trying to restart the link >because there is a file sitting on the queue, but I would prefer it not >to loop all night. I can't find a timeout value or retry interval that >looks relevant to this problem.
I was going to recommend to define the link with ITO=0 and AST, but you already have. In addition, a file has been queued to the link, RSCS is trying to deliver the file. There isn't other tuning parameters to modify this behavior. You could choose to remove the AST parameter and the autostart GCS exec which is restarting the link automatically. Instead provide the user the authority to start this link they turn the printer back on. Alternatively, LPR is a better alternative. However, RSCS will continue to try to deliver the file in a similar fashion under the same error conditions. Best Regards, Les Geer IBM z/VM and Linux Development
