Hi,

CICS ROUTE is not currently supported.

You can use the CICS Precompiler directive CICSECM FUNCTION option to control the behaviour. You can ignore unsupported CICS Syntax or to cause an abend at runtime.

If you want to print to multiple 3270 printer terminals then you could look to do something like:-

- Store Data to be printed in storage such as TSQ , File , SQL Database

- Use EXEC CICS START TERMID to start a transaction on the required terminals

- In the started transaction you could retrieve the data and SEND to the Terminal.

Regards

David

Hi David

I was planning on doing an EXEC CICS START for each different printer, then in the receiving task just receiving the data and doing a SEND MAP PRINT along with the SEND PAGE to send the logical BMS message to the printer.

I guess my question is where is the printer(in the Windows environment) tied to the TERMID in CICS?

I'm using the .NET CICS administrator program to configure the region.

n the system definitions that ship with .NET CICS, I see a termid, such as L860, which has a Net Name of "IVPL860", but how is "IVPL860" tied to the Windows printing environment?

Hi David

I was planning on doing an EXEC CICS START for each different printer, then in the receiving task just receiving the data and doing a SEND MAP PRINT along with the SEND PAGE to send the logical BMS message to the printer.

I guess my question is where is the printer(in the Windows environment) tied to the TERMID in CICS?

I'm using the .NET CICS administrator program to configure the region.

n the system definitions that ship with .NET CICS, I see a termid, such as L860, which has a Net Name of "IVPL860", but how is "IVPL860" tied to the Windows printing environment?

Hi David

I was planning on doing an EXEC CICS START for each different printer, then in the receiving task just receiving the data and doing a SEND MAP PRINT along with the SEND PAGE to send the logical BMS message to the printer.

I guess my question is where is the printer(in the Windows environment) tied to the TERMID in CICS?

I'm using the .NET CICS administrator program to configure the region.

n the system definitions that ship with .NET CICS, I see a termid, such as L860, which has a Net Name of "IVPL860", but how is "IVPL860" tied to the Windows printing environment?

Are you using native Enterprise Server with Mainframe Subsystem Support, or Enterprise Server for .NET?

You wrote "I'm using the .NET CICS administrator program to configure the region" - but there isn't any .NET administration program, strictly speaking, so it's not clear to me which CICS environment (native or managed) you're using.

Native Enterprise Server is administered using a web browser, through the Enterprise Server Administration (MFDS) and Enterprise Server Monitor and Control (ESMAC) web pages. Enterprise Server for .NET is administered using Microsoft Management Console. (Both also offer command-line utilities and other administration options, but those are the main interactive ones.)

Since you mention .NET, I'll assume you're using ES for .NET for now.

CICS for ES for .NET doesn't yet have all of the printing features that are available in native ES. Currently it only supports TN3270 printer connections. That means you have to use a TN3270 client such as Rumba that supports printing, and configure it to connect to ES for .NET as a TN3270 printer. The client must also be configured to use a specific Windows printer.

So, for example, in Rumba 9, you would do the following:

1. Start Rumba Desktop
2. Go to File | New | Mainframe Printer
3. Select the Windows printer you want to use by right-clicking the appropriate entry under PC Printer Queues and selecting Output Destination
4. Go to Connection | Configure
5. On the General tab, select TN3270
6. On the TN3270 tab, set the hostname and port
7. Also on the TN3270 tab, you can enter a device name; this will be the LU name for your printer. If you don't enter a device name, you'll get an LU name from the pool when you connect. In either case, that's the name of your printer in CICS, so it's generally easiest to specify a device name and always use that.

At least that's the theory. At the moment I seem to be having some trouble getting this to work.

I'm not getting any output from a SEND to a specific printer LUNAME in CICS under ES for .NET. It's possible that under managed CICS we currently only support screen printing (printing to a printer associated with a terminal session, using the start-print bit in the WCC). Most of the printing support in ES for .NET currently is in the JES engine.

I'll look into this a bit further, but you may need to contact Micro Focus support to raise an RPI if you need this functionality.

The Enterprise Server for .NET documentation states that SEND MAP PRINT is fully supported, but I haven't been able to get it to work in a recent build. I believe it was working at one point, though possibly only to the printer associated with the primary facility (terminal).

I'm going to raise an internal problem report for this (primarily for tracking purposes since I'll probably be the one to investigate and fix it anyway), but as I noted above, if your application requires CICS printing support in ES for .NET, I'd recommend you open an incident with Micro Focus Customer Care and ask them to raise a customer RPI.

Thanks for looking into this Michael.

I will open an incident for this.

From within ES for .NET, though, how do you specify which terminal goes to which Windows printer?

Thanks for looking into this Michael.

I will open an incident for this.

From within ES for .NET, though, how do you specify which terminal goes to which Windows printer?

You can't associate a terminal with a Windows printer directly, unless the TN3270 client software you're using has some special mechanism for doing that.

What you should be able to do is associate a terminal session with a CICS printer session, and associate the printer client for that session with a specific Windows printer. That's what I described in my first reply. Unfortunately the terminal-session-to-printer-session association doesn't seem to be working, at least in the current Enterprise Developer 2.2 build. (I don't have an ED 2.1 product currently installed to see if that's a regression; it's possible it does work in the ED 2.1 product.)

So, to reiterate what's in that first post:

• You need a TN3270 printer client. Rumba includes one, as do many other TN3270 implementations.
• You configure your TN3270 client software to connect a printer session to ES.
• You tell your TN3270 client what Windows printer to print to. How you do this depends on your client software.
• You configure your TN3270 terminal client to associate itself with the printer session. Again, how you do this depends on the client software.