Installing File-AID/MVS in a CA roscoe environment
- Running File-AID/MVS under CA Roscoe requires that you do the following:
- Activate the ETSO option of CA Roscoe.
- Set up an RPF to allocate the required ISPF and File-AID/MVS files.
- Invoke File-AID/MVS under ISPF from a panel.
Does this require a separate TSO region for each active File-AID/MVS user?No.
CA Roscoe runs as a single address space with users sharing the same region. ETSO lets CA Roscoe simulate a TSO environment, which allows each user to process programs intended to run under TSO. All processing is done in the CA Roscoe region.
Do I need to install both ISPF and PDF for File-AID/MVS to run?Yes.
Both ISPF and PDF are required.
- What if ETSO/CA Roscoe abnormally terminates with abend code U0998?
This condition can cause File-AID/MVS to hang ETSO/CA Roscoe while switching between functions in the product. If this occurs, the EPL storage limits are not set high enough. Increase the GETMAIN amounts in the EPL.
Tasks
Perform the following tasks to set up the necessary File-AID/MVS product for CA Roscoe users.
Task 2.1 Install and configure BMC AMI DevX File-AID/MVS
Use the installation instructions in Installing to install and configure File-AID/MVS.
Task 2.2 Verify ISPF Installed under CA Roscoe
Verify that ISPF has been installed under CA Roscoe. This is a requirement for File-AID/MVS to run under CA Roscoe.
Task 2.3 Make the File-AID Load Library Available to CA Roscoe
The File-AID load library can be made available to CA Roscoe by using one of the following methods:
- Concatenate the File-AID load libraries, hlq.CXVJLOAD and hlq.SXVJLOAD, to the ETSOLIB DD statement in your CA Roscoe start-up JCL.
- Copy the File-AID load libraries to an existing library allocated to ETSOLIB.
- Allocate the File-AID load libraries to ISPLLIB in the RPF. See Create an RPF to Invoke File-AID/MVS.
Task 2.4 Create an RPF to Invoke BMC AMI DevX File-AID/MVS
The appropriate File-AID libraries must be allocated under ETSO. The RPF (Roscoe Programming Facility) allocates both ISPF and File-AID libraries and ISPSTART is called to invoke File-AID under ISPF.
- Modify the sample JCL member hlq.SXVJSAMP(XFARPF).
- Check the data set names and make sure they point to your File-AID and system libraries.
- Modify the ISPF version, release and modification level for your site.
- To call PDF instead of File-AID replace the CALL in hlq.SXVJSAMP(XFARPF) with this CALL:
Task 2.5 Define File-AID in the EPL
ISPSTART must be defined in the EPL (Eligible Program List) to enable terminal users to call File-AID/MVS. Sites must ensure the following when these applications are added to the EPL:
- The list must be arranged in ascending, alphabetical order by application name.
- Each record that comprises the list must conform to the format in these tables:
The following information will help you to determine memory requirements:
- If File-AID is installed in 31-bit mode, most memory usage is above the 16-MB line.
- An edit session in File-AID requires the most memory.
- File-AID uses reentrant modules. Therefore, storage for these modules is only acquired once.
- Editing non-keyed files requires enough storage for the size of the file plus 170K of overhead for each user. Storage for keyed files requires just the 170K of overhead for each user.
Keyed File Region Requirements and Non-Keyed File Region Requirements show typical region requirements for editing a keyed file and non-keyed file of 700 300-byte records. Fixed storage is acquired once for all users. Variable storage is acquired by each user using the Edit function.
Keyed File Region Requirements
File | Fixed | Variable |
|---|---|---|
File-AID reentrant modules | 900K |
|
File-AID non-reentrant modules |
| 7K |
Working storage | 64K |
|
Buffers | 99K |
|
Total | 900K | 170K |
Non-Keyed File Region Requirements
File | Fixed | Variable |
|---|---|---|
Size of Data File (LRECL x no. of records) |
| 205K |
Total | 900K | 375K |
Other File-AID functions require significantly less region.
ETSO 5.7 (And Above)
ETSO 5.7 (and Above)
Column | Contents | Comments |
|---|---|---|
1-8 | Application Name | ISPSTART. If ISPSTART exists, an ALIAS can be specified for ISPSTART. |
9 | blank |
|
10-12 | Maximum Executions | Maximum number of concurrent executions of the application. |
13 | blank |
|
14-17 | CPU Time Slice | Maximum number of CPU time slices to be provided before the application is forced to terminate. The default time slice value is equal to 5,000 microseconds. To prevent the application from terminating, specify 9999. |
18 | blank |
|
19-24 | Maximum Memory <16 MB line | Total amount of memory (in K) to be provided to the application below the 16 MB line. |
25 | blank |
|
26-31 | Memory Request <16 MB line | Total amount of memory (in K) to be provided to the application in any one variable length request. For example, an application limited to a maximum of 512K can be further restricted so memory is provided in increments of 32K. Storage is acquired below the 16 MB line. |
32 | blank |
|
33-38 | Maximum Memory >16 MB line | Maximum amount of memory (in K) to be provided to the application above the 16 MB line. |
39 | blank |
|
40-45 | Memory Request >16 MB line | Maximum amount of storage (in K) that the application can acquire above the 16 MB line in any one getmain request. |
46 | blank |
|
47 | Dump Flag | Flag used to control the production of a dump if the application should abend. Y - Produce dump. (Y and D are synonymous.) N - Suppress dump. Recommended value is N. |
48 | blank |
|
49 | MODESET Flag | Flag used to control the application’s use of SVC107. |
50 | blank |
|
51-52 | TSO Flag | Flag used to designate that the application is to be called as a TSO command processor. ISPSTART is a TSO command processor. |
53-255 | Ignored |
|
ETSO 5.6
ETSO 5.6
Column | Contents | Comments |
|---|---|---|
1-8 | Application Name | ISPSTART. If ISPSTART exists, an ALIAS can be specified for ISPSTART. |
9 | blank |
|
10-13 | CPU Time Slice | Maximum number of CPU time slices to be provided before the application is forced to terminate. The default time slice value is equal to 5,000 microseconds. To prevent the application from terminating, specify 9999. |
14 | blank |
|
15-18 | Maximum Memory | Total amount of memory (in K) to be provided to the application. |
19 | blank |
|
20-23 | Memory Request | Total amount of memory (in K) to be provided to the application in any one variable length request. For example, an application limited to a maximum of 512K may be further restricted so memory is provided in increments of 32K. |
24 | blank |
|
25 | Dump Flag | Flag used to control the production of a dump if the application should abend. Y - Produce dump. (Y and D are synonymous.) N - Suppress dump. Recommended value is N. |
26 | blank |
|
27 | MODESET Flag | Flag used to control the application’s use of SVC107. |
28 | blank |
|
29-30 | TSO Flag | Flag used to designate that the application is to be called as a TSO command processor. ISPSTART is a TSO command processor. |
31-49 | reserved |
|
50-72 | Comment | Any comments used by the sites to describe the application. |
Task 2.6 Submit Batch JCL from BMC AMI DevX File-AID/MVS
For File-AID/MVS to submit batch jobs in the copy, reformat, search/update, and print functions, the CA Roscoe submit routine must be installed. This routine is shipped in the CA Roscoe source library as member name ETSSUB. We recommend that you read the documentation in this member for information on how to install it. The following figure shows sample JCL for assembling and link editing this exit.
Sample Assemble/Link-Edit JCL for ETSSUB Exit
Task 2.7 Override data set naming conventions
The default high-level qualifier for data sets is ROSCOE. If you want to override this high-level qualifier, Computer Associates provides a user exit, CLLEXIT. CLLEXIT should be modified, assembled, and linked into a library in the CA Roscoe startup procedure. You can also use CLLEXIT to override the TSO userid, which consists of a user PREFIX and ETSO.
If you are not using this exit, you must modify your existing security rules (CA ACF2, CA Top Secret, or RACF) to allow users to allocate data sets with the high-level qualifier, ROSCOE.