Customizing Address Space Operations (IJTCFGxx)

This chapter will help you customize Cisco IOS for S/390 Address Space Operations. This is handled through the Infrastructure (IFS) environment. The IFS configuration member is IJTCFGxx.

IFS is a generic, multitasking, runtime environment for MVS system application address spaces. A system using IFS is an authorized, operator-started task or job that initializes as a subsystem (the primary JES must be initialized first to support SYSOUT requirements).

• IFSPARM Statement

Describes how to set timing services, time zone, tracename, and GTF ID

• Controlling Message Logging

Describes how to tailor message logging

• Authorization Key Information

Describes how to set component authorization key

• Setting SMF Parameters

Describes how to tailor parameters for SMF statements issued by Cisco IOS for S/390

• Setting Exit Points

Describes how to configure exit points

• Security Settings

Describes how to set Security

• POOLDEF Settings

Describes the pools available for Cisco IOS for S/390

IFSPARM Statement

The IFSPARM Statement in IJTCFGxx allows you to set GTF ID, timezone, and timing services.

IFSPARM Syntax

Syntax Description

IFSPARM Usage Notes

Timing Services

The IFS timing service, ITIME, allows interval timing to occur in modes other than primary task mode. The heart of the timing service is a fixed interval timer DIE that schedules SRBs in response to timers expiring.

Each timer is capable of tracking eight separate intervals. When the interval time expires, either an exit can be driven or an ECB posted.

The time interval (TIMER) for the DIE is configurable and has a range of 0.1 to 1 second. The time interval is specified in IJTCFG00. Note that specifying a large interval will decrease timer resolution. Specifying a very small interval will increase timer overhead.

Setting the Time Zone

To set the time zone for your system, specify your choice on the IFSPARM statement with the TIMEZONE parameter. For example, to set the time zone to Eastern Standard Time:

IFSPARM TIMEZONE (EASTERN)

Setting the GTF ID

To set the Generalized Trace Facility (GTF) identification value for Cisco IOS for S/390, specify the value on the IFSPARM GTFID statement. For example, to set the value as 17:

IFSPARM GTFID 17

Controlling Message Logging

The LOGGING statement in IJTCFGxx specifies the filtering for both print and console messages. Messages are filtered by component and level within component. For instance, specifying:

LOGGING PRINT((TC,RFEWISDT)) WTO((TC,FE)) 

LOGGING Statement

Syntax Description

Component and Message Type Definitions

Table 3-1 displays the WTO and PRINT components and their message type defaults, according to message destination. Message type is listed in the table and is specified as:

• R--Response

• F--Fatal

• E--Error

• W--Warning

• I--Informational

• S--Statistics

• D--Debugging

• T--Trace
  

Examples of Logging

To Write to the Operator (WTO) only messages for the IF component and type Debug, Error, Warning, and Informational messages for the IJ component, use this syntax:

WTO(NONE,(IF,ALL),(IJ,DEWI)) 

To print all type Debug and Error messages, but not anything for the SO component:

PRINT((ALL,DE),(SO,NONE))

To send everything to Write to Operator:

WTO(ALL)

To print nothing:

PRINT(NONE)

Note that parameters are processed left to right, as an example:

PRINT(ALL,(IJ,I),NONE)

The final NONE subparameter overrides the ones before it.

Authorization Key Information

AUTH information is required for Cisco IOS for S/390 operation. Both customer number and authorization key must be supplied. The initial component authorization key is provided at installation time and determines which Cisco IOS for S/390 components are authorized for your installation. The key has a built-in expiration date. Once the expiration date arrives, you will no longer be able to restart Cisco IOS for S/390 and you will need to contact Customer Support for a new key. After entering the component authorization key, you will need to stop and restart
Cisco IOS for S/390 for the authorization key to take effect.

Information on setting the component authorization key for initial startup is included in the
Cisco IOS for S/390 Planning Guide.

AUTH Statement Syntax

Syntax Description

Setting SMF Parameters

The TCP/IP stack generates SMF records at various processing points, such as connection establishment, connection termination, connection rejection, and failed connection attempts.

The INTERVAL parameter of the SMF statement determines the frequency (in minutes) with which periodic SMF statistics records, such as virtual storage utilization and driver statistics, are written.

SMF Statement Syntax

Syntax Description

SMF Usage Notes

Record Subtypes

The absence of an SMF statement in the configuration indicates that no SMF recording is performed.

SMF Examples

These examples show the usage of the SMF statement:

SMF TYPE(189) ALL
SMF TYPE(241) SUBTYPE(21)
SMF NONE

Setting Exit Points

Use the EXIT statement to define global user exits to Cisco IOS for S/390. Each EXIT statement defines an exit program to Cisco IOS for S/390, and specifies at which exit point(s) the program will be invoked.

EXIT Statement Syntax

Syntax Description

Using the IEFUSI Sample Exit

When a single Cisco IOS for S/390 region is to service many application users, it may require virtual storage beyond the default provided in most installations. Specifying a private area REGION size greater than 16 MB however, can cause storage allocation problems for system resources below the 16 MB line. In these instances it may be necessary to implement a user exit, such as IEFUSI, to ensure that adequate region values are supplied for Cisco IOS for S/390 operation. Source for a sample IEFUSI exit is provided in the TCPSAMP distribution data set.

Security Settings

This section describes how to configure the SECURITY Statement.

Security Statement Syntax

This is the syntax for the Security statement.

Syntax Description

POOLDEF Settings

The POOLDEF statement is used to define pools of control blocks necessary to run the API and put limits on API usage. Because the API is used internally by the domain name resolver, it must be set up properly for Cisco IOS for S/390 to run. The pool definitions specify an initial amount, an expansion amount, and a minimum amount to limit contraction. You can adjust these numbers to minimize expansion and contraction and improve efficiency. Refer to Defining Control Block Pools (POOLDEF Statement) for more specific information.