On Thu, Jan 20, 2022 at 08:10:47AM +1100, Attila Fogarasi wrote: > OS/390 era software didn't support network printing without extra-cost > products (so you can't direct SYSOUT=A to T006).
Good to know, thank you. > If you have CICS or IMS then you can easily define the printer and > send a test message, otherwise you would need to write an SNA > application using the VTAM macros. I have CICS available, though maybe an upgrade to z/OS is more straight-forward. I was considering that anyways. > The printer data stream is surprisingly complex, hence the pricing of > the products that could use it. This is a good part of the reason for > the rise of non-mainframe solutions :) Things became better with z/OS > but you are using OS/390. Thank you, -Alex > On Thu, Jan 20, 2022 at 5:26 AM Alexander Huemer <[email protected]> > wrote: > > > Following up on this. > > > > I have added a LU1 MODEENT definition to ISTINCLM according to [1] and > > assigned that to the respective LU, in my case that is T006. > > When I power the printer on, I get 'SLU ENABLED' in `d net,id=T006'. > > Apparently VTAM knows the printer is there. > > The documentation I've consulted so far talks a lot about IEBGENER, the > > P390 cookbook also has a JCL example that is supposed to print a > > document. It says, bone-dry: 'DD SYSOUT=A'. What all documents I've read > > so far omit though, is how I tell my system that a printer is at T006. > > How do I tell my system that SYSOUT=A should go to T006? > > > > -Alex > > > > [1] https://www.ibm.com/docs/en/gddm?topic=gddm-4224-ipds-printer > > > > On Sun, Jan 16, 2022 at 09:12:22PM +1100, Attila Fogarasi wrote: > > > The 42xx printers are dot matrix that were primarily meant to be used by > > > non-mainframe hosts so they come in a variety of configurations to > > emulate > > > asynchronous devices. You might have one that is not usable with OS/390 > > > without special hardware (there is an adapter card on the 3174 for it, > > for > > > example. You'd have to determine exactly what model of 4224 you have, > > and > > > then configure the 3174 appropriately. I don't think it is a VTAM > > logmode > > > issue (yet). You've picked about the most difficult printer type to use, > > > might be a lot easier to get a 3287 etc. The 4224 claim to fame was that > > > it could handle a high volume of dot matrix multi-part form printing at > > > high speed. Unlikely to be useful these days :) > > > > > > On Sat, Jan 15, 2022 at 6:32 AM Alexander Huemer <[email protected] > > > > > > wrote: > > > > > > > Blast from the past, I know. Maybe somebody here remembers how this is > > > > done. > > > > I have a 4224, connected to a 3174 that is talking APPN to OS/390. The > > > > printer registers successfully on the 3174, I see a 'p' at the port > > that > > > > it is connected to in the 'Status Summary' screen of the 3174. > > > > Searching for documents that would explain how OS/390 / VTAM is to be > > > > configured, I didn't find much. > > > > [1] provides guidance in regard to a MODEENT macro that is supposed to > > > > work. > > > > But, where to go from there? I found [2], but RSCS seems to be a > > VM-only > > > > thing. > > > > I assume I'll have to configure the thing somehow in VTAM, though there > > > > must be more to it I think. > > > > If anybody can point me to relevant documents or has a 20 year old > > > > wrinkled-up cheat-sheet in their deskdrawer, I would appreciate a > > little > > > > help. > > > > > > > > -Alex > > > > > > > > [1] https://www.ibm.com/docs/en/gddm?topic=gddm-4224-ipds-printer > > > > [2] > > > > > > https://www.ibm.com/docs/en/zvm/7.2?topic=connections-sna-3270-printer-support > > > > > > > > ---------------------------------------------------------------------- > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to [email protected] with the message: INFO IBM-MAIN > > > > > > > > > > ---------------------------------------------------------------------- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
