Macro Level Interpreter Presenter: Richard Verville

1
Macro Level InterpreterPresenter Richard
Verville

• WAVV 2009
• May 15-19
• Orlando

2
Is macro level code keeping you on CICS 2.3?
3
Agenda

• Support for Macro Level code is dropped
• Introducing Macro Level Interpreter (MLI)
• Previous CICS choices
• Supporting Legacy Applications with MLI
• How It Works
• Parameter Customization
• Activation
• Evolution of MLI
• Debuggers

4
History

• PROBLEM With support for Macro Level code going
  away, a cost effective solution for porting
  legacy applications was needed
• SOLUTION Macro Level Interpreter (MLI)
• conceived as Macro Level Adaptor or translator
• evolved to become much more

5
History

• MLI originally written for VSE in 1994
• MVS version available in 1995
• First customer
• Life/70 Application (Insurance package)
• Stairs (IBM package)
• Alpha Search (IBM package)
• PMS/Policy Management System (Insurance)

6
In the past, VSE offered two CICS versions

• CICS V2.3 (Coexistence release since VSE/ESA 2.4)
• - Command Level but still supported Macro Level
• - Minimal storage protection
• - Security using DFHSNT
• CICS Transaction Server (CTS since 1998)
• - CSA/TCA fetch protected, storage protection
• - New COBOL and new PL/1
• - Command Level only
• - Security - Basic Security Manager (no DFHSNT)
• - Discontinued PCT, PPT and most TCT definitions

7
In the past, VSE offered two CICS versions

• CICS V2.3 (coexistence was required if running
  legacy apps)
• - Macro Level, old COBOL, old PL/1
• - CSA and control block chaining
• - VSAM using ISAM compatibility
• - Command Level with Mixed Mode
• - BMS with MSETADR and MAPADR
• - BMS with pre-VS Maps
• - New COBOL w/calls to ASM Macro Level routines

8
The future leaves one CICS choice

• CICS Transaction Server

9
The future leaves one CICS choice

• CICS Transaction Server
• and if you have legacy applications
• Macro Level Interpreter
• - Macro Level, old COBOL, old PL/1
• - CSA and control block chaining
• - VSAM using ISAM compatibility
• - Command Level with Mixed Mode
• - BMS with MSETADR and MAPADR
• - BMS with pre-VS Maps
• - New COBOL w/calls to ASM Macro Level routines

10
Benefits of running legacy w/MLI under CTS

• Preserve legacy application investment ()
• No source code changes
• No recompilation
• No re-linking
• Easier CICS resource management (RDO)
• DSA below-the-line relief
• Application protection with STGPROT
• Application protection with REENTPROTECT
• Web enabling of legacy applications is possible

11
What MLI is

• Macro Level Interpreter is a Macro to Command
  Level Dynamic Translator plus much more

CICS Transaction Server
Macro Level Interpreter
Legacy Macro Level App 1
Legacy Macro Level App 2
Legacy Macro Level App 3
12
Example 1

• DFHSC TYPEGETMAIN,CLASSTERMINAL,LENGTH80
• MVC TCASCSNB,Y(80)
• MVI TCASCRS,X85
• L R14,CSASCNAC
• BALR R14,R14
• L RX,TCASCSA
• - 8500nnnnBBaaaaaa nnnnyyyy starts here
• EXEC CICS GETMAIN SET(POINTER) LENGTH(80)
• - Setup EXEC Interface call
• - Call CICS stub
• - MLI adds the prefix and trailer SAA length
• - 8500nnnnBBaaaaaa nnnnyyyy starts here

13
Example 2

• DFHFC TYPEGET,FILENAMEMSTRFIL
• - 8F00nnnnBBaaaaaa starts here
• EXEC CICS READ FILE(MSTRFIL) INTO(record) or
  SET(pointer)
• - 8F00nnnnBBaaaaaa starts here
• Macro Level Interpreter acts as an adapter
  between Macro Level programs and CICS
  Transaction Server

14
How It Works

• Easy Installation (20 mins)
• Parameter Customization (depends on customer
  environment)
• Easy online menus
• MLI supports Generic Name and character position
  masking
• Stored in a VSAM file
• Activation at PLTPI time

15
Parameter Customization
Macro Level Interpreter
15
16
Parameter Customization

• Which programs to monitor in MLI
• All macro level programs
• All mixed-mode programs (command and macro level
  mix)
• All command level using EXEC CICS ADDRESS
  CSA(pointer)
• Transaction with a mix of command level only AND
  macro level programs
• The first program of the transaction (MLI 141)
• Command level with EXEC CICS ADDRESS CWA(pointer)
• Not required if CWAMLI
• Required if CWA2 copies

17
Parameter Customization
Macro Level Interpreter
17
18
Parameter Customization
Macro Level Interpreter
18
19
Parameter Customization

• VSAM with ISAM compatibility
• FCT with VSAM files defined as
  RECFORM(,UNBLOCKED)
• ADD DDNAMES of files in MLI menus
• Application packages
• Some require pre-defined resources like PCT and
  FCT
• These can be scoped

20
Activation Time

• At PLTPI Activation
• Setup an application CICS V2 Environment
• CSA CWA
• Optional other pre-defined control blocks

21
Activation Time

• At Transaction Start Time
• On first occurrence of a macro level program
• Setup a CICS V2 TCA TWA (if required) TCT
  (if terminal attached)
• Gives control to macro level program
• Resource(s) used by macro programs are built as
  required
• No unused allocated storage
• Subsequent macro programs
• Build PPT entry
• Transaction end
• Release TCA TWA storage

22
Evolution

• Added support over time
• RENTPGMPROTECT
• STORAGE RESERVED option
• DIRECT LINK for highly used assembler programs
• Fast Path
• Old F-COBOL (Command or Macro Level)
• Old DOS/PLI (Command or Macro Level)
• Pre-VS BMS Map support

23
Debuggers

• Works with major debuggers
• MacKinney Systems/TRACK and XRAY
• Compuware/XPEDITOR
• CA/INTERTEST

24
Summary

• There is now one CICS option CICS Transaction
  Server
• MLI is a low cost alternative to porting legacy
  applications
• On z/OS, MLI supports CICS V4.1 and CICS TS 1.3
  4.1
• On z/OS, OS/VS COBOL DROPPED with TS 3.1
• VS/COBOL Interpreter (VCI) product runs OS/VS
  COBOL as is (no changes)
• Command and macro level OS/VS COBOL programs
  using MLI and VCI
• VCI is FCOBOL adaptable

25
Contact information

• Email richard_at_mackinney.com or
  sales_at_mackinney.com
• Web www.mackinney.com
• Phone [phone]

26
CICS/SignOnPresenter Rusty Swift
WAVV 2009 May 15-19 Orlando
CICS/SignOn
26
27
Are security issues keeping you on CICS 2.3?
CICS/SignOn
27
28
Agenda

• Support for DFHSNT is dropped
• Introducing CICS/SignOn
• Using CICS/SignOn
• How It Works
• Parameter Customization
• Activation

CICS/SignOn
28
29
History

• PROBLEM Support for DFHSNT is missing in CICS
  Transaction Server, and a cost and resource
  effective solution for porting User and
  Transaction Profiles was needed
• SOLUTION CICS/SignOn
• - originally targeted for VSE
• - many MVS customers because of ease of use

CICS/SignOn
29
30
History

• CICS/SignOn for VSE - 5/23/1997
• CICS/SignOn for MVS - 6/23/1997
• Current GA release 1.5 3/22/2007
• Current Beta Release 1.6 2Q 2009

CICS/SignOn
30
31
Goals

• What CICS/SignOn would address
• Identification (Userid, Username and Opid)
• Transaction Security
• Migration Tools
• Application Programming Interface
• Audit Logging
• What CICS/SignOn would NOT address
• Resource Security such as files and programs
• Leave to External Security Manager

CICS/SignOn
31
32
User Profiles

• Identification
• Userid 8 character
• Username 30-character (CESN)
• Opid 3-character (optional)
• Security
• User Keys 1-64 multiple keys can be selected

CICS/SignOn
32
33
User Profile
CICS/SignOn
33
34
Passwords

• Expiration Interval
• Days (1-366 )
• None
• Password rules
• Minimum Length (1-8)
• Required characters
• Alpha
• Special Character
• Numeric
• History
• Save 0-6 passwords

CICS/SignOn
34
35
Transactions

• Security
• CICS Keys 1-64
• DFHSNT restricted key selection to a single key
• CICS/SignOn allows multiple transaction keys
• If a user inputs a CICS transaction and any of
  the users keys match any of the keys defined for
  the transaction, then the user can execute the
  transaction.
• If none of the keys match, then the user gets a
  Security Violation which is logged.

CICS/SignOn
35
36
Transaction Profiles
CICS/SignOn
36
37
Installation Options
CICS/SignOn
37
38
Benefits of running CICS/SignOn under CTS

• Familiar concept for security
• Keys are similar to DFHSNT
• Migration from existing security
• Export/Import from CICS with DFHSNT
• VSE IUI
• In house or export from other security
• API allows home-grown security with benefits
• Password handling (rules, expiration, length,
  history)
• Audit logging
• Securing access from non-terminal resources (Web)
• VFYSEC provides authorization check using passed
  Tranid and Userid

CICS/SignOn
38
39
Summary

• There is now one CICS option CICS Transaction
  Server
• SignOn is a cost and resource effect solution for
  identification and transaction security

CICS/SignOn
39
40
Whats New at MacKinney

• CICS/Swap 4.8
• CICS/Menu II 1.1
• MacKinney Batch to CICS / IP 1.3

40
41
Contact information

• Email rswift_at_mackinney.com or sales_at_mackinney.com
  
• Web www.mackinney.com
• Phone [phone]

CICS/SignOn
41