The resource definitions stored by MSS are different in both content and form to those stored on the mainframe. Many resource types and attributes that you can define on the mainframe are meaningless in the Windows environment, for example LSRPOOL. MSS recognizes these resource types and attributes but takes no action on them. Conversely, MSS understands some additional attributes that only make sense in the Windows environment, and some of these are mandatory.
The following table lists all the types of resource definition used or recognized by MSS. For each type of resource definition, the name by which it is known in the .rdt file used for exchanging resource definitions with other Enterprise Server with MSS systems is given, followed by an indication of the support provided, then any abbreviation used within the interface and its meanings. Mainframe resource types are listed first, followed by Micro Focus extensions.
| Keyword in .rdt file | Used or recognized | Abbreviation | Meaning |
|---|---|---|---|
| CONNECTION | Used | ||
| FILE | Used | FCT | file control table |
| LSRPOOL | Recognized | ||
| MAPSET | Recognized | ||
| PARTITIONSET | Recognized | ||
| PARTNER | Recognized | ||
| PROFILE | Recognized | ||
| PROGRAM | Used | PPT | program processing table |
| SESSIONS | Recognized | ||
| TERMINAL | Used | Term | terminal |
| TRANCLASS | Used | TRCLASS | transaction class |
| TRANSACTION | Used | PCT | program control table |
| TYPETERM | Used | T-type | terminal type |
| TDQUEUE | Used | DCT | destination control table |
| _JOURNAL | Extension | JCT | journal control table |
| _PGMLIST | Extension | PLT | program load table |
| _SIGNON | Extension | SNT | signon table |
| _SIT | Extension | SIT | system initialization table |
| _STARTUPLIST | Extension | ||
| _TEMPSTORAGE | Extension | TST | temporary storage table |
| _XOPENCOMPAT | Extension | XAT | XA-compliant database table |
The CICS resources are defined in the resource definition file dfhdrdat (with index dfhdrdat.idx). This is an ISAM file.
When Enterprise Server runs the application, it needs to know where the application's dfhdrdat file is. You specify its location using the /ip switch of the casrdtex command and /op switch of the casrdtup command.