Creating a static application list
- Create members that contain the lists of applications to include in or exclude from the actual application list.
- Place the members in -RHILEV-.RLSPARM.
- Define the APPLIST commands in -RHILEV-.RLSCMDS that point to the members you created in -RHILEV-.RLSPARM. For more information, refer to the APPLIST command in the IBM CL/SuperSession Operator's Guide.
- Assign application lists to users through the user profile screens, as discussed in Assigning static application lists.
For example:
APPLIST LIST1 ID=PROGAPP
However, if you issue the APPLIST command dynamically, your new application list definition is temporary; it is not saved when you shut down and restart CL/SuperSession. To save your new definition, you must change the KLGCAPLT member in your commands library and then initialize the change through the operator facility.
Example 1: A simple application list
The following example creates an application list (PROGAPP) that contains two applications, TSOA and VM, and assigns the application list to the application programmers.
- You want to include the applications
TSOA and VM in your application list. Check that these applications are defined by the APPLDEF
command in member KLSCAPLS or KLGCAPLS of your runtime commands library. The command definitions
look something like this:
APPLDEF TSOA - DEST(TSOA) - DESC('TSO SYSTEM A') - POOL(TSOLGNHR)APPLDEF VM - DEST(VM) - DESC('VM SYSTEM A') - POOL(VIRT3270) - Create a member in -RHILEV-RLSPARM that lists the applications
you want to include in the application list. The application names
listed in the member are APPLDEF command session IDs.
The member list for this example looks like this:
TSOAVMIn this example, the member name is LIST1.
- Add the following command to member KLGCAPLT in -RHILEV-.RLSCMDS.
APPLIST LIST1 ID=PROGAPPThe
ID=parameter points to the APPLDEF entries in LIST1. Users with an application list ID of PROGAPP specified in their common profile would get the applications included in LIST1.To initialize your new application list definition, issue the following command through the operator facility:
KLGCAPLT - Assign the application list to users. For more information, see Assigning static application lists.
Example 2: The wildcard character
The following example creates an application list (PROGSYS) that contains three members and assigns the application list to the systems programmers.
- You want to include the VM application and all applications that begin with the characters TSO, CICS, and IMS. Check that these applications are defined by the APPLDEF command in member KLSCAPLS or KLGCAPLS of your commands library.
- Create the members LIST1, LIST2, and LIST3 in -RHILEV-.RLSPARM.
Each member will contain the applications you want to include in the
APPLIST command. For example:
LIST1
'TSO*'VMLIST2
'CICS*'LIST3
'IMS*'The wildcard character (
*) includes in the application list all definitions with session IDs beginning with TSO, CICS, and IMS. - Add the following command to member KLGCAPLT in -RHILEV-.RLSCMDS:
APPLIST LIST1 LIST2 LIST3 ID=PROGSYSThe
ID=parameter points to the APPLDEF entries in LIST1, LIST2, and LIST3. Users with an application list ID of PROGSYS specified in their common profile would get the applications included in those three lists (that is, the APPLDEF VM and all APPLDEFs starting with the character strings TSO, CICS, and IMS).To initialize your new application list, issue the following command through the operator facility:
KLGCAPLT - Assign the application list to users. For more information, see Assigning static application lists.
Example 3: The GROUP parameter for separate menu panels
You can also use the GROUP parameter to help you construct menus. All the authorized applications that share the same group number display together on each menu panel.
For example, if you have CL/SuperSession, you might want to list SINGLE applications on one menu panel, and MULTI applications on another.
- You want TSO, IMS, and CICS to be
SINGLE applications, and NetView and PROFS to be MULTI applications. That is:
- Member KLSCAPLS of -THILEV-.SKLSCMDS includes APPLDEF commands that define TSO, IMS, and CICS as SINGLE applications with GROUP=100.
- Member KLGCAPLS of -THILEV-.SKLSCMDS includes APPLDEF commands that define NetView and PROFS as applications with GROUP=200 and MULTSESS=YES.
- In -RHILEV-.RLSPARM, create a member named LIST1. In LIST1, list
the authorized applications by group, as follows:
GROUP=100 TSO IMS CICS GROUP=200 NETVIEW PROFS - Add the following command to -RHILEV-.RLSCMDS(KLGCAPLT):
APPLIST LIST1To initialize your new application list definition, issue the following command through the operator facility:
KLGCAPLT - Assign the application list to users. For more information, see Assigning static application lists.
Example 4: TYPE=EXCLUDE
You can create a member that contains only the applications you want to exclude from a group of users. This may be a more efficient way to use authorized application lists when you want to allow access to many applications and restrict access for only a few applications.
This example creates a list that contains only applications to which you do not want to give access.
- Verify that the applications you want to exclude are defined with the APPLDEF command in member KLGCAPLS or KLGCAPLS in -RHILEV-.RLSCMDS.
- Create member LIST1 in -RHILEV-.RLSPARM. For this example, LIST1
contains the following:
NETVIEW OMEGAMON VTPOPER - To define the application list, add the APPLIST command with the
TYPE=EXCLUDE parameter to member KLGCAPLT in your commands library,
as follows:
APPLIST LIST1 ID=TECHDOC TYPE=EXCLUDEThis list gives Technical Documentation (TECHDOC) access to all defined applications except NetView, OMEGAMON, and the operator facility (VTPOPER).
To initialize your new application list definition, issue the following command through the operator facility:
KLGCAPLT - Assign the application list to users. For more information, see Assigning static application lists.