20.6 Batch Keywords that are Not Recommended

The following table lists obsolete keywords from previous releases of DITTO that are still recognized by DITTO/ESA in batch mode. It is recommended that you use the indicated replacement, if any.

Function(s)

Keyword

Description

Replacement

 

 

 

 

BS, BT, CS, CT, FT, SS, ST, TFT,

BLKFACTOR=

Output blocking factor

RECFMOUT=

TS, TTR, VS, VT

 

 

B L K S I Z E =

 

 

 

 

TF

BLKFACTOR=

Output blocking factor

-

 

 

 

 

BS, CS, SS, TS, VS

CISIZE=

FBA control interval size

B L K S I Z E =

 

 

 

 

FT

M O D E =

Input record format

-

 

 

 

 

SP (VSE, CMS), SS, ST (VSE,

M O D E =

Input record format

RECFMIN=

CMS), SV, TC, TF, TFT, TRS, TS,

 

 

 

TTR, TV

 

 

 

 

 

 

 

BT, CT, ST (MVS), VS, VT

M O D E =

Output record format

RECFMOUT=

 

 

 

 

TTR

O U T M O D E =

Output record format

RECFMOUT=

 

 

 

 

TP, TRS

N B L K S =

Number of blocks

NLRECS=

 

 

 

 

FT

RECSIZE=

Record length for deblocking

-

 

 

 

 

VC, VL, VP, VRU, VS, VT, VV

S T A R T = K

VSAM start positioning by key

K E Y = k e y

 

POSITION=key

value

 

 

 

 

 

SET

TSOPRINT=

Print output destination

PRINTOUT=

 

 

 

 

SET

ASCII=YES

Translate from ASCII to EBCDIC

A S C I I = I N

 

 

 

 

Notes:

1. For the SP function, the MODE keyword is obsolete under VSE and CMS but still applies under MVS.

2. For the ST function, the MODE keyword is obsolete. Under VSE and CMS, use RECFMIN; under MVS, use

RECFMOUT.

20.7 DITTO/ESA Security

DITTO provides secure control of function authorization, either through RACF (or an equivalent security product) or through the DITSECUR exit.

DITSECUR is a customizable exit. It provides a DITS macro, which lets you define a table of user names or job names, DITTO-protectable resources (called profiles), and access levels.

OS/390, MVS, or CMS: If OS/390 Security Server, RACF 1.9 or later (or equivalent) is active, the System Authorization Facility (SAF) with the DITTO enhanced security facility is used for access control and authorization verification. Authorization is controlled by DITTO-specific profiles in the FACILITY class. If SAF with RACF 1.9 is not active at DITTO initialization time, all DITTO special security checks during that DITTO session are passed to the DITSECUR user exit (if any) instead of to SAF; if the DITSECUR module cannot be found, no security checks are done.

VSE: All DITTO special security checks during a DITTO session are passed to the DITSECUR user exit. If the DITSECUR module cannot be found, no security checks are done.

Chapter 20. DITTO 385

Page 409
Image 409
IBM OS/390 manual Batch Keywords that are Not Recommended, DITTO/ESA Security

OS/390 specifications

IBM OS/390, a versatile operating system, was a cornerstone in enterprise environments and played a pivotal role in mainframe computing. Released in the mid-1990s, OS/390 combined the strengths of IBM's MVS (Multiple Virtual Storage) with new features and enhancements, targeting scalability, reliability, and performance in demanding business applications.

One of the key features of OS/390 was its robust support for multiple users and processes. The system allowed thousands of concurrent users to access applications and data, ensuring high availability and minimizing downtime—a critical requirement for many large organizations. This scalability was supported through various enhancements in memory management and processor scheduling, enabling optimal resource allocation across diverse workloads.

OS/390 was known for its superior workload management capabilities. The Workload Manager (WLM) component allowed administrators to define service policies, specifying how system resources would be allocated according to the priority of tasks. This ensured that critical business processes received the necessary resources while less critical tasks were managed more flexibly.

Another significant characteristic of OS/390 was its commitment to security. The operating system provided comprehensive security features, including user authentication, data encryption, and auditing capabilities. This focus on security was vital for organizations handling sensitive data, ensuring compliance with regulations and safeguarding against unauthorized access.

OS/390 also supported advanced technologies that facilitated integration and development. The system included features like the IBM CICS (Customer Information Control System) for transaction processing and IMS (Information Management System) for database management. These technologies allowed organizations to build robust, high-performance applications tailored to specific business needs.

The ease of network integration was another strength of OS/390. With the advent of the Internet and global connectivity, OS/390 systems could easily interface with various network protocols, enabling businesses to operate in a connected world. This inclusion paved the way for many organizations to expand their capabilities and offer new services, driving digital transformation.

In conclusion, IBM OS/390 represented a significant advancement in mainframe technology, combining scalability, security, and robust workload management. Its rich feature set and support for critical enterprise applications solidified its role as a vital component of many organizations' IT infrastructures, ensuring they could meet their operational challenges head-on while supporting future growth. As technology continues to evolve, the legacy of OS/390 remains influential in the realm of computing.