Resource Definition Types and Characteristics

This chapter defines different resource definitions provided by OSC. Each resource definition has various settings according to its characteristics. Therefore the administrator needs to accurately set the following resource definitions according to the resources used by the application programs.

CONNECTION resource definition defines the information used to connect an OSC application server to other OSC application servers. Unlike CICS, OSC does not also register the SESSION resource definition when registering the CONNECTION resource definition.

The following is a list of the CONNECTION resource definition elements. The "blank" choice indicates a blank space.

The following is an example of a macro that defines the CONNECTION resource definition OSCA, which contains the connection information to OSC application server OSC00001.

DOCTEMPLATE resource definition defines the properties of the document template.

The following is a list of the DOCTEMPLATE resource definition elements.

The following is an example of a macro that defines the DOCTEMPLATE resource named 'DOC01'.

The FILE resource definition defines the elements related to the physical data set settings and operations of the file.

The following is a list of element of the FILE resource definition.

The following is an example of a macro that defines the FILE0001 file, which can only read and add a record from and to the OSC.OSDLIB.FILE0001 data set. FILE00001 enables the add record and read record authorities for application programs but not the search, delete, or modify authorities.

JOURNALMODEL resource definition defines the OSC journal name, the physical data set where the actual record will be written, and the connection information. If the journal name is being used by a previous version of CICS, use the name after changing the type for compatibility.

The following is a list of elements of the JOURNALMODEL resource definition.

The following is an example of a resource macro that defines JNMODEL2 and JNMODEL3 which write a journal record to the SMF data set. JNMODEL3 are converted to DFHJ03 for compatibility with the old version of CICS.

The following is an example of a resource macro that defines JNAUD01 for writing journal records in MVS LOG STREAM.

The PROGRAM resource definition defines the elements related to the program control information to execute a transaction or a part of a transaction.

The following is a list of elements of the PROGRAM resource definition.

The following example is a resource definition macro which defines the OIVPMAIN program written in COBOL.

The TDQUEUE resource definition defines the TDQ (Transient Data Queue) properties. The main TDQUEUE resource definition elements include filename and the method for using the file..

A TDQ can be divided into three types according to functional characteristics: Extra-partition, Intra-partition, and Log. In terms of management, it can be divided into two types: Indirect and Remote. OSC supports resource definitions for the total five TDQs.

The following is a list of the common elements of each TDQUEUE resource.

The TERMINAL resource definition defines the characteristics of the terminal that communicates with OSC, and whether the terminal is currently used.

The following is a list of elements of the TERMINAL resource definition.

The following is an example of a macro which defines TTRM terminal, which has TESTTERM as the NETNAME and TESTTTRM as the TYPETERM. The TTRM terminal is set up to print out with PRNT after receiving a print request. PRNT must be defined as a TERMINAL resource. If PRNT cannot be used, printing fails.

The TRANCLASS resource definition defines the elements for controlling a queue count and the number of transactions that can be executed simultaneously by grouping transactions. The TRANCLASS function is supported by configuring the Tmax server, therefore Tmax needs to be configured according to the resource definition. The oscadmin tool provides a function that automatically displays the Tmax configuration. For more information, refer to OpenFrame Tool Reference Guide.

The following is a list of elements of the TRANCLASS resource definition.

The following example is a macro that defines TCL1 TRANCLASS. The number of simultaneously executable transactions is 3, and only up to 10 transaction requests can wait in a queue.

The TRANSACTION resource definition defines the elements related to the functions provided by OSC.

An OSC application program is composed of one or more programs that provide specific functions. A request for this program is a transaction. OSC identifies these transactions with a transaction identifier (TRANSID).

The following are descriptions for each element of the TRANSACTION resource definition.

The following example is a resource definition macro which defines the transaction OIVP. The program name is set to OIVPMAIN, the security check will be executed, and TWASIZE is set to 255.

The TSMODEL resource definition specifies the TSQ properties according to the prefix of the TSQ (Temporary Storage Queue) name. The TSMODEL resource definition defines the TSMODEL name and the prefix of TSQ to which this TSMODEL is applied, and sets LOCATION and RECOVERY elements as the corresponding TSQ properties.

The following are descriptions for elements of the TSMODEL resource definition.

The following example is a macro which defines TSMODEL to select the storage space for TSQ starting with TEST, to not use the recovery function, and to use the security check function.

The TYPETERM resource definition defines the common properties for the terminal group. If there are terminals which have the same properties, specify the properties for the TYPETERM resource definition, and specify the TYPETERM name for each TERMINAL resource definition in order for multiple terminals to act in the same way. Each TERMINAL resource definition must specify the TYPETERM resource name.

If the TYPETERM resource definition is used, the administrator does not need to set the individual terminals, reducing the time and potential for administrator error during the setting process.

The following are descriptions of elements of the TYPETERM resource definition.

The following is an example of a macro which defines TYPETERM named TESTTTRM. It disables the alarm function, enables extended color, supports highlight effects (such as reverse, underline, and blink effects), sets the terminal input/output value length from 512 to 4,096 bytes, supports Japanese KATAKANA, supports the outline of fields, supports the Programmed Symbol Facility, specifies 2-byte characters, disables the conversion of lower case to upper case, sets the screen size to 24X80, and sets TCTUA to 128 bytes. In the transaction, the ALTERNATE screen size with the specified PROFILE definition is 27X132, and the default screen size with the specified PROFILE definition is 24X80.

You can define the URIMAP resource when you are using OSC as an HTTP client or server to specify the HOST and PATH. You can send/receive requests to/from an external server/client corresponding to the HOST and PATH. When a request is received from an external client through URIMAP, you can specify the ANALYZER and Alias Transaction, which is the name of the transaction that is mapped when the DFHWBA program starts. You can also specify a PROGRAM name to use to handle a specific request.

The following describes each item in the URIMAP resource definitions.

You can define the TCPIPSERVICE resource for external communication by setting OSC TCP. OSC uses TCPIPSERVICE by integrating it with URIMAP to specify an ANALYZER program or an alias transaction for a request received through URIMAP.

The following describes each item in the TCPIPSERVICE resource definitions.