Previous Topic: Implementing CA Dataquery Under CICSNext Topic: CA Dataquery Memory Requirements


CA Dataquery Requirements Under CICS/VS

Operation

CA Dataquery does not issue terminal read operations but instead uses pseudo-conversational programming techniques to initiate a transaction when the terminal has input ready for processing. Most core requirements are therefore restricted to the brief interval needed to actually process the input stream and to write to the display screen.

TRANSIDs

Following is a list of the CA Dataquery TRANSIDs and their functions. For information on ordering transaction IDs in the CICS Program Control Table (PCT), see Implementing CA Dataquery Under CICS.

DQIN

Used internally by CA Dataquery to reschedule CA Dataquery and need not be known by terminal users.

DQPR

Used internally by CA Dataquery for online printing to a 328x printer.

DQRY

Initiates a CA Dataquery session.

Limits

It is important that CA Dataquery transactions are not limited in such a way as to inhibit other system functions. This could happen, for example, if the DQIN transaction is put in a CICS task class that does not allow an asynchronous task to be dispatched.

CICS MRO

If you are operating in a CICS MRO environment, the Network Printers must be local to the transaction owning region. If the printers are not local to the transaction owning region, your print requests will fail.