8
Mainframe Express CICS Support Queues Queues are dynamic storage mechanisms that can be used by transaction programs to pass data on to other transactions or to external destinations. Mainframe Express (MFE) CICS supports temporary storage queues (TS) and Transient Data queues (TD) Temporary Storage Queues A program can access records in a temporary storage (TS) queue in any order, by specifying the position of the record in the queue. A Temporary Storage Table (TST) entry is required only if the queue is one of the following White PapersOn a remote CICS system White PapersRecoverable If your CICS API fails with QUIDERR, EIBRESP 44, it may be that you need to create a Temporary Storage Table entry in the Resource Definition. A TST entry is also required if INQUIRE TSQUEUE/TSQNAME is to be used. The Temporary Storage Table (TST) The Temporary Storage Table lets you define local or remote temporary storage queues, which are datasets created by transactions to hold temporary data. To create a TST entry, access the character Resource Definition (Mainframe Express IDE, Tools, CICS, Resource Definition). Press F7 for Group Resources and select the group you are using. Press F8 for TST Page 1 of 8

Mainframe Express CICS Support Queues Mainframe Express ... · Mainframe Express CICS Support Queues [Extrapartition] Path: Specify the path of the file that holds this queue if you

Embed Size (px)

Citation preview

Mainframe Express CICS Support Queues

Queues are dynamic storage mechanisms that can be used by transaction programs to pass data on to other transactions or to external destinations.

Mainframe Express (MFE) CICS supports temporary storage queues (TS) and Transient Data queues (TD)

Temporary Storage Queues

A program can access records in a temporary storage (TS) queue in any order, by specifying the position of the record in the queue.

A Temporary Storage Table (TST) entry is required only if the queue is one of the following

White PapersOn a remote CICS system

White PapersRecoverable

If your CICS API fails with QUIDERR, EIBRESP 44, it may be that you need to create a Temporary Storage Table entry in the Resource Definition.

A TST entry is also required if INQUIRE TSQUEUE/TSQNAME is to be used.

The Temporary Storage Table (TST)

The Temporary Storage Table lets you define local or remote temporary storage queues, which are datasets created by transactions to hold temporary data.

To create a TST entry, access the character Resource Definition (Mainframe Express IDE, Tools, CICS, Resource Definition).

Press F7 for Group Resources and select the group you are using.

Press F8 for TST

Page 1 of 8

Mainframe Express CICS Support Queues

Enter the fields as follows:

Data id: The name of the queue. The name can be up to 8 characters. The first character must be a letter. The name is forced to upper case.

Description: Up to 60 characters of optional text.

Recoverable: Determines whether the queue is recoverable.

Remote System id: (Remote queues only). The id of the remote system on which this queue resides. It can be up to 4 characters. The first character must be A-Z, @, # or $. The remaining characters can be any of these, or 0-9. The name is forced to upper case.

Remote Data id: (Remote queues only). The name by which this queue is known on the remote system. Can be up to 8 character from the set A-Z, @, # or $. The first character must be a letter. The name is forced to upper case.

Resource keys: This is a set of 24 display-only indicators, corresponding to the 24 resource keys you can toggle on and off for this queue. Each CICS resource has a similar set of keys associated with it. A user has access to a particular resource only through a matching key as defined in his Sign-on Table entry.

Enter Resource keys to toggle: By default, all 24 resource keys are disabled. If you enable a key, its representation on the above list changes to its number, for example, "08". To change one or more keys, enter them here as a comma-separated list.

Page 2 of 8

Mainframe Express CICS Support Queues

Once you have made these changes using the character resource definition interface, you must refresh the Mainframe Express session. To do this, right-click CICS System in the left-hand pane of the CICS View and click Refresh CICS View from RDF on the popup menu.

Transient Data Queues

A program can only process transient data (TD) sequentially, in the order in which it was written (first-in-first-out).

TD queues are also known as destinations and you can define them in the Destination Control Table (DCT). You can define a TD queue as one of three types:

White PapersIntrapartion

White PapersExtrapartition

White PapersIndirect

You can also specify whether the queue is to be recoverable.

Intrapartition and Extrapartition queues are stored as local files if defined as local. Queues defined as remote are stored on other CICS systems.

Intrapartition queues are accessible only from Mainframe Express CICS Option but offer the Automatic Transaction Initiation (ATI) facility. Extrapartition queues are accessible from non-MFE CICS Option applications.

An indirect queue is simply an alias for another TD queue defined in the DCT.

The Destination Control Table (DCT)

The Destination Control Table (DCT) enables you to set up transient data queues for those CICS functions which use queues.

For each queue you can specify:

Queue name (four character ID used to identify the queue in a CICS program)

Type of INTRA or EXTRA

A non-recoverable INTRA (intra-partition) transient data queue is stored in the TXTDN file, while recoverable INTRA queues are stored in the TXTDR file.

You can use an INTRA queue for both input and output

An EXTRA queue is held in a user specified sequential file.

For EXTRA type queues you also need to define:

Page 3 of 8

Mainframe Express CICS Support Queues

Filename for queue

Filetype (Input, output or append)

Minimum and maximum record lengths

To create a DCT entry, access the character Resource Definition (Mainframe Express IDE, Tools, CICS, Resource Definition).

Press F7 for Group Resources and select the group you are using.

Press F2 for DCT.

Enter the fields as follows.

Destid:A required field specifying the local name of this queue. It can be up to four alphanumeric characters, the first of which must be a letter other than C (MFE CICS uses destinations beginning with C for its own purposes).

Description: Up to 60 characters of optional text.

Type: Specified this queue as one of the following types:

I - Intrapartition. The contents of the queue are accessible only to transactions D - Indirect. This entry is simply an alias for another DCT entry, specified in the Name field here. E - Extrapartition. The contents of the queue are accessible to non-transaction programs.

Page 4 of 8

Mainframe Express CICS Support Queues

The value you specify for this field determines which of the remaining fields must be filled in. The values I, D and E must correspond to completed sets of fields under Intrapartition, Indirect and Extrapartition labels respectively.

Enabled:Determines whether the queue is enabled at system startup (when the region is started).

Recovery: Determines if the queue is recoverable.

If you specify that that the queue is recoverable (Yes), you must also fill in the FS Server id field. This is because CICS recovery is handled by Fileshare and you must specify the name of the Fileshare server that holds this queue. You can also specify that the queue is not recoverable.

[Indirect] Name: Specifies the actual name of another DCT entry for which this entry is an alias. The name can be up to four characters, the first of which must be a letter.

You must fill in this field if you have specified Type=D

[Intrapartition] Transaction id: The id of the transaction to be run when this queue reaches the trigger level specified here (the transaction must be specified in the PCT).

Specify the id in either of these formats

Up to four alphanumeric characters, the first of which must be a letter

A hexadecimal value of the form x'hhhhhhhh' or x"hhhhhhhh".

You must fill in this field if you have specified Type=I.

[Intrapartition] Terminal Id: The id of the terminal with which this queue is associated (the terminal must be defined in the Terminal Table). The id can be up to four alphanumeric characters, the first of which must be a letter;

You must fill in this field if you have specified Type=I.

[Intrapartition] Trigger Level: The number of data records to be accumulated in this queue before the specified transaction is run. A value of 0 means that the transaction is never triggered.

You must fill in this field if you have specified Type=I.

[Extrapartition] Filename: Specify the filename of the file that holds this queue if you want to override the default. Do not include the file extension.

The default filename and extension is dfhxdddd.tdq, where dddd is the four character name of this queue specified in the Destid field

Page 5 of 8

Mainframe Express CICS Support Queues

[Extrapartition] Path: Specify the path of the file that holds this queue if you want to override the default which is the path specified by FILEPATH. Do not include the filename or extension.

[Extrapartition] Extension: Specify the file extension of the file that holds this queue if you want to override the default.

FS Server id: The id of the Fileshare server on which this queue resides. The id can be up to 16 characters.

You must fill in this field if you have defined the queue as recoverable (Recovery=Y).

[Extrapartition] Min. record length: The minimum length of records in this queue. Must be less than or equal to the value specified in Max. record length.

You must fill in this field if you have specified Type=E.

[Extrapartition] Max. record length: The maximum length of records in this queue. Must be greater than, or equal to, the value specified in Min. record length.

You must fill in this field if you have specified Type=E.

I/O Type: Type of the TD queue. The options are Input, Output and Read Backward. Output is the default.

Print attrs: The CTL print attributes the TD queue is to have. The options are Machine, ASA or NoCtl. The default is NoCtl.

OpenState: The state of the TD queue. The options are Open or Closed. The default is Open.

File type: The type of file. The options are Normal, or Line Sequential. Line Sequential produces a file that you can edit. The default is Normal.

Page 6 of 8

Mainframe Express CICS Support Queues

Remote queue id: The name by which this queue is known on the remote system (that is, the region) if this is different from the local name. If you do not specify a value, the queue is assumed to have the same name on both regions. The remote region's DCT must contain an entry for this queue.

Remote system id: The id of the remote system on which this queue resides. The id can be up to four alphanumeric characters, the first of which must be a letter.

This value must correspond to the system id of an MFE CICS region you have defined (a region's system id is specified in the Local SYSID field of the SIT you run it with).

This field and the next must be filled in if you want to enable function shipping.

Resource keys: This is a set of 24 display-only indicators, corresponding to the 24 resource keys you can toggle on and off for this queue.

Each MFE CICS resource has a similar set of keys associated with it. A user has access to a particular resource only if a matching key as defined in the user's Sign-on Table entry.

Enter Resource keys to toggle: By default, all 24 resource keys are disabled. If you enable a key, its representation on the above list changes to its number, for example, "08".

To change one or more keys, enter them here as a comma-separated list. For example:

08 Toggles resource key 08

Page 7 of 8

Mainframe Express CICS Support Queues

08,18-22,24 Toggles keys 08, 18, 19, 20, 21, 22 and 24

ALL-ON Sets all 24 keys on

ALL-OFF Sets all 24 keys off

ALL-ON,08,12 Enables all keys except 08 and 12

Queue Location and Recovery.

You specify the path to the TS and TD queues on the TS/TD tab of the SIT (Mainframe Express IDE, CICS tab, select SIT in left hand pane and right click on the required SIT in the left hand pane and select Properties). You do not need to specify Fileshare Server ids for the recoverable queues but it is recommended.

Refer to the context help in Mainframe Express 3.0 for more information on the individual fields.

Page 8 of 8