Re: RSCS LPR won't autostart
Looks like that's the problem. AST is not enabled. I have to look into it closer because that config source that's supposedly in place has AST defined. Unfortunately it's on a remote VM which I don't administer and I don't have access to the RSCS config disk. If available, check the RSCS console to find the event which caused AST to be turned off. RSCS displays a message indicating AST was disabled for the link. Conditions that can cause this to occur include someone draining the link, or an unrecoverable error was encountered. Best Regards, Les Geer IBM z/VM and Linux Development
Re: RSCS LPR won't autostart
Looks like that's the problem. AST is not enabled. I have to look into it closer because that config source that's supposedly in place has AST defined. Unfortunately it's on a remote VM which I don't administer and I don't have access to the RSCS config disk.
RSCS LPR won't autostart
I have 2 different RSCS links defined to the same physical LPR (HP 8150). One link is for landscape, one is for portrait (see definitions below). W hen I send a printout to the portrait queue, the link autostarts fine and the document is printed successfully. When I send the same printout to the landscape queue, I get DMTAXM101I File 7431 (7431) enqueued on link ROC815WL and the link never starts. I can stop/restart the link and the document will then print. I have other LPR's defined exactly the same way and they all autostart correctly on both landscape and portrait queues. The links are defined as follows: LINKDEF ROC815W TYPE LPR MANUAL FORM *AST LINKDEF ROC815WL TYPE LPR MANUAL FORM *AST ... PARM ROC815W EXIT=LPRXPSE ITO=0 SEC=NO # HOST=149.24.51.28 #/* HP 8150 Devl WW * / PRINTER=raw # USER=YES # /* allow overrides * / EPARM='FORM=POCP1109' /* Portrait 60 lpp */ PARM ROC815WL EXIT=LPRXPSE ITO=0 SEC=NO # HOST=149.24.51.28 #/* HP 8150 Devl WW * / PRINTER=raw # USER=YES # /* allow overrides * / EPARM='FORM=LACP1012' /* landscape */ Any thoughts on what might be causing this?
RSCS LPR won't autostart
I have 2 different RSCS links defined to the same physical LPR (HP 8150). One link is for landscape, one is for portrait (see definitions below). W hen I send a printout to the portrait queue, the link autostarts fine and the document is printed successfully. When I send the same printout to the landscape queue, I get DMTAXM101I File 7431 (7431) enqueued on link ROC815WL and the link never starts. I can stop/restart the link and the document will then print. I have other LPR's defined exactly the same way and they all autostart correctly on both landscape and portrait queues. When you mention you can stop/restart the link and the document prints fine, that implies the link state is not drained. What state is the link in? Can you trace this? Best Regards, Les Geer IBM z/VM and Linux Development
Re: RSCS LPR won't autostart
Here's the info: ROC815W is the portrait queue, ROC815WL is the landscape queue. sm rscs q sys link name roc815w Ready; Link Line Name Status Type Addr LU Name Logmode Queueing ROC815W inactive LPR ... ... priority 1 link found sm rscs q sys link name roc815wl Ready; Link Line Name Status Type Addr LU Name Logmode Queueing ROC815WL inactive LPR ... ... priority 1 link found sm rscs q roc815wl q Ready; Link ROC815WL inactive sending=0 receiving=0 queued=1 looping=0 held=0 Pos Loc Origin Destination in Q IDID Node Userid Node Userid Status 1 7435 7435 MVM1 BHENRROC815WL SYSTEM waiting 1 file found Is that what you mean by link STATE?
Re: RSCS LPR won't autostart
Yes inactive is the link state, which indicates RSCS never tried to start the link when a file was queue to it. Next, check if autostart is still defined on for the link Issue: sm rscstst1 q links node roc815wl show ast Best Regards, Les Geer IBM z/VM and Linux Development Here's the info: ROC815W is the portrait queue, ROC815WL is the landscape queue. sm rscs q sys link name roc815w Ready; Link Line Name Status Type Addr LU Name Logmode Queueing ROC815W inactive LPR ... ... priority 1 link found sm rscs q sys link name roc815wl Ready; Link Line Name Status Type Addr LU Name Logmode Queueing ROC815WL inactive LPR ... ... priority 1 link found sm rscs q roc815wl q Ready; Link ROC815WL inactive sending=0 receiving=0 queued=1 looping=0 held=0 Pos Loc Origin Destination in Q IDID Node Userid Node Userid Status 1 7435 7435 MVM1 BHENRROC815WL SYSTEM waiting 1 file found Is that what you mean by link STATE?
