The Web User Interface server repository contains the Web User Interface server's view and menu definitions, that is, it contains all the recoverable resources maintained by the Web User Interface server.
The Web User Interface server repository consists of a variable length record, key sequenced VSAM file created before using the Web User Interface. You must have one repository, which cannot be shared, for each Web User Interface server.
The DDname of the Web User Interface server repository must be included in the start-up JCL for the Web User Interface server.
Definitions from the repository can be imported and exported to a transient data queue (TDQ) so that you can back up menu and view definitions, distribute definitions to other Web User Interface servers, and migrate menus and view sets to other releases.
The COVC import and export functions use transient data queues that have certain properties. COVI and COVE are examples of these TDQs. You can copy COVI and COVE to create more TDQs. See CICS® Transaction Server for z/OS® Installation Guide for more information about the COVI and COVE TDQs.
You can import and export to and from any suitable named TDQ.
The import and export TDQ entries should be associated with a single data set or member of a partition data set with the following characteristics:
Record format: VB
Logical record length: 32000
Block size: 32004
You have the option to import view sets, menus or both view sets and menus in one operation.
If you do not specify OVERWRITE on the COVC import panel, only definitions for view sets or menus that do not already exist in the input data set are imported. Definitions for view sets or menus that already exist are ignored.
If there is a failure during import, complete menu and view set definitions that have already been read successfully remain in the repository but the failing definition and any that follow are not imported. In the case of failure, a message is written to the EYULOG or operator log.
See Importing view set or menu definitions for guidance on carrying out an import operation.
You can export either view sets or menus in one operation but not both. If the same TDQ is used for export more than once, for example, to export menus then view sets, the second export either overwrites the first or is appended to it, depending on how the TDQ is defined.
If there is a failure during export, the data in the TDQ that you were writing to is incomplete so should be discarded. In the case of failure a message is written to the EYULOG or the operator log.
See Exporting view set or menu definitions for guidance on carrying out an export operation.
The starter set of view set and menu definitions is supplied in CICSTS31.CPSM.SEYUVIEW. It is available in languages denoted by EYUnVX01, where n is the language letter. These starter set names match the 3-letter language identifiers that you specified on the INITPARM CICS system initialization parameter. For a list of supported languages see Table 8.
Language | Language identifier | Starter set name |
US English | ENU | EYUEVX01 |
Japanese | JPN | EYUKVX01 |
Simplified Chinese | CHS | EYUSVX01 |
The naming convention for the supplied set of view set, view and menu definitions is as follows:
where objectname is the name of a resource.
This displays a tabular view.
This displays a detail view. In some cases, detail views are named DETAIL1, DETAIL2, and so on, when applicable.
This displays a confirmation panel for that action
where menuname is the name of a menu. For example, EYUSTARTMENU displays the starter set's home menu and navigation frame.