IBM OS/390 User Manual

Product codes
Page of 673
IBML
VSE to OS/390 Migration Workbook
Cliff Bays ** Dave Greenough ** John Hutchinson
Dan Janda ** Kevin Jones ** Gilbert Saint-flour
International Technical Support Organization
http://www.redbooks.ibm.com
This book was printed at 240 dpi (dots per inch). The final production redbook with the RED cover will
be printed at 1200 dpi and will provide superior graphics resolution. Please see “How to Get ITSO
Redbooks” at the back of this book for ordering instructions.
SG24-2043-00

Summary of Contents of user manual for IBM OS/390

  • Page 1

    IBML VSE to OS/390 Migration Workbook Cliff Bays ** Dave Greenough ** John Hutchinson Dan Janda ** Kevin Jones...

  • Page 2

  • Page 3: VSE to OS/390 Migration Workbook

    IBML SG24-2043-00 International Technical Support Organization VSE to OS/390 Migration Workbook October 1998

  • Page 4

    Take Note! Before using this information and the product it supports, be sure to read the general information in...

  • Page 5: Contents

    Contents Figures . . . . . . . . . . . . . . . . . ....

  • Page 6

    2.7.5 Project Management . . . . . . . . . . . . . . . ....

  • Page 7

    4.3.13 Summary of MVS JCL Statements . . . . . . . . . . . . ....

  • Page 8

    6.1.11 CICS UPSI . . . . . . . . . . . . . . . ....

  • Page 9

    9.4.1 Network Definitions . . . . . . . . . . . . . . . ....

  • Page 10

    11.5 Other Differences . . . . . . . . . . . . . . . ....

  • Page 11

    Chapter 14. RPG II . . . . . . . . . . . . . . . ....

  • Page 12

    15.11.1 Storage Management in DOS . . . . . . . . . . . . . ....

  • Page 13

    18.5 Migration Issues . . . . . . . . . . . . . . . ....

  • Page 14

    25.2.1 Processor Requirements . . . . . . . . . . . . . . . ....

  • Page 15

    28.2.2 Managing Display Consoles . . . . . . . . . . . . . . ....

  • Page 16

    30.7.2 Tasks . . . . . . . . . . . . . . . . ....

  • Page 17

    32.5.1 Program Conversion . . . . . . . . . . . . . . . ....

  • Page 18

    C.1 Data Set Naming Guidelines . . . . . . . . . . . . . ....

  • Page 19: Figures

    Figures 1. VAE with Three Address Spaces . . . . . . . . . . . . ....

  • Page 20

    46. Loading a Sequential DAM File under VSE . . . . . . . . . . ....

  • Page 21: Tables

    Tables 1. Comparison of VSE Functions & Components to OS/390 Replacements 16 2. Who′ s Normal Activities are Affected? ....

  • Page 22

    xx VSE to OS/390 Migration Workbook

  • Page 23: Preface

    Preface The purpose of this document is to provide information and guidance to personnel involved in a VSE to OS/390...

  • Page 24

    Authors and Significant Contributors Riaz Ahmad IBM, Gaithersburg Boris Barth IBM, Germany Bette Brody IBM, Gaithersburg Jerzy Buczak IBM, Cary...

  • Page 25: Part 1. Planning the Migration - An Introduction

    Part 1. Planning the Migration - An Introduction  Copyright IBM Corp. 1998 1

  • Page 26

    2 VSE to OS/390 Migration Workbook

  • Page 27: Chapter 1. Why Customers Migrate

    Chapter 1. Why Customers Migrate This chapter discusses the following topics: 1.2, Traditional Reasons for Migrating 1.3, Functional Reasons for...

  • Page 28

    • Part 4, Converting VSE Utilities to OS/390 Utilities Conversion of the VSE utilities to their equivalent OS/390 utilities...

  • Page 29

    1.2.2 Mergers/Acquisitions As with corporate consolidations, mergers and acquisitions present an equal number of challenges when having to incorporate the...

  • Page 30

    ┌─────────────────────────────┐ ───── │ │ │ SVA - 2,304K │ │ │ │ │ ├─────────────────────────────┤ │ │ F1 - VSE/POWER...

  • Page 31

    ┌───────────────────────────────────────┐ ───── │ │ │ SVA - 2,304K │ │ │ │ │ ├───────────────────────────────────────┤ 5,184 K │ F1 -...

  • Page 32

    │ Static │ Dynamic │ │ Partitions │ Partitions │ ├──────────────────────────────────────────────┴───────────────┤ │ │ │ SVA (31-Bit) │ ├──────┬───────┬───────┬───────┬───────┬───────┬───────┬───────┤ │...

  • Page 33

    ┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┐ 2GB │ │ │ │ │ │ │ │ │ │ │ J │ C │ D │...

  • Page 34

    manner. That is, not concurrent with OS/390 and/or VM/ESA. This has lead users to ponder whether VSE is a...

  • Page 35

    OS/390 systems managed storage (DFSMS) provide enhanced system resource allocation and management. The Hierarchical Storage Manager (HSM), Removable Media...

  • Page 36

    1.3.5 Staff Availability In recent years S/390 application and system programming resources have become increasingly more difficult to acquire. This...

  • Page 37: Chapter 2. Sizing the Effort

    Chapter 2. Sizing the Effort This chapter discusses the following topics: 2.1, Introduction to Sizing 2.2, OS/390 Components/Products/Subsystems 2.3, What...

  • Page 38

    2.1.2 Areas of VSE and OS/390 Differences In order to properly assess and size the magnitude of the migration project,...

  • Page 39

    document is organized by source language type and goes into great detail at that level and includes the I/O considerations....

  • Page 40

    Sequential DASD files are compatible between VSE and OS/390. However, OS/390 does not support sequential (SAM) files located within...

  • Page 41

    Table 1 (Page 2 of 3). Comparison of VSE Functions & Components to OS/390 Replacements VSE OS/390 Comment and Reference...

  • Page 42

    Table 1 (Page 3 of 3). Comparison of VSE Functions & Components to OS/390 Replacements VSE OS/390 Comment and...

  • Page 43

    2.2.1 The OS/390 Operating Environment This section introduces the OS/390 operating environment. A publication entitled OS/390 Introduction and Release Guide...

  • Page 44

    • Distributed Computing − UNIX Application Services (Shell, Utilities, and Debugger) − UNIX System Services (included in the BCP)...

  • Page 45

    • Systems Management Services − DFSMS/MVS features (DFSMSdss, DFSMSrmm, DFSMShsm) − HCM − RMF − SDSF • Application Enablement Services...

  • Page 46

    • Data Facility Storage Management Subsystem Complementary functions of MVS/DFP and other individual products of the Data Facility family...

  • Page 47

    • System Modification Program Extended (SMP/E) SMP/E controls software changes to modules and macros in the operating system, using a...

  • Page 48

    in your environment. Each should be researched individually for installation applicability. 2.2.2 Subsystem Level Comparison/Affinity Various sections in this...

  • Page 49

    2.3.1.2 Automation VSE customers who use OCCF and/or ISV products to provide console automation functions will find enhanced function in...

  • Page 50

    2.4 Who is Affected by This Migration? 2.4.1 Job Roles and Normal Activities The following table which lists job roles...

  • Page 51

    5. Security 6. Performance 7. Capacity Planning 8. Testing 9. Backup/Recovery 10. Disaster Planning 11. Project Plan Development 2.5...

  • Page 52

    • OS/390 production is realized at an early time in the migration. When the first kernel is completed it...

  • Page 53

    A conversion team is normally chosen that will be dedicated to the project until its end. Included with this...

  • Page 54

    • Staff availability Deciding to use in-house staff as part of the migration makes it difficult to perform regular...

  • Page 55

    • Mass conversion - (Cortex-MS) • Program inventory - (IBM OPTI-AUDIT) 2.6 Educational Requirements 2.6.1 Introduction The educational requirements...

  • Page 56

    2.7 Scope of Work and Challenges When converting VSE applications to OS/390 several tasks have to be performed. The following...

  • Page 57

    2.7.2 Program Conversion The conversion of VSE application code to OS/390 is often (but falsely) believed to be the center,...

  • Page 58

    JCL: it is hidden inside the code (main or sub-program) associated with the step. Some of the file attributes...

  • Page 59

    flows. For example: You can have hundreds of files with the same name, for example ″WORK1″. WORK1 can exist...

  • Page 60

    The main challenge is the identification and classification of files for the migration. All files that will be used...

  • Page 61

    2.7.5 Project Management As with application inventory or JCL conversion, the management of a VSE to OS/390 conversion project is...

  • Page 62

    procedures. Most will simply try to reproduce with the new OS/390 product what they were doing in VSE with...

  • Page 63

    The purpose here is not to predict or estimate project costs but to identify major cost elements and any...

  • Page 64

    2.9.2 Key Documents and Other References • OS/390 V2R5 Planning and Installation , SK2T-2484 • CBIPO (System Pak) Custom Built...

  • Page 65: Chapter 3. Developing the Plan

    Chapter 3. Developing the Plan This chapter discusses the following topics: 3.1, Overview 3.2, Plan Components 3.3, Progressive versus Mass...

  • Page 66

    3.1.2.2 Take Advantage Of Conversion Tools and Automation Executing a migration with a mass conversion tool and automated processes...

  • Page 67

    SISRO and is no longer available, but deserves mentioning. The product documentation is helpful in that it provides a very...

  • Page 68

    The hired conversion specialists can be deployed for converting the in-house developed applications, and leading the overall migration effort,...

  • Page 69

    3.2 Plan Components 3.2.1 Approach For the purposes of providing more specific guidance for conversion projects, an approach to the...

  • Page 70

    If a mass migration/conversion tool is used someone will need to become familiar with the product and the mass...

  • Page 71

    3.2.2.3 Applications Programmers The applications programmers help the project manager to develop migrations procedures. They also test converted applications....

  • Page 72

    7 Training personnel to work with the OS/390 system. 8 Planning and installing the OS/390 system products. 9 Developing...

  • Page 73

    3.2.5 Education OS/390, and to some degree migration/conversion skills are crucial factors to the success of the migration project. Identification...

  • Page 74

    3.3.2 Historical Perspective The progressive conversion approach was the only solution available until the early 80s. More recently modern VSE...

  • Page 75

    separate operating systems, or the division of tape files and tape volumes between two tape managers running on two...

  • Page 76

    automated conversion defects. The switchover of an entire VSE production to OS/390 over a weekend cannot be improvised: it...

  • Page 77

    • Program clauses that restrict device independence are eliminated; that is, I/O assignment clauses removed from programs, placed in...

  • Page 78

    3.4.1 Project Schedule 3.4.1.1 Estimated Project Schedule The following is an estimated schedule for Project 2 - VSE to MVS...

  • Page 79

    3.4.1.3 Estimated Schedule for ABC Responsibilities The following is an estimated schedule for the ABC responsibilities. The actual schedule will...

  • Page 80

    3.4.2 Project Plan Example The actual schedule will be determined at Project 2 start, based on the completion of the...

  • Page 81

    Task Name ID 1998 Jan Feb Mar Apr May Jun Jul Aug Sep Oct ↓ Preparation Phases 01 Preparation...

  • Page 82

    3.4.2.2 Project Plan - Details ID Task Name Projected Actual Start End Start End 01 Project Approval 01/09/98 01/09/98...

  • Page 83

    ID Task Name Projected Actual Start End Start End 38 Perform Online Application Tests 06/07/98 08/16/98 39 Perform Online Network...

  • Page 84

    ID Task Name Projected Actual Start End Start End 72 Batch Application Tests Can Start 06/07/98 06/07/98 73 Perform Critical...

  • Page 85

    Task ID 1998 Jan Feb Mar Apr May Jun Jul Aug Sep Oct ↓ 01 ♦ Project A p...

  • Page 86

    62 Task ID 1998 Jan Feb Mar Apr May Jun Jul Aug Sep Oct VSE to OS/390 Migration Workbook ↓...

  • Page 87

    Task ID 1998 Jan Feb Mar Apr May Jun Jul Aug Sep Oct ↓ 43 Install Conversion Software 44...

  • Page 88

    64 Task ID 1998 Jan Feb Mar Apr May Jun Jul Aug Sep Oct VSE to OS/390 Migration Workbook ↓...

  • Page 89

    Task ID 1998 Jan Feb Mar Apr May Jun Jul Aug Sep Oct ↓ 85 Perform Production Tests 86...

  • Page 90

    66 VSE to OS/390 Migration Workbook

  • Page 91: Part 2. Converting the VSE Operating System to the OS/390 Operating System

    Part 2. Converting the VSE Operating System to the OS/390 Operating System  Copyright IBM Corp. 1998 67

  • Page 92

    68 VSE to OS/390 Migration Workbook

  • Page 93: Chapter 4. Job Control Language (JCL) Differences and Considerations

    Chapter 4. Job Control Language (JCL) Differences and Considerations The following sections describe the major tasks and considerations involved in...

  • Page 94

    OS/360 (PCP, MFT, MVT), the predecessors to MVS, and OS/390, specified Job Control Language but when JCL was needed...

  • Page 95

    Because there is no concept of permanent ASSGN or specification of standard label facilities, all resource requirements for each job...

  • Page 96

    Unlike VSE, the operator does not manipulate elements within a job stream, nor is he given the opportunity to...

  • Page 97

    4.2.1.7 Instream Data Both operating systems allow Instream Data in the middle of the JCL. This is data that...

  • Page 98

    Instream data will always follow an EXEC statement, and it is the responsibility of the executing program which is...

  • Page 99

    4.3.1.2 Data Driven Segmentation of Output An artifact of this sequential processing in VSE is that the spooling system extracts...

  • Page 100

    expansion for subsequent steps. In general, this is not possible in MVS JCL in the OS/390 environment. 4.3.2 JCL...

  • Page 101

    // PAUSE mount tape 123456 on an available drive. // ASSGN SYS005,CUU - or - // ASSGN SYS005,Drive The operator...

  • Page 102

    There is no equivalent function in OS/390. Many users write their own routine to replace the PAUSE function, if...

  • Page 103

    the conversion of the JCL which may have to be converted differently, depending on in which partition the job normally...

  • Page 104

    Understanding tool provides a graphical analysis of your VSE/ESA JCL job stream. You can find further details at the...

  • Page 105

    • For unlabeled tapes - the DEVADDR is the only link between the program and the JCL (there is...

  • Page 106

    In OS/390 the DATE function can be replaced by a control card, a parameter on the EXEC statement, or...

  • Page 107

    The VSE file-id (the label), which can be up to 17 characters long, is equivalent to the MVS DSname, which...

  • Page 108

    location for these. In OS/390 these duplicate names need to be resolved somehow. Refer to Chapter 5, “Disk and...

  • Page 109

    COND Parameter on the EXEC Statement To indicate the results of its execution, a program can issue a return code....

  • Page 110

    4.3.12 Comparison of VSE and MVS JCL - A Summary Below is a summary of VSE JCL statements and possible...

  • Page 111

    Table 7 (Page 2 of 2). VSE Job Control Statements Summary VSE Function MVS Equivalent Statement ON Causes specified action...

  • Page 112

    4.3.13 Summary of MVS JCL Statements Table 8. MVS Job Control Statements JCL Statement Purpose // command Enters an MVS...

  • Page 113

    4.4 JECL JECL is very important in VSE and is commonly used. The difficulty from a conversion standpoint is to...

  • Page 114

    Table 9 (Page 2 of 2). Overview of POWER JECL Statements POWER Function JES2 or MVS Equivalent Statement *...

  • Page 115

    Table 10 (Page 2 of 2). JES2 Control Statements Statement Purpose Comments /*ROUTE PRT Specifies the default print or...

  • Page 116

    job (all definitions available to all steps). OS/390 operation does not perform this ″carry-over″ (unique to VSE). 4.5.1 Sample...

  • Page 117

    4.5.2 Sample MVS JCL The task surrounding the conversion of JCL is more than mapping between VSE JCL using this...

  • Page 118

    A method that used two SYSOUT devices and output two DCBs in the program could also work. 3. PROGRAM2...

  • Page 119

    ** JOB JOB3 PRINT REPORT // EXEC PROGRAM2,SIZE=300K * $$ LST LST=SYS010,DEST=KCJONES 01 ENDICOTT * $$ LST LST=SYS010,DEST=HERBERT 02 BOEBLINGEN...

  • Page 120

    96 VSE to OS/390 Migration Workbook

  • Page 121: Chapter 5. Disk and Tape Storage Considerations

    Chapter 5. Disk and Tape Storage Considerations The VSE/SP and VSE/ESA systems and MVS and OS/390 systems have some conceptual...

  • Page 122

    DAM (or BDAM) Direct Access Method (or Basic Direct Access Method) -- used for disk devices. Still in some...

  • Page 123

    In OS/390, the application program linkage is handled through the SVC interfaces of the operating system. In either case,...

  • Page 124

    As it is desirable from both performance and integrity perspectives to separate user data sets into several user catalogs,...

  • Page 125

    functional components as well as RACF and DFSORT. For details, see section 1.3 in the DFSMS/MVS General Information , GC26-4900....

  • Page 126

    For more information on the benefits of system-managed storage, refer to the following publications: DFSMS/MVS General Information , GC26-4900...

  • Page 127

    DFSMS FIT is documented in the following IBM International Technical Support Organization publications (Redbooks): Get DFSMS FIT: Fast Implementation...

  • Page 128

    VOL1 v o l u m e label HDR1 and HDR2 data set header label EOV1 and EOV2 data...

  • Page 129

    • block length • record length • tape recording technique (seven-track only) • tape density • record format to...

  • Page 130

    statement. If a tapemark might precede the first data set and you specify the LABEL subparameter LTM, OS/390 tests...

  • Page 131

    A. VSE: With Tapemark Before Data Records ┌─────┬───────────────────┬─────┬─────┐ │ TM │ Data Records 1-n │ TM │ TM │...

  • Page 132

    5.5 DASD Similarities and Differences 5.5.1 Volume Interchangeability DASD file label conventions, requirements, and handling techniques differ between VSE and...

  • Page 133

    maintaining the accuracy of the Format-5 DSCB. The Format-5 DSCB , sometimes called the ″free space DSCB″, is used...

  • Page 134

    5.6 VSAM Differences 5.6.1 Introduction This section covers the differences between OS/390 VSAM and VSE/VSAM. In OS/390, the functions of...

  • Page 135

    • OS CVOL catalogs - these are a carry-over from the past (pre-OS/390) and are non-VSAM in structure. It has...

  • Page 136

    If access to a disk volume is lost, DFSMShsm can be used to perform a full-volume restore with update....

  • Page 137

    Item G023729 Last updated....: 10/13/1997 Abstract........: WSC FLASH 9741 VSAM CATALOG AND CVOL SUPPORT ENDS IN YR2000 Access to an...

  • Page 138

    When the system date is on or after 1/1/2000, the following reason code will be issued: ″34 - Explanation:...

  • Page 139

    IPL unit_address LOADPARM where LOADPARM bytes contain: bytes 1--4 5--6 7 8 ┌──────────────┬────────────┬─────────────┬─────────────┐ │ IODF DASD │ LOADxx │PROMPT...

  • Page 140

    The data set names of the user catalogs are contained in the OS/390 master catalog. Information necessary to locate...

  • Page 141

    Do not use JOBCAT or STEPCAT statements in OS/390 In predecessors of today′s OS/390 systems, it was not uncommon...

  • Page 142

    5.6.4.1 Accessing a VSE/VSAM Catalog from an OS/390 System Your migration plan might include the requirement to access VSE/VSAM...

  • Page 143

    5.6.4.3 Moving a VSAM Catalog to a Different DASD Type VSE/VSAM provided no facility for moving a catalog to...

  • Page 144

    • VSE/VSAM-managed SAM files − Default models − NOALLOCATION data sets − Implicit JCL DEFINE • Reusable data sets...

  • Page 145

    maintain the ″VSAM Ownership Bit″ in the VTOC, and the list of volumes owned by the catalog. Under VSE, multiple...

  • Page 146

    VSE/ESA Version 2.2 included new VSAM support for compression of VSAM data sets. The implementations of the two VSAM...

  • Page 147

    VSE SAM/VSAM data sets may also be converted to VSAM ESDS data sets. However, this is not recommended as it...

  • Page 148

    • acts as an ACB without RESET (add new records to existing file) • DISP=OLD overrides IDCAMS REPRO with...

  • Page 149

    in the VTOC. This equivalent function is performed in OS/390 VSAM by the AMS command ALTER REMOVEVOLUMES. The volume...

  • Page 150

    5.6.6.1 Cross-Region Sharing - Single CPU Environment Whenever a VSAM data set (ACB) is opened by more than one...

  • Page 151

    OS/390 VSAM Cross-Region SHR(4) VSE VSAM SHR(4 x) will refresh buffers from disk for every read I/O, and will also...

  • Page 152

    5.6.6.2 Single Region Data Set Sharing Single ACB Open - Multiple String Processing Full write integrity is provided within...

  • Page 153

    5.6.6.3 Cross-System and DASD Sharing You are in a cross-system sharing environment whenever you allow more than one copy of...

  • Page 154

    • Planning for Installation • DFSMSdfp Storage Administration Reference • Using Data Sets SHAREOPTIONS (X 4) Cross-system SHR(x 4)...

  • Page 155

    This provides cross address space sharing as well as journaling and recovery for the batch applications. It also allows...

  • Page 156

    perform a DFSORT COPY function to copy the temporary data set back into the original SORTIN VSAM data set....

  • Page 157: Chapter 6. CICS

    Chapter 6. CICS 6.1 Introduction This section is directed to individuals with a working knowledge of both CICS for VSE/ESA...

  • Page 158

    • Enhanced interface to the World Wide Web (WWW) adds support for 3270-based transactions. • The CICS Gateway for...

  • Page 159

    Please contact your local IBM Representative for more information on how to access IBM manuals via the INTERNET. Another...

  • Page 160

    application programs may be placed above the 16 megabyte line if they are written in VS COBOL II, PL/I,...

  • Page 161

    to SYSLST, access to CICS system control blocks. You should consider what impact each of the removed service or support...

  • Page 162

    Access to CICS system control blocks CICS management modules are provided as pregenerated systems for MVS. All the functional...

  • Page 163

    ┌────────────┐ ┌───────────────────┐ ┌───────────────────┐ │ ├────┤ Parameter manager │ │ Application ├────┤ │ │ domain (PA) │ │ domain (AP)...

  • Page 164

    CICS data table services RDO for VSAM files and LSR pools Some EXEC CICS system programming functions Autoinstall terminal...

  • Page 165

    Also, you should remove the parameters such as REUSE, RSL, and DEVICE from the DCT specification; these parameter are...

  • Page 166

    TCT review the entire table, particularly for BTAM changes. Add CONSLID=console designation for MVS Multiple Console Support (MCS). You...

  • Page 167

    JCT The CICS log manager does not support journal data sets, making the journal control table obsolete. The CICS...

  • Page 168

    Warning: When you migrate your CSD entries you must ensure that you do not copy over IBM supplied definitions...

  • Page 169

    TRANSACTION/RESTART this option now governs restart in two separate types of situation. TYPETERM/RECOVNOTIFY the scope of this parameter is...

  • Page 170

    ┌───────────┬───────────┬─────────────────────────────────────────────┐ │ Coupling │ OS/390 │ Log stream possibilities │ │ facility? │ Version │ │ │ │ 2.4?...

  • Page 171

    6.1.9 CICS System Program Interface and Exits 6.1.9.1 System Programming Commands CICS system programming interface (SPI) commands provide you with...

  • Page 172

    Your program must be in primary-space translation mode when you invoke the XPI. (For information about translation modes, see...

  • Page 173

    You must rewrite all user-replaceable modules except for DFHACEE, DFHUAKP, DFHXSP and DFHXSE user-replaceable modules, which are obsolete. Also,...

  • Page 174

    Bit 0 SYSIPT overrides yes or no. All overrides are passed as execution parameters to DFHSIP. Bit 1 This...

  • Page 175

    • RPG II is not a supported language for CICS/OS. RPG II programs should be converted to a supported application...

  • Page 176

    functions are provided by the Application Support Facility for MVS (ASF), 5685-043. Some CICS programs written in assembler language...

  • Page 177

    programs use CICS macros, which is very useful when you must determine your scope-of-effort. The CICS Application Migration Aid...

  • Page 178

    • handling output from CICS dumps. • handling output from CICS trace. • handling output from CICS statistics. •...

  • Page 179: Chapter 7. ICCF and TSO

    Chapter 7. ICCF and TSO DOS/VSE users of the Interactive Computing and Control Facility (ICCF) who migrate to OS/390 will...

  • Page 180

    You may choose to assign account numbers to your users for accounting or other purposes. This account number can...

  • Page 181

    7.1.2 LOGON Procedures In ICCF, a logon procedure may be specified in the user profile. This entry references an ICCF...

  • Page 182

    ICCF provides another level of security by defining ICCF libraries within DTSFILE as either PUBLIC, PRIVATE, or COMMON. All...

  • Page 183

    7.2.1 Accessing the System Since LOGON to TSO/E is dependent on the telecommunications access method used with TSO/E, the System...

  • Page 184

    Descriptive Qualifier Data Set Contents LOADLIST Output listing from loader OBJ Object module OUTLIST Output listing from OUTPUT command...

  • Page 185

    7.3 Executing Programs at a Terminal Both ICCF, TSO/E, and ISPF provide commands to compile, link-edit, and execute (or compile...

  • Page 186

    7.4 Submitting Jobs for Batch Execution ICCF allows users to submit jobs for batch execution through the SUBMIT procedure and...

  • Page 187

    7.4.1 Using Command Procedures Both ICCF and TSO/E provide the capability of storing frequently executed commands or lists of commands....

  • Page 188

    method over the first would be the total flexibility available in creating the tape input to IEBUPDTE and the...

  • Page 189

    &&IF &&PARAM1 EQ ′′ &&GOTO TAG3 &&SET &&VARBL3 &&PARAM1 &&LABEL TAG3 &&TYPE ENTER THE DESCRIPTIVE QUALIFIER FOR THE PDS TO...

  • Page 190

    &&OPTIONS 1100001 /LIB FULL ALL &&OPTIONS 0010001 /LOAD DTSPROCS /OPTION NOPROMPT &&OPTIONS 0010001 /LIST 1 1 IEBUPDTE &&IF &&RETCOD...

  • Page 191

    delete the first character of each record, and will delete the END OF MEMBER statements. The last statement placed...

  • Page 192

    168 VSE to OS/390 Migration Workbook

  • Page 193: Chapter 8. Databases

    Chapter 8. Databases 8.1 DL/I and IMS/VS DB Differences 8.1.1 Introduction This section addresses differences that exist between DL/I DOS/VS...

  • Page 194

    8.1.2 MVS System Requirements IMS/ESA requires a Type 2 SVC in the MVS nucleus and a Type 4 SVC in...

  • Page 195

    SEQFLD= SRCH= of XDFLD SEQVAL= SUBSEQ= of XDFLD SUPVAL= NULLVAL= of XDFLD SUPRTN= EXTRTN= of XDFLD The non-ACCESS statement...

  • Page 196

    8.1.5.4 Statement Compatibility All batch programs using the calls, GU - GHU - GN - GHN - GNP -...

  • Page 197

    8.1.5.10 Assembler Language Calls CALLDLI MF=E is not supported in IMS/ESA. 8.1.6 Utilities Equivalents of all DL/I utility programs...

  • Page 198

    8.1.7.2 Backout Utility/Disk Logging IMS/ESA supports both DASD and tape logging in batch. The archive utility DFSUARC0, is used...

  • Page 199

    8.1.8 Database Portability There are two fundamental approaches to making your DL/I databases available to IMS/ESA. One is to unload...

  • Page 200

    Recovery of DL/I - IMS/ESA compatible databases require special procedures. Image copy, change accumulation, and log files are not...

  • Page 201

    ┌───────────┐ │ DL/I DBD │ └─────┬─────┘ ┌───────────┐ │ │ MVS GEN │ │ └─────┬─────┘  │ ┌───────────┐ │ │...

  • Page 202

    8.1.9 DL/I Multiple Partition Support Conversion to IMS/ESA BMPs (Batch Message Processing programs) running under DBCTL should be considered as...

  • Page 203

    systems and security folks. This is not to say that differences do not exist, just that they are minor and...

  • Page 204

    8.2.1.3 Database Administrators (DBAs) As with the previous two groups discussed, there are really more similarities than differences between...

  • Page 205

    At the physical level, in DB2 each tablespace is stored in a pageset, which consists of one or multiple...

  • Page 206

    • http://www.software.ibm.com/year2000/db2-html SQL/DS Version 5 (proper name is DB2 for VSE Version 5) is Year 2000 compliant. 8.2.2.2 DRDA...

  • Page 207

    7 Migrate the user queries 8 Migrate user profiles and authorizations 9 Change operational procedures to reflect new backup/recovery, problem...

  • Page 208

    184 VSE to OS/390 Migration Workbook

  • Page 209: Chapter 9. Telecommunications Subsystems

    Chapter 9. Telecommunications Subsystems VSE and OS/390 platforms rely on the same set of communications products and protocols. Although the...

  • Page 210

    9.1.1 Product Installation The VTAM installation procedures for OS/390 are very different from those for VSE, since this is the...

  • Page 211

    (from ACF/SSP) and user-written VTAM exits. In our example STEPLIB points to the ACF/SSP library which contains the NCP...

  • Page 212

    The current supported levels of VTAM on VSE are V3R4 and V4R2. VSE VTAM V4R2 is available in three...

  • Page 213

     The 3174 with a Token-Ring or Ethernet adapter provides direct connection to Token-Ring and Ethernet LANs.  The...

  • Page 214

    without disruption. Sessions are simply taken over by a new copy of the application running in the same, or...

  • Page 215

    9.1.3.2 Programming Any coding done under VSE, such as VTAM exits, will almost certainly need rewriting (and will certainly...

  • Page 216

    9.2 ACF/NCP ACF/NCP in a 37XX controller may itself be completely independent of the operating system in the host, but...

  • Page 217

    • On the PCCU statement there are DUMPDS, MDUMPDS and CDUMPDS keywords which refer to various data sets which...

  • Page 218

    One of the reasons why TCP/IP is so popular is that there are many simple and useful standard applications...

  • Page 219

    9.4.2 TCP/IP Configuration First of all, configure the UNIX System Services (part of the OS/390 base product) in order to...

  • Page 220

    9.4.5.1 TCP/IP Applications using the Sockets API for Assembler VSE/ESA applications based on the SOCKET Assembler macro cannot be...

  • Page 221

    9.4.7 Bibliography VSE/ESA SC33-6601 TCP/IP for VSE/ESA User ′ s Guide SG24-2041 The Native TCP/IP Solution for VSE SG24-2040 VSE/ESA...

  • Page 222

    • your MQSeries based applications. In the next sections each of these topics will be addressed at a general...

  • Page 223

    The following list shows the required products with product numbers: • VSE/ESA Version 1.4 (5750-ACD) in ESA mode, with: ...

  • Page 224

    The following languages and compilers are supported for MQSeries applications: • Assembler  Assembler H (5668-962)  IBM High...

  • Page 225

    • install required CICS and IMS adapters • define queues • set up distributed queuing Customization is described in detail...

  • Page 226

    an MQSeries termination, and automatic resource resynchronization after a restart. The CICS adapter is supplied with MQSeries as the...

  • Page 227

    9.5.2 Networking Definitions You will have some other systems with an MQSeries product installed which are connected to your VSE/ESA...

  • Page 228

    4. namelists 5. process definitions 6. storage classes These objects can be manipulated, that is, defined, deleted, changed, by...

  • Page 229

    • for channel definitions under CICS/ESA find matching channel attributes in MQSeries Distributed Queuing Guide , SC33-1139 • define...

  • Page 230

    No special considerations apply to the compile and link step under VSE/ESA except that the product library which contains...

  • Page 231: Chapter 10. POWER and JES2

    Chapter 10. POWER and JES2 10.1 JES2 Introduction VSE uses POWER as a spooling system. MVS uses either JES2 or...

  • Page 232

    10.1.1.2 Time Event Scheduling for Jobs POWER supports the scheduling of job submission based on a one-time or repetitive...

  • Page 233

    can write your own using JES2 exit 1. (For PSF controlled printers, use PSF exits APSUX01 and APSUX02.) For...

  • Page 234

    POWER | JES2 ┌──────────────┐ | ┌──────────────┐ │ │ │ Checkpoint │─┐ │ Queue file │ | │ Data set...

  • Page 235

    JES2 initialization options described in Chapter 1 of the OS/390 JES2 Initialization and Tuning Guide . 10.2.2.1 The JES2...

  • Page 236

    • Network Job Entry (NJE) • Application Programming Interfaces • Accounting • RAS Characteristics • Testing Techniques Note: The...

  • Page 237

    10.3.3 Job Scheduling POWER and JES2 both manage the job input queue and manage the job selection for execution according...

  • Page 238

    10.3.3.2 Serializing Job Execution JES2 does not guarantee that jobs will run in the order they are submitted. If...

  • Page 239

    10.3.4 Output Service As with POWER, JES2 supports line-mode printers, whereas PSF controls AFP Printers. (See Chapter 11, “Advanced Function...

  • Page 240

    Table 13 (Page 2 of 2). POWER/JES2 Output Service Comparison Output Service POWER JES2 JES2 Comments Function End-of-Page sensing...

  • Page 241

    10.3.4.4 Printer Forms Alignment via PSETUP The PSETUP function is not supported in JES2. See 10.1.1.4, “Printer Forms Alignment via...

  • Page 242

    FCB Specification POWER users specify the full eight-character FCB name, whereas OS/390 users only specify the last four characters....

  • Page 243

    Table 15. POWER/ICCF, VM/CMS, and JES2/TSO Functional Comparison Interactive POWER - VM - CMS JES2 - TSO/E Interfaces ICCF...

  • Page 244

    RMT BSC and SNA RJE Workstations R(nn).RD(n) RJE Workstation Readers R(nn).PR(n) RJE Workstation Printers R(nn).PU(n) RJE Workstation Punches See...

  • Page 245

    10.3.7.1 NJE Definitions Use the following JES2 initialization statements to define your NJE network and networking options: TPDEF BSC...

  • Page 246

    Job Information Services Current Job Identification If you have code that is called by an MVS application, you can...

  • Page 247

    Subsystem Version ID You can obtain version-specific information about a subsystem with SSI function code 54. See Using the...

  • Page 248

    NJE Network Management Records JES2 records the following information reflecting network events: • SMF 55 Network Signon • SMF...

  • Page 249

    • Operator Monitor Spool Utilization • Spool Full Condition - $S SPL upon warning (Output limits minimize this) •...

  • Page 250

    Table 17 (Page 1 of 2). POWER Macro to JES2 Parameter Mapping POWER Description JES2 Parm Comment or Parm...

  • Page 251

    Table 17 (Page 2 of 2). POWER Macro to JES2 Parameter Mapping POWER Description JES2 Parm Comment or Parm Recommendation...

  • Page 252

    Table 18. PLINE MACRO to JES2 Parameter Mapping PLINE Description JES2 LINE Comment Parameter Parameter ADDR= Unit address of...

  • Page 253

    Table 19 (Page 2 of 2). PRMT MACRO to JES2 Parameter Mapping PRMT Description JES2 RMT Comment Parameter Parameter MSGSPCE...

  • Page 254

    10.4.1.5 Define NJE Nodes This table shows the conversion of POWER PNODE parameters to JES2 parameters. Table 21. PNODE...

  • Page 255

    Table 23. POWER Exit to JES2 Exits POWER Description JES2 Exit Comment Exit JOBEXIT Job input - Scan JCL...

  • Page 256

    10.4.3.1 Queue Management Commands Table 24. Queue Management Commands POWER PWR Function JES2 Command Short Command Code Form Verb...

  • Page 257

    10.4.3.3 Control Commands Table 26. Control Commands POWER PWR Function JES2 Command Short Command Code Form Verb PACCOUNT J Save...

  • Page 258

    Table 27 (Page 2 of 2). Network Management Commands Function POWER JES2 Display Network I ALL $DCONNECT, $DPATH Connections...

  • Page 259: Chapter 11. Advanced Function Printing and Print Services Facility/ MVS

    Chapter 11. Advanced Function Printing and Print Services Facility/MVS 11.1 Introducing PSF/MVS Print Services Facility (PSF) is the Advanced Function...

  • Page 260

    • 11.2, “Installing and Configuring PSF/MVS” • 11.3, “Setting up AFP Resources” on page 240 • 11.3.4, “Migrating Print...

  • Page 261

    11.2.2.2 TCP/IP Attached Printers Unlike VSE, OS/390 also supports printing to TCP/IP connected printers. There are several ways to...

  • Page 262

    11.2.5 FSS Procedure and PRINTDEV Statements Below is the sample FSS proc shown in the PSF/MVS Systems Programming Guide ....

  • Page 263

    Table 30. PRINTDEV Parameter Comparison PSF/VSE OS/390 Equivalent Parameter Description and Comment PRINTDEF Parameter ASA (not necessary) ASA control records...

  • Page 264

    11.3 Setting up AFP Resources PSF/MVS supports resources in the system libraries defined in the PRINTDEV statement, and dynamically on...

  • Page 265

    PSF/MVS utility APSRMARK against these ported VSE resources in order for PSF/MVS to consider these resources ′marked′ for printer...

  • Page 266

    OS/390 Dynamic Allocation and Output Descriptor Macros Traditional SYSOUT attributes can be specified on the DYNALLOC macro. AFP attributes...

  • Page 267

    Table 31 (Page 2 of 2). VSE - OS/390 Command Comparison VSE or POWER Command JES2 Command Comment PSTOP...

  • Page 268

    11.5.3 Accounting PSF/VSE uses the POWER ACCOUNT=AFP (or =ALL) parameter to capture accounting information about printing through PSF. In OS/390,...

  • Page 269

    11.6.5.4 Internet Locations The IBM Printing Systems Company Web Site at http://www.printers.ibm.com/ contains a “Tools” directory along with product...

  • Page 270

    246 VSE to OS/390 Migration Workbook

  • Page 271: Part 3. Converting VSE Languages to OS/390 Languages

    Part 3. Converting VSE Languages to OS/390 Languages  Copyright IBM Corp. 1998 247

  • Page 272

    248 VSE to OS/390 Migration Workbook

  • Page 273: Chapter 12. COBOL

    Chapter 12. COBOL 12.1 Introduction This chapter introduces IBM COBOL for OS/390 and VM (program number 5648-A25), which is the...

  • Page 274

    12.1.2 Comparison of IBM COBOL Compilers DLL Support Extensions for: Object-Oriented COBOL C Interoperability Intrinsic Functions Intrinsic Functions Amendments to...

  • Page 275

    Under VSE/ESA version 1 release 4, and VSE/ESA version 2 and above, the COBOL compilers available were DOS/VS COBOL,...

  • Page 276

    Table 32. Useful COBOL Publications Form Publication Title Number COBOL for OS/390 and VM Compiler and Run-Time Migration Guide...

  • Page 277

    12.3.2 DOS/VS COBOL Programs Containing REPORT WRITER Statements COBOL for OS/390 and VM does not support the REPORT WRITER statements....

  • Page 278

    For example: 01 RECORD-A PIC X(4). 01 FILLER REDEFINES RECORD-A. 10 RECA-FIRST PIC 9(2). 10 RECA-SECND PIC 9(2). Using...

  • Page 279

    12.4.2 ENVIRONMENT DIVISION 12.4.2.1 CONFIGURATION SECTION - SPECIAL-NAMES Paragraph UPSI Switch Processing In DOS/VS COBOL and COBOL for OS/390 and...

  • Page 280

    ASSIGN Clause The format of the ASSIGN clause has become simpler. COBOL for OS/390 and VM may sometimes allow...

  • Page 281

    12.4.4.1 Program Termination There are three COBOL program termination statements: • EXIT PROGRAM • GOBACK • STOP RUN There...

  • Page 282

    12.4.5.2 File Attribute Mismatches DOS/VS COBOL file open processing does not always check that the attributes of the file...

  • Page 283

    12.5.1 VS COBOL II CICS Programs COBOL for OS/390 and VM and OS/390 do not support CICS macro-level programs. If...

  • Page 284

    12.8 Compiler Options This section discusses some of the compiler option considerations when converting from the various VSE COBOL compilers...

  • Page 285

    DOS/VS COBOL Option COBOL for OS/390 and VM Equivalent (If Any) BUF=nnn BUFSIZE(nnn) CATALR/NOCATALR NAME/NONAME CLIST/NOCLIST OFFSET/NOOFFSET COUNT/NOCOUNT None FLAGE/FLAGW...

  • Page 286

    COBOL for OS/390 and Comments VM Option PGMNAME(COMPAT) If compiling with COBOL for OS/390 and VM use this option...

  • Page 287

    VS COBOL II Option Comments FDUMP/NOFDUMP COBOL for OS/390 and VM does not provide the FDUMP compiler option. For...

  • Page 288

    ALPHABET END-COMPUTE FALSE OVERRIDE ALPHABETIC-LOWER END-DELETE FUNCTION PACKED-DECIMAL ALPHABETIC-UPPER END-DIVIDE GLOBAL PADDING ALPHANUMERIC END-EVALUATE INHERITS PROCEDURE-POINTER ALPHANUMERIC-EDITED END-IF INITIALIZE...

  • Page 289

    12.9.2 Reserved Word Considerations for VS COBOL II and COBOL for VSE/ESA There are two reserved words in COBOL for...

  • Page 290

    266 VSE to OS/390 Migration Workbook

  • Page 291: Chapter 13. Assembler

    Chapter 13. Assembler 13.1 Assembler Products In OS/390, the High-Level Assembler for MVS and VM Program Product (5696-234) is required...

  • Page 292

    The selection of a particular option of MVS may require redesigning the application programs. In addition, a program logic...

  • Page 293

    13.2.1.1 Initiation Under VSE, main programs (those programs that are invoked by the operating system directly) are not required to...

  • Page 294

    PROGA START PROGB CSECT PROGC CSECT BALR (VSE) (VSE) USING . . . . . . ST 13,SAVEB+4 ST...

  • Page 295

    contained in register 13. Therefore, you must specify a save area to receive the registers. PROGA START PROGB CSECT PROGC...

  • Page 296

    VSE CALL Entrypoint ,(PARAMETER LIST) (15) MVS CALL Entrypoint ,(ADDRESS),VL (15) ,ID=number Call is used the same way in...

  • Page 297

    Under MVS, the RETURN macro returns control to the calling program and signals normal termination of the returning program. Control...

  • Page 298

    When this program received control from MVS Reg. 13 contained address of MVS save area. Reg. 14 contained address...

  • Page 299

    region in register 1. The first eight bytes of the communication region is the date in the form MM/DD//YY (month/day/year)...

  • Page 300

    is an explicit request. If a separate module is requested, then the additional virtual storage requirement is implicit in...

  • Page 301

    programs. You can also leave the tests in your program and provide an UPSI constant in your COMRG macro...

  • Page 302

    (MVS) LOAD EP=PROGB LOAD the load-module LR 15,0 pass address CALL (15),parm1,parm2 invoke PROGB FETCH Macro The VSE FETCH...

  • Page 303

    The MVS TIME macro has an additional operand MIC,address that causes the time of day to be returned in the...

  • Page 304

    ┌─────┬──────┬──────────────────────────────────────────┐ │ VSE │ PDUMP│ address1 , address 2 ,MFG=area │ │ │ │ r1 r2 (S,area) │ │...

  • Page 305

    CANCEL Macro ┌───────┬───────────┬────────────────────────────────┐ │ VSE │ CANCEL │ ALL │ ├───────┼───────────┼────────────────────────────────┤ │ MVS │ ABEND │ comple─ion code │ │...

  • Page 306

    CHKPT Macro ┌─────┬────────┬────────────────────────────────┐ │ │ │ res─ar─ address │ │ │ │ SYSnnn, (r1) │ │ │ │ ,...

  • Page 307

    13.2.2 Multitasking Macros Under VSE, when you specify asynchronous processing at system generation time, the multitasking group of macros is...

  • Page 308

    ENTRYPOINT In VSE, it defines the storage address of the entry point of the subtask. The entry point must...

  • Page 309

    terminate normally. MVS does not permit the subtask to issue its own DETACH. If neither ECB nor ETXR is specified...

  • Page 310

    as complete. This number may be less than or equal to the number of ECBs specified in the macro....

  • Page 311

    13.2.3 Interrupt Handling Routines Interrupt routines take care of the interval timer, abnormal conditions, and operator communication interrupts. Abnormal condition...

  • Page 312

    Wait Handling This method of using the interval timer allows you to set the timer and wait for the...

  • Page 313

    The preceding combination of VSE macro instructions allows you to execute a routine when an operator attention interrupt occurs...

  • Page 314

    13.2.4.2 RELPAG Macro The MVS PGRLSE and PGSER RELEASE macros have functions similar to the VSE RELPAG macro. ┌─────┬────────┬─────────────────────────────┐...

  • Page 315

    • CATALOG=YES/NO - NO is used if the catalog is to be processed as a normal cluster with normal GET/PUT...

  • Page 316

    • MSGLEN=length - The length of the MSGAREA specified above. The size of a message is 128 bytes. •...

  • Page 317

    13.2.6.1 List and Execute Macro Forms The list and execute forms of data management macro instructions, used together provide the...

  • Page 318

    13.2.6.4 I/O Error Checking When an input/output error occurs under MVS, a user-written synchronous error routine (SYNAD) can be...

  • Page 319

    VSE DTFCD MVS DCB DSORG=PS DEVADDR = SYSxxx DDname (in DD statement) IOAREA1 = xxxxxxxx BUFNO = 1 or IOAREA1...

  • Page 320

    OPEN CARD VSE GET CARD,WORK . CLOSE CARD CARD DTFCD DEVADDR=SYSIPT,IOAREA1=CARDIN1, C IOAREA2=CARDIN2,EOFADDR=END, C WORKA=YES CDMOD WORKA=YES OPEN CARD...

  • Page 321

    VSE DTFPR MVS DCB DSORG=PS DEVADDR = SYSxxx DDname (in DD statement) IOAREA1 = xxxxxxxx BUFNO = 1,MACRF =(..M..)...

  • Page 322

    Note: You can specify any number of dcbaddresses and associated options in the OPEN macro instruction. CLOSE Macro VSE...

  • Page 323

    Notes: 1. The codes are as follows: ┌──────┬────────────────────────────────────────────────────────────┐ │ VSE │ MVS (BSAM only) │ ├──────┼────────────────────────────────────────────────────────────┤ │ REW │ No...

  • Page 324

    Notes: 1. VSE: The address is that of a four-byte storage location containing the required record identification in the...

  • Page 325

    FEOV Macro VSE FEOV filename (1) MVS FEOV dcbaddress , REWIND (1-12) LEAVE The basic functions of the VSE and...

  • Page 326

    VSE DTFMT MVS DCB DSORG=PS BLKSIZE = nnnnn BLKSIZE = nnnn DEVADDR = SYSxxx N/A EOFADDR = xxxxxxxx EODAD...

  • Page 327

    OPEN TAPE VSE PUT TAPE . CLOSE TAPE RECORD1 DS 2000C TAPE DTFMT DEVADDR=SYS005,TYPEFLE=OUTPUT, C FILABL=STD,IOAREA1=RECORD1, C HDRINFO=YES,IOREG=(5), C...

  • Page 328

    VSE DTFDI MVS DCB DSORG=PS DEVADDR = SYSxxx DDname (in DD statement) IOAREA1 = xxxxxxxx BUFNO = 1 or...

  • Page 329

    Options Option 1 Option 2 QSAM INPUT ,REREAD OUTPUT ,LEAVE UPDAT ,DISP EXTEND INPUT EXTEND OUTPUT ,REREAD BSAM INOUT ,DISP...

  • Page 330

    MVS GET dcbaddress area address PUT (2-12) (2-12) (1) (0) CNTRL Macro There is no equivalent for the VSE...

  • Page 331

    ACC Specifies that the problem program accepts the block causing the error. This action can be specified when a data...

  • Page 332

    Notes: 1. The decbaddress must be the same as used in the READ or WRITE macro (decbname). 2. If...

  • Page 333

    NOTE Macro VSE NOTE filename (1) MVS NOTE dcbaddress (1-12) The MVS NOTE macro is valid only for BSAM and...

  • Page 334

    VSE DTFSD MVS DCB DSORG=PS BLKSIZE = nnnn BLKSIZE = nnnn EOFADDR = xxxxxxxx EODAD = xxxxxxxx DELETFL =...

  • Page 335

    OPEN SAMFILE . WRITE SAMFILE,SQ,DATA VSE CHECK SAM FILE . CLOSE SAMFILE SAMFILE DTFSD DEVADDR=SYS005,DELETFL=NO, C DEVICE=3340,RECFORM=FIXUNB, C BLKSIZE=8O,TYPEFLE=WORK,VERIFY=YES...

  • Page 336

    VSE DTFDA MVS DCB DSORG=DA BLKSIZE = nnnn BLKSIZE = nnnn DEVICE = nnnn UNIT = (in DD statement)...

  • Page 337

    ERROR VSE MVS Byte Bit Byte Bit Wrong-length record 0 1 2 1 Nondata transfer error 0 2 2...

  • Page 338

    WRITE Macro KEY VSE WRITE filename , ID (1) RZERO AFTER AFTER,EOF MVS WRITE decbname,type, dcbaddress , area address,...

  • Page 339

    13.2.6.12 Track and Record Addressing Track Addressing In VSE and MVS, you can make track references by using either the...

  • Page 340

    Record Addressing by KEY Supply the key as follows: VSE READ filename,KEY KEYARG and KEYLEN operands are required in...

  • Page 341

    Reference Method VSE MVS Relative Track Assumed if DSKXTNT is Assumed if OPTCD does not Addressing specified. RELTYPE=HEX contain R...

  • Page 342

    Reference VSE MVS Method: Relative Track Assumed if DSKXTNT is Assumed if OPTCD does not Addressing specified. RELTYPE=HEX contain...

  • Page 343

    OPEN (DAMFILE,(OUTPUT)) . . WRITE DECBADD,DI,DAMFILE,DATA,′ S′ , KEY,BLOCKADDRESS CHECK DECBADD . . DAMFILE DCB ..MACRF=(WICS),DSORG=DA,OPTCD=R... . . Figure...

  • Page 344

    OPEN (DAMFILE,(OUTPUT),TAPE,(INPUT)) GET GET TAPE . WRITE DECB1,SF,DAMFILE,(10) CHECK DECB1 . WRITE DECB2,SD,DAMFILE,DUMMYREC CHECK DECB2 . TAPE DCB ..........

  • Page 345

    Notes . OPEN (R0FILE,(OUTPUT),TAPE) WRITER0 WRITE DECBR0,SZ,R0FILE STC 15,RC (1) CHECK DECBR0 CLI RC,X′ 0 0 ′ BE WRITER0...

  • Page 346

    Notes RC DS CL1 WC DC CLI′ 0 ′ COUNT DC H′ 0 ′ THREE DC H′ 3 ′...

  • Page 347

    4. Since 37 records (blocks) will fit on one 3340 track, the three-byte key (ranging from 001-999) is divided...

  • Page 348

    To create a file using this method under MVS, you would normally initialize each track by writing a capacity...

  • Page 349

    When updating records, it is convenient to use the list and execute forms of READ/WRITE macros rather than the standard...

  • Page 350

    In MVS, to make a request for feedback, insert the letter F in the type code of a READ/WRITE...

  • Page 351

    13.2.6.14 PIOCS EXCP is often used in VSE in association with card files (for example, SYSIPT), print files (for example,...

  • Page 352

    DTFPH Macro Figure 54 shows the correspondence between the operands of the DTFPH macro and their MVS equivalents: DTFPH...

  • Page 353: Chapter 14. RPG II

    Chapter 14. RPG II 14.1 Migration from VSE to OS/390 The aim has been to make it easy to convert...

  • Page 354

    • With the device type PRINTER or with a blank entry for device type and symbolic device SYSLST (DOS/VS...

  • Page 355

    Direct access method files are processed with BDAM. VSAM files are handled in the same way as under VSE....

  • Page 356

    332 VSE to OS/390 Migration Workbook

  • Page 357: Chapter 15. PL/ I

    Chapter 15. PL/I The PL/I language compiler implemented on VSE is the DOS PL/I Optimizing Compiler (5736-PL3). In MVS, the...

  • Page 358

    15.1.2 Extended Precision Available with the MVS version of the PL/I compiler, extended precision floating point allows working with variables...

  • Page 359

    15.1.6 Parameters Passed to a Main Program It is possible to pass parameters to a PL/I program having the option...

  • Page 360

    15.2.1.2 DYNBUF In MVS the buffers are always acquired dynamically by the compiler. This option is therefore suppressed. 15.2.1.3...

  • Page 361

    15.2.2.5 SMESSAGE or LMESSAGE This option requests the compiler to supply messages in short or long format. This is...

  • Page 362

    15.2.3.4 SPIE STAE As user-program execution options they authorize PL/I to issue SPIE and STAE macros to intercept program...

  • Page 363

    15.4.1 Not Supported in MVS 15.4.1.1 MEDIUM Physical and logical unit type. This option is ignored by the MVS compiler....

  • Page 364

    15.4.1.10 NOTAPEMK NOLABEL These are specified in the JCL in the LABEL parameter of the DD statement. 15.4.2 Supported...

  • Page 365

    15.5.2.1 SORT FIELDS SORT data: a character string containing an image of the SORT statement. This card image must begin...

  • Page 366

    15.5.2.9 SORT TECHNIQUES The user can specify a particular sort technique: PEER Peerage sort BALN Balanced CRCX Criss-cross OSCL...

  • Page 367

    15.6.3 PLICANC Another possibility offered in the MVS PL/I optimizer is the ability to annul a request for an automatic...

  • Page 368

    15.7.3 Options Specific to MVS The options A, E and 0 are used only in a multitasking environment: A Dump...

  • Page 369

    15.9.2 Automatic Restart An automatic restart in the case of an ABEND can only take place if an ABEND is...

  • Page 370

    large enough ISA to reduce subsequent GETMAINs and FREEMAINs to zero (or some very small number). This is one...

  • Page 371

    15.12.7 PL/I Return from ON-units and CICS Transaction Backout If a CICS transaction ABEND begins but is intercepted in a...

  • Page 372

    348 VSE to OS/390 Migration Workbook

  • Page 373: Chapter 16. FORTRAN

    Chapter 16. FORTRAN 16.1 VS FORTRAN in OS/390 VS FORTRAN is the compiler and library to use on OS/390. VS...

  • Page 374

    350 VSE to OS/390 Migration Workbook

  • Page 375: Chapter 17. Language Environment (LE)

    Chapter 17. Language Environment (LE) 17.1 Introduction This chapter introduces OS/390 Language Environment (program number 5645-001). OS/390 Language Environment is...

  • Page 376

    17.1.2 Conceptual Differences between LE/VSE and OS/390 Language Environment There are some conceptual differences between LE/VSE and OS/390 Language Environment....

  • Page 377

    17.2.2 Useful Publications Table 35 lists some publications that you may find useful when planning your conversion. Table 35. Useful...

  • Page 378

    17.3.2 COBOL for VSE/ESA COBOL for VSE/ESA is an LE/VSE-conforming language. If your COBOL applications are written in COBOL/VSE, they...

  • Page 379

    Table 36. REPORT and ISASIZE Options, C/370 and DOS PL/I REPORT option, C/370 The information supplied by the REPORT...

  • Page 380

    Table 38 on page 356 lists some migration considerations you should be aware of when migrating from VS COBOL...

  • Page 381

    Table 40. DOS PL/I Migration Considerations Migration Comments Consideration Dumps The output produced by PLIDUMP is different when running under...

  • Page 382

    17.4.6 VS FORTRAN If your VSE applications are currently written in VS FORTRAN, you must convert them to another version...

  • Page 383

    Table 41 (Page 2 of 2). ILC Migration Considerations To Migrate: You Need To: A phase containing one or...

  • Page 384

    ABPERC In LE/VSE you can specify the abend code to the option ABPERC in one of three formats. These...

  • Page 385

    TEST The IBM defaults for the TEST option differ between LE/VSE 1.1, LE/VSE 1.4 and OS/390 Language Environment. They are:...

  • Page 386

    17.5.1.2 Run-time Options and LE/VSE 1.4 and Later Releases The following options were introduced in LE/VSE 1.4, but their...

  • Page 387

    17.5.1.3 Recommended Settings for Options The recommended settings for options for OS/390 Language Environment are described in the OS/390 Language...

  • Page 388

    Table 43 (Page 2 of 2). Option Recommendations Differing between LE/VSE 1.4 and OS/390 Language Environment Language Option Recommendation...

  • Page 389

    In OS/390 Language Environment a sample job, CEEWHLLX, is provided that contains an SMP/E USERMOD to replace the IBM-supplied...

  • Page 390

    CEE5ABD CEE5GRN CEE5MDS CEE5SPM CEE5CIB CEE5GRO CEE5MTS CEE5SRC CEE5CTY CEE5LNG CEE5PRM CEE5SRP CEE5DMP CEE5MCS CEE5RPH CEE5USR CEE5GRC Figure 56....

  • Page 391

    The recommended settings for run-time options for CICS, are the same for OS/390 Language Environment and for LE/VSE, with...

  • Page 392

    368 VSE to OS/390 Migration Workbook

  • Page 393: Chapter 18. Procedure Language REXX

    Chapter 18. Procedure Language REXX The REstructured eXtended eXecutor language, or REXX language, is a versatile, easy to use structured...

  • Page 394

    18.4 Environments The system under which REXX procedures run is assumed to include at least one environment for processing commands....

  • Page 395

    18.4.3 TSO/E Environment TSO/E provides among others the following host command environments: • TSO allows you to invoke TSO/E commands...

  • Page 396

    18.5.1 REXX and SAA Issuing commands to the surrounding environment is an integral part of REXX. REXX is the only...

  • Page 397: Part 4. Converting VSE Utilities to OS/390 Utilities

    Part 4. Converting VSE Utilities to OS/390 Utilities In addition to this part of the book on converting utilities,...

  • Page 398

    374 VSE to OS/390 Migration Workbook

  • Page 399: Chapter 19. SORT

    Chapter 19. SORT This chapter addresses considerations for migrating to the OS/390 Sort product, DFSORT (5740-SM1) from the VSE Sort...

  • Page 400

    //MYJOB JOB ... //SORTIT EXEC PGM=SORT //SYSOUT DD SYSOUT=* //SORTIN DD DSN=... //SORTOUT DD DSN=... //SYSIN DD * SORT...

  • Page 401

    19.2 Control Statements DFSORT was designed to be functionally compatible with Sort/Merge at the control statement level, and for the...

  • Page 402

    • ERASE: Can be used with no changes. DFSORT ignores ERASE. Use a security product, such as RACF, to...

  • Page 403

    19.3 Additional DFSORT/VSE Migration Considerations DFSORT/VSE is based on and replaces Sort/Merge. It offers additional features not available in Sort/Merge....

  • Page 404

    • p,m,Y2x: Must be removed. DFSORT terminates if this operand is specified. p,m,Y2x can be specified in the OUTREC...

  • Page 405: Chapter 20. DITTO

    Chapter 20. DITTO Data Interfile Transfer, Testing, and Operations Utility (DITTO) is IBM′s best known storage media and data maintenance...

  • Page 406

    double asterisk (**) represents any number of characters in any number of qualifiers. Under VSE and CMS, an implicit...

  • Page 407

    Function Description Replacement SD, SDD Split-Cylinder Disk Dump - SDU SAM to Diskette - SIS SAM File to ISAM...

  • Page 408

    20.4 DITTO Function Code Synonyms The following table lists supported synonyms for DITTO function codes. Function Synonym(s) Description BS BQ,...

  • Page 409

    20.6 Batch Keywords that are Not Recommended The following table lists obsolete keywords from previous releases of DITTO that are...

  • Page 410

    386 VSE to OS/390 Migration Workbook

  • Page 411: Chapter 21. VSAM Backup/ Restore

    Chapter 21. VSAM Backup/Restore 21.1 VSAM Backup/Restore The following describes the methods and utilities used in OS/390 as compared to...

  • Page 412

    Operations: 1. Handle several VSE/VSAM files with a single command, either with a generic name or as files of...

  • Page 413: Chapter 22. Librarian

    Chapter 22. Librarian Both VSE and OS/390 have facilities to help you define, organize, and manage libraries of system data....

  • Page 414

    functional enhancements of the VSE Librarian. The Librarian functions can be invoked through a console or through job streams...

  • Page 415

    22.1.2 OS/390 Library Management The Software Configuration Library Manager (SCLM), a component of ISPF, introduces an object-oriented approach to library...

  • Page 416

    392 VSE to OS/390 Migration Workbook

  • Page 417: Chapter 23. LISTLOG/PRINTLOG - Printing Log Streams

    Chapter 23. LISTLOG/PRINTLOG - Printing Log Streams Both VSE and OS/390 provide facilities to capture system log data in a...

  • Page 418

    23.3.1 SYSLOG The system log (SYSLOG) is a data set residing in the primary job entry subsystem′s spool space. It...

  • Page 419

    23.5 JES2 System Data Sets - Job Log and System Messages The job′s hardcopy log and any system messages related...

  • Page 420

    396 VSE to OS/390 Migration Workbook

  • Page 421: Chapter 24. VSE/Fast Copy and OS/390 DFSMSdss

    Chapter 24. VSE/Fast Copy and OS/390 DFSMSdss The following briefly describes VSE/Fast Copy and the comparable OS/390 component, DFSMSdss. 24.1...

  • Page 422

    24.2 DFSMSdss - OS/390 Component DFSMSdss has four functions to help you manage your DASD space: • COMPRESS Compresses your...

  • Page 423: Part 5. Setting Up the Migration Environment

    Part 5. Setting Up the Migration Environment  Copyright IBM Corp. 1998 399

  • Page 424

    400 VSE to OS/390 Migration Workbook

  • Page 425: Chapter 25. Prepare the Migration Environment

    Chapter 25. Prepare the Migration Environment 25.1 Introduction Setting up the OS/390 environment, similar to setting up the VSE environment,...

  • Page 426

    25.2 Install and Configure Required Hardware VSE and OS/390 operating systems both use the same basic S/390 hardware platform, although...

  • Page 427

    A beginning rule of thumb shows 12 volumes of 3390-3 (or equivalent) DASD, allocated as follows: (Your mileage will...

  • Page 428

    OS/390 through cross-domain resource definitions. They are also useful for data transfer via NetView FTP or NJE. OSA (Open...

  • Page 429

    25.2.5.4 Data Transfer and NJE You will want to set up an NJE connection between the two systems for...

  • Page 430

    25.3.1.2 SoftwareXcel SystemPac/MVS The SystemPac installation offering is a world-wide offering similar to SIE, but without on-site assistance by...

  • Page 431

    25.3.2.2 CBPDO Custom-Built Product Delivery Option is a software delivery package consisting of uninstalled products without integrated service. You...

  • Page 432

    Related Redbooks Here is a list of DFSMS ″Fast Implementation Techniques″ (FIT) Redbooks: • DFSMS FIT: Fast Implementation Techniques...

  • Page 433

    Other MVS Names There are many other objects which require naming in OS/390. Here is just a sample: •...

  • Page 434

    25.4.2.1 Enforcing Installation Standards You will continue to refine the standards developed above, and should use RACF to protect...

  • Page 435

    25.4.2.5 Setting Up Critical Operations Procedures You should set up, test, and document procedures that are critical to the smooth...

  • Page 436

    25.4.3 Documentation You should already have the following planning publications which are available as part of the OS/390 Installation Planning...

  • Page 437

    25.5 Customize Your New OS/390 System Before you start using your new OS/390 system, you must complete the installation and...

  • Page 438

    IBM′s comprehensive testing does not replace the need for this testing in your own environment. Here are some sample...

  • Page 439

    25.5.1.4 NetView FTP Access You can also use the same VTAM connections to send bulk data between the two...

  • Page 440

    25.5.2.3 Tailoring Other Components Other features of OS/390, such as JES2 are described in other chapters of this book....

  • Page 441

    25.5.3.3 Independent Software Vendor Products If you chose to use ISV (non-IBM) products, you should recognize the additional implementation, customization,...

  • Page 442

    418 VSE to OS/390 Migration Workbook

  • Page 443: Chapter 26. Test Environments

    Chapter 26. Test Environments This chapter describes the different needs for test systems during and after the migration to OS/390....

  • Page 444

    Application Development & Test System A system that is expected to stay up without disruption at least during ″normal...

  • Page 445

    3 Final System Test on OS/390 Just before you migrate to OS/390, you should run all your important applications...

  • Page 446

    evaluate each of the alternatives mentioned, but that would be beyond the scope of this book, and not necessarily...

  • Page 447

    Recent advances in the PR/SM LIC have solved some of the real storage management difficulties encountered in the past...

  • Page 448

    central storage as if it were running natively on the processor. While storage is dedicated to a particular virtual...

  • Page 449

    installed. This support exists in VM/ESA Version 2 Release 3 on Multiprise 2000, 9672 G3, and G4 processors. If you...

  • Page 450

    VM/ESA distribute that communication capability among the guest images using virtual channel to channel devices. Similarly, any DASD that...

  • Page 451

    new vendor package that runs under AIX. As guests of VM/ESA, all three can run efficiently while sharing one...

  • Page 452

    VM/ESA and its customers exclusive technical advantages not available in any other operating system platform. Operations Management With PROP...

  • Page 453

    distributed servers. VSE, OS/390, TPF, AIX and others are discovering the enormous value VM/ESA brings to the table. DB2 Guest...

  • Page 454

    26.3.3.5 OS/390 Guest Considerations The considerations for defining OS/390 guests are no different from those associated with defining VSE...

  • Page 455

    26.5.1 OS/390 Maintenance Environment Early in the project a test SMP/E environment needs to be designed and built. This process...

  • Page 456

    26.6 Shared DASD vs. Cloned DASD The issue of whether to share DASD volumes and data sets between systems is...

  • Page 457

    26.6.2 Shared DASD between VSE and OS/390 (vs. Cloned DASD) As mentioned in the previous section, it is risky to...

  • Page 458

    434 VSE to OS/390 Migration Workbook

  • Page 459: Part 6. Running Your OS/390 System

    Part 6. Running Your OS/390 System  Copyright IBM Corp. 1998 435

  • Page 460

    436 VSE to OS/390 Migration Workbook

  • Page 461: Chapter 27. Orienting ICCF Users to TSO/ISPF

    Chapter 27. Orienting ICCF Users to TSO/ISPF There are many facets of VSE/ICCF that are done differently in OS/390. TSO...

  • Page 462

    also build lists of personal data sets. Personal data set lists are a good way to group (by project,...

  • Page 463

    • finding specific character strings in the data, changing them to other character strings or to exclude the lines...

  • Page 464

    27.1.4 Creating and Executing ISPF Applications Since ISPF is a dialog manager, many other products have written dialogs, connect themselves...

  • Page 465

    For more information see the OS/390 ISPF Software Configuration and Library Manager Developer ′ s Guide, OS/390 ISPF Software...

  • Page 466

    442 VSE to OS/390 Migration Workbook

  • Page 467: Chapter 28. Orientation to OS/390 Console Operation

    Chapter 28. Orientation to OS/390 Console Operation 28.1 Introduction There are enough differences between VSE and OS/390 operations to warrant...

  • Page 468

    • NetView Consoles • TSCF Consoles • Programmed Operator Subsystems This chapter will only deal with MCS and SDSF...

  • Page 469

    28.2.2.2 Display Areas These may be handy for operating a console with a lot of traffic, when you want...

  • Page 470

    28.2.3.2 Using SDSF for System Operation Below is the Primary Option Menu for SDSF showing you the basic panels...

  • Page 471

    28.3 Controlling the OS/390 System The OS/390 System commands are only a subset of the commands necessary to operate the...

  • Page 472

    28.3.3 Stopping the System There are several ways to stop or halt the system, and important subsystems. Here is a...

  • Page 473

    28.4.3 JES2 Devices Devices such as printers, punches, TP lines, and spool offload tapes can be allocated by JES2 dynamically....

  • Page 474

    28.5.1.1 MVS Commands Use the DISPLAY JOBS, J, A, or TS command to display information about current system activity,...

  • Page 475

    28.5.2 Controlling Time Sharing Users TSO/E users logon through terminals controlled by VTAM. You can use MVS or JES2 commands...

  • Page 476

    28.6 Managing Remote Operations As with VSE, remote systems and workstations can communicate through NJE or RJE via commands and...

  • Page 477

    $D MMn,′Please restart my printer′ Send a message to the operator on member n See JES2 Commands for details....

  • Page 478

    $D PATH(node_name) Display the path(s) to another node $D Nxx.′$D NODE(yy)′ Send a command to node xx to display...

  • Page 479: Chapter 29. Orientation for Utilities

    Chapter 29. Orientation for Utilities 29.1 IEBxxx or IEHxxx There are many utilities in OS/390 provided by DFSMS/MVS to assist...

  • Page 480

    • Reblock or change the logical record length of a data set. • Copy user labels on sequential output...

  • Page 481: Chapter 30. Systems Management Philosophy and Methodology

    Chapter 30. Systems Management Philosophy and Methodology Many VSE installations have small staff and have mature systems which are changed...

  • Page 482

    In many smaller computer installations, where at most a few people are involved in system changes, ad-hoc and informal...

  • Page 483

    • Places a stronger emphasis on service, as it promotes keeping one′s ″eye on the ball.″ • Provides more...

  • Page 484

    well, and the disciplines should include those to avoid ″the hole in the boat isn′ t on my side...

  • Page 485

    • Scheduling - occurs during the planning process, and aids in identifying conflicts and impacts, and determines target dates...

  • Page 486

    30.3.2 Tasks The problem management process includes the following: • Problem determination - the detection of the loss or impending...

  • Page 487

    update and manage problem management records, but use of a searchable database technology, such as DB2 or a custom...

  • Page 488

    ⇒ Establishing performance specifications and policies. • Performance execution and measurement ⇒ Response time monitoring - what is the...

  • Page 489

    Projected trends recorded in this way represent accurate growth measurements. These projections can be used to identify needed changes...

  • Page 490

    • Automated Operations - handles the complex operations job scheduling procedures to ensure that work is completed in a...

  • Page 491

    the MPF list can be customized to carry this out. For other automation tasks, IBM provides several products to support...

  • Page 492

    The following books contain planning information for automation and illustrate sample automated operational scenarios using IBM Systems Management products:...

  • Page 493

    30.6.3 Methodology In VSE, users with security needs frequently use one or another vendor security package, as IBM provides only...

  • Page 494

    • Configuration creation - building and maintaining a configuration description that is resource-specific. • Updating configuration information - providing...

  • Page 495

    30.8 Asset Management 30.8.1 Overview Asset management provides for managing the information technology inventory of resources, including both physical and...

  • Page 496

    30.9.2 Tasks Accounting management activities include the following: • Measurement - collection of actual usage and service-level data. • Cost...

  • Page 497: Chapter 31. Diagnosing System Problems

    Chapter 31. Diagnosing System Problems 31.1 Problem Determination Tools Several tools are available under OS/390 to help the system programmer...

  • Page 498

    • Reduce the size of a stand-alone dump. You can reduce the size of a stand-alone dump as you...

  • Page 499

    31.4 JES2 Diagnosis There are some JES2 mechanisms that can be used for problem determination. • $TRACE: JES2 internal tracing...

  • Page 500

    addition, IPCS can be used to format the in-storage LOGREC buffers while analyzing a dump. 31.8 SYSLOG All system...

  • Page 501

    No matter what utility is used to perform the backup and recovery of a catalog, the process isn′t complete...

  • Page 502

    31.9.3 DFSMSrmm The diagnosis document for DFSMSrmm is the DFSMS/MVS DFSMSrmm Diagnosis Guide , SY27-9615. It documents how to obtain...

  • Page 503: Part 7. Converting your Applications

    Part 7. Converting your Applications  Copyright IBM Corp. 1998 479

  • Page 504

    480 VSE to OS/390 Migration Workbook

  • Page 505: Chapter 32. Conversion Process

    Chapter 32. Conversion Process Converting a data processing installation from VSE/ESA to OS/390 is a complex process that affects all...

  • Page 506

    • Refer to MVS MS - Production Standards , LB11-8080. 6 Translating the programs, taking into account the differences...

  • Page 507

    2 Conversion Phases • Initial Trial Conversion • Regression Testing and Repeated Trial Conversions 3 Implementation Phases • Actual...

  • Page 508

    32.1.2 Prerequisites There are two key requirements that need to be satisfied before embarking on a migration: 1. The source...

  • Page 509

    32.1.3.5 Migrate the SNA Network Early If the migration plan includes converting an SNA communications network, then consider migrating ownership...

  • Page 510

    32.1.3.7 Two Phase Approach The migration project can be broken into a few logical pieces that may help its...

  • Page 511

    32.2.2 Mass Conversion Overview / Benefits Mass conversion is the major distinction of the CORTEX-MS process. It results in a...

  • Page 512

    32.2.2.1 Automated Conversion There are several ways to automate some or all of the conversion. The automation that Cortex-MS...

  • Page 513

    OS/390. Therefore, it is not required to freeze or follow up development, enhancement, or maintenance of applications during the...

  • Page 514

    routines must allow users to custom adapt the tools to specific local conversion requirements. These requirements, not addressed by...

  • Page 515

    functional descriptions of batch applications (standards and system independent). EZ-PCL (Easy PCL) A PC/MS-Windows based graphic user interface (GUI)...

  • Page 516

    • Inventory Validation • Translate the Languages/Programs • Translate the JCL • File Transfer 32.2.5.1 Inventory Validation The Cortex...

  • Page 517

    32.3 Mass Conversion Phase Overview Built on the principles of mass, automated, and repetitive conversion, a mass conversion project is...

  • Page 518

    • Refer to Chapter 3, “Developing the Plan” on page 41 for information on project staffing, assignments and responsibilities....

  • Page 519

    • At project start • Before the start of online application tests • Before the start of batch application...

  • Page 520

    The key terms associated with determining your application inventory are: 1. Determination 2. Collection 3. Supply 4. Analysis and...

  • Page 521

    be performed on the VSE side and then sent to OS/390. The determination and collection procedures are developed once...

  • Page 522

    names. This is because naming conventions can facilitate or impair the implementation of OS/390 system components (such as DFSMS)...

  • Page 523

    and parameters), and library members for control cards. This is because many of the VSE names are syntactically incorrect...

  • Page 524

    References you can consult for additional information about the conversion specification phases include: • Refer to Appendix C, “DFSMS...

  • Page 525

    32.4.4.2 Design the MVS Target Output All the material in this book, including the charts that show functional comparisons...

  • Page 526

    • tailoring and custom modifying the conversion tools through installation options and exit routines according to the conversion specifications...

  • Page 527

    cannot be converted entirely automatically, and for which the unresolved conversion requirement cannot be addressed through VSE positioning. 32.5...

  • Page 528

    VSE 2.1 for the EXEC statement), or change the program′s logic to read and process a ″control record″ which...

  • Page 529

    work, cataloged temporary, handoff, backup, transmit, master sequential, master VSAM, and so on. File classification is a large JCL-related...

  • Page 530

    The first trial conversion starts with a complete fresh supply of the VSE conversion inventory. Every three to four...

  • Page 531

    • Simulated production (or acceptance) tests: in conjunction with batch production tests • Network and performance tests with actual connection...

  • Page 532

    • Application personnel should be made responsible for providing test data, and for evaluating, and approving application test results....

  • Page 533

    test phase will have its own test plan. The key application development people at the installation must be involved when...

  • Page 534

    • Migrating copies of VSE production files, needed for regression tests, to OS/390 • Migrating copies of VSE production...

  • Page 535

    The large number of inactive and non-critical or obsolete tape files is not migrated. They are either eliminated, or...

  • Page 536

    32.5.6.1 Online Unit Testing Prior to this task, an online test plan, and possibly detailed test scripts, have been...

  • Page 537

    the beginning of staggered and overlapping testing. Online system testing may overlap batch unit testing. 32.5.7 System Testing In...

  • Page 538

    the third job in the sequence is missing due to being treated as a temporary data set. The management...

  • Page 539

    Job Simulation The goal is to get through as many days as possible. It is a comfort to know...

  • Page 540

    32.6.1.1 Converting the Development Material This is the code that the systems programmers are working on. It is recommended...

  • Page 541

    procedure in order to apply jobset maintenance concurrently with maintenance to VSE production. 32.6.2.2 Final Program Conversion There are...

  • Page 542

    32.6.3.2 Additional Switchover Tasks These tasks may also need to be addressed during switchover: • RJE workstation configurations •...

  • Page 543: Chapter 33. Conversion Services and Tools

    Chapter 33. Conversion Services and Tools The actual process of converting JCL and programs from VSE to OS/390 can be...

  • Page 544

    AMS is an IBM Business Partner • Call 1-800-482-6267 or, • Contact AMS through IBM 33.2 Conversion Tools 33.2.1...

  • Page 545

    • Program status • Program usage • File cross-referencing • Job cross-referencing 33.2.2.1 Product Highlights IBM OPTI-AUDIT for VSE Version...

  • Page 546

    • REPORT 1 - ACTIVE phases (lists all ′executed′ phases by library). • REPORT 2 - INACTIVE phases (lists...

  • Page 547

    33.2.3.1 Product Positioning COBOL and CICS Command Level Conversion Aid for VSE Release 1 is positioned as a COBOL migration...

  • Page 548

    Driver: This component reads the COBOL source program, extracts copy members from the input source file, and executes the...

  • Page 549

    33.2.5 Computer Associates 33.2.5.1 CA-Convertor CA-Convertor is a comprehensive system to manage and implement the conversion from VSE to MVS...

  • Page 550

    33.2.6.1 Recovery/SRC This is the basic service provided by SRC. The basic recovery utilizes a proprietary technology that generates...

  • Page 551: Part 8. Migration Experience

    Part 8. Migration Experience  Copyright IBM Corp. 1998 527

  • Page 552

    528 VSE to OS/390 Migration Workbook

  • Page 553: Chapter 34. Customer Migration Example

    Chapter 34. Customer Migration Example This chapter describes an actual user experience with migration. Since every customer environment is unique,...

  • Page 554

    34.3 Inventory • 1500 COBOL programs - mix of DOS/VS COBOL and COBOL II • 2600 RPG programs • 80...

  • Page 555

    34.5 Duration Due to the data sharing requirements, the availability requirements, and, in general, the dynamic environment of the business,...

  • Page 556

    about the same after switchover, with MVS showing a couple of percentage points higher. Since the workload at this...

  • Page 557: Part 9. Appendixes

    Part 9. Appendixes  Copyright IBM Corp. 1998 533

  • Page 558

    534 VSE to OS/390 Migration Workbook

  • Page 559: Appendix A. Education Information

    Appendix A. Education Information The task of providing the right training, to the right people, at the right time, at...

  • Page 560

    It is recommended that a class on TSO and ISPF, to help navigate through panels, be taken prior to...

  • Page 561

    A.3 Who will Provide the Training? Hiring a skilled MVS person for the migration, whether temporary or permanent, helps with...

  • Page 562

    538 VSE to OS/390 Migration Workbook

  • Page 563: Appendix B. Mapping ISV Products and Functions

    Appendix B. Mapping ISV Products and Functions This is a frequent topic of discussion with customers considering migrating. How a...

  • Page 564

    Table 46 (Page 2 of 3). S/390 Software Product Mapping Vendor Vendor Product I B M Product PID #...

  • Page 565

    Table 46 (Page 3 of 3). S/390 Software Product Mapping Vendor Vendor Product I B M Product PID # Primary...

  • Page 566

    542 VSE to OS/390 Migration Workbook

  • Page 567: Appendix C. DFSMS Naming Conventions

    Appendix C. DFSMS Naming Conventions This chapter was written by John Tyrrell of IBM′s Storage Systems Division. John is one...

  • Page 568

    There are two basic pieces of information that one should be able to obtain from the data set name:...

  • Page 569

    individuals keep a standard LOGON ID, and change the set of filters instead of the IDs. As an example of...

  • Page 570

    − E3380D − E3380S − E3990M3 − E3990M2 The above example would allow various filtering techniques the flexibility of...

  • Page 571

    readable, such as, a file called MASTER.PAYROLL.WEEKLY. This might be just too tempting to your average system hacker. A...

  • Page 572

    C.3.2 Application Location If this application ever got moved to another site, then all of the data sets would have...

  • Page 573

    C.3.6 Access Method At one point in time, many installations adopted a policy of distinguishing VSAM data from non-VSAM data....

  • Page 574

    usability of the system and the need to manage it differently based on what set of data this actually...

  • Page 575

    within the data set name so that ACS Routines can easily ascertain one piece of data from another. The...

  • Page 576

    552 VSE to OS/390 Migration Workbook

  • Page 577: Appendix D. Special Notices

    Appendix D. Special Notices This publication is intended to help customers and IBM technical personnel to migrate from VSE to...

  • Page 578

    including these reference numbers is to alert IBM customers to specific information relative to the implementation of the PTF...

  • Page 579

    SupportPac System/360 System/370 System/390 SystemPac Systems Application Architecture SystemView Virtual Machine/Enterprise Systems Architecture VisualAge VisualLift VM/ESA VM/XA VSE/ESA VTAM The...

  • Page 580

    OMEGAMON is a trademark of Candle Corporation ONC is a trademark of Sun Microsystems, Incorporated Open Software Foundation is...

  • Page 581: Appendix E. Related Publications

    Appendix E. Related Publications The publications listed in this section are considered particularly suitable for a more detailed discussion of...

  • Page 582

    E.2.1 Planning Books The following hard-copy books are part of the OS/390 Installation Planning Kit which can be ordered by...

  • Page 583

    E.3 Other Publications Book Title Publication Number RACF General Information GC23-3723 Getting Started with DFSORT SC26-4109 Get DFSMS FIT: Fast...

  • Page 584

    560 VSE to OS/390 Migration Workbook

  • Page 585: How to Get ITSO Redbooks

    How to Get ITSO Redbooks This section explains how both customers and IBM employees can find out about ITSO redbooks,...

  • Page 586

    How Customers Can Get ITSO Redbooks Customers may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about redbooks,...

  • Page 587

    IBM Redbook Order Form Please send me the following: Title Order Number Quantity First name Last name Company Address City...

  • Page 588

    564 VSE to OS/390 Migration Workbook

  • Page 589: A

    Glossary Access Method Services (AMS). A utility program Numerics (named IDCAMS) that defines VSAM data sets (or files), allocates space...

  • Page 590

    MO:DCA-P is the strategic AFP interchange data separately orderable licensed program that allows an stream, and IPDS is the strategic...

  • Page 591: C

    bootstrap. A sequence of instructions whose B execution causes additional instructions to be loaded and executed until the complete...

  • Page 592

    CCYY format. A 4-digit-year format that uses two environments. One of the three SAA architectural century digits (CC) to indicate...

  • Page 593: D

    CP command. In VM, a command by which a Data Language One (DL/I). 1. In IMS/VS, the data terminal user...

  • Page 594: E

    Device Support Facilities (DSF). An IBM-supplied directories. (2) An index that is used by a control system control program for...

  • Page 595: G

    features to permit a computing system to execute programs written for another system. F emulator. A combination of programming techniques...

  • Page 596: I

    GRS. global resource serialization. A component of IDCAMS. Utility program name for Access Method MVS/ESA SP used for sharing system...

  • Page 597: J

    purpose of modifying or extending the functions of the the host processor, as it is used by the channel IBM...

  • Page 598: L

    Job Entry Subsystem. An MVS subsystem that receives jobs into the system, converts them to K internal format, selects them...

  • Page 599: M

    link-edit. To create a loadable computer program by includes keeping a functional unit in a specified state means of a...

  • Page 600: P

    multivolume file. A file contained on more than one open. The function that connects a file to a program storage...

  • Page 601

    routines. They can run on different computers with problem determination. The process of determining little or no modification. the source...

  • Page 602: S

    by identifying and by verifying the users to the Q system, authorizing access to protected resources, logging the detected...

  • Page 603

    sequential data set. A data set whose records are SMS. Storage Management Subsystem. A organized on the basis of their...

  • Page 604

    Storage Management Subsystem (SMS). A system generation (SYSGEN). The process of component of MVS/DFP that is used to automate and...

  • Page 605: U

    TSO/E. time sharing option/extended. An option on T the operating system; for System/370, the option provides interactive time sharing...

  • Page 606: Y

    VSAM managed space. A user-defined space on disk V that is under the control of VSAM. verification test. A...

  • Page 607: List of Abbreviations

    List of Abbreviations ABEND ABnormal END BCS Basic Catalog Structure ACB Access Control Block BDAM Basic Direct Access Method ACF/NCP...

  • Page 608

    CGI Common Gateway Interface DBCS Double Byte Character Set CHKPT CHecKPoinT DBD Data Base Directory CI Control Interval DBRC Data...

  • Page 609

    DSCB Data Set Control Block FILESEC FILE SECurity DSECT Dummy Control SECTion FIPS Federal Information Processing Standard DSN Data Set...

  • Page 610

    HPR High Performance Routing IPDS Intelligent Printer Data Stream HSM Hierarchical Storage Manager IPF Interactive Productivity HTML HyperText Markup Language...

  • Page 611

    LPAR Logically PARtitioned mode OCO Object Code Only LRECL Logical RECord Length OE Order Entry LRU Least Recently Used, Line...

  • Page 612

    PPFA Page Printer Formatting Aid RPM Remote Print Manager PPT Processing Program Table RRDS Relative Record Data Set PR/SM Processor...

  • Page 613

    SPG Service Planning Guide TPF Transaction Processing Facility SPI System Programming Interface TRS Time Recording System SPIE Specify Program Interruption...

  • Page 614

    VTAM Virtual Telecommunications WTOR Write To Operator with Reply Access Method WWW World Wide Web VTOC Volume Table of Contents...

  • Page 615: A

    Index ACF/VTAM (continued) Special Characters resource definition and operation * $$ DATA 89 operation 190 * $$ LST 89 resource...

  • Page 616

    APSRMARK (MVS) 240 Assembler macros (continued) APTRMARK (VSE) 240 POST 285 APTZPARM macro 241 PRTOV 296 ASCII subsystem 188 PUT...

  • Page 617: B

    Assembler Products (continued) Assembler Products (continued) data management macros (continued) system interface & macros (continued) multiple search / feedback 325...

  • Page 618: C

    batch (continued) CBPDO 407 TCP/IP 195 CCB macro 327 unit testing 512 CCCA 522 BCP customization 415 CCCA positioning 523...

  • Page 619

    CICS (continued) COBOL (continued) MRO 136 from VS COBOL II 258 MVS management modules 142 general comments on COBOL for...

  • Page 620

    comparing (continued) conversion (continued) PSF commands 242 CA-Convertor 525 VSE & MVS JCL 86, 91 CICS Command Level Conversion Aid...

  • Page 621: D

    conversion phases (continued) courses (continued) unit testing (continued) locations 537 timing between on-line & batch testing 512 schedules 536 conversion...

  • Page 622

    data DB2 naming conventions 550 access 182 DB2 transparency feature 130 driven output segmentation 75 DBA 180 entry 76 DBD...

  • Page 623

    device (continued) DITTO (continued) control 448 function code synonyms 384 information 329 functions not recommended 383 migration 36 obsolete batch...

  • Page 624: E

    DOS/VS COBOL (continued) enforcing installation standards 410 REPORT WRITER statements 253 entering and manipulating data 159 reserved word considerations 263...

  • Page 625: H

    EXLST macro 291 functional reasons for migrating to OS/390 (continued) expanded JCL 76 connectivity 11 expiration date 548 staff availability...

  • Page 626: I

    HLL programming interfaces 242 implementing system security 410 host operations 452 implicit DEFINE 123 IMPRECISE 337 IMS/VS DB & DL/I...

  • Page 627: J

    introducing PSF/MVS (continued) JCL (continued) functional comparison (continued) parameter handling 75 PSF/MVS exclusives 235 partition dependent codes 81 migration effort...

  • Page 628

    JCL differences (VSE and MVS) (continued) JES2 (continued) VSE Job Control statements major JES2-POWER differences 207 ASSGN statement 83 NJE...

  • Page 629: L

    JES2/POWER functional comparison (continued) Language Environment (LE) (continued) output service (continued) conceptual differences between LE/VSE and OS/390 printers supported 216...

  • Page 630: M

    loading a DAM File (Fixed-Length Records without mass conversion - background, benefits & keys) 323 method 486 loading a DAM...

  • Page 631

    migrating from LE/VSE-conforming languages 353 migration (continued) C for VSE/ESA 353 project objectives 13 COBOL for VSE/ESA 354 reasons 3,...

  • Page 632: N

    MVS (continued) NJE (continued) device addresses 80 operator commands 233 DFP 21 PLINE mapping to JES2 LINE 227 DISPLAY command...

  • Page 633

    OPTI-AUDIT highlights 521 OS/390 (continued) OPTI-AUDIT product details 521 NCP 192 option setting recommendations 363 NJE connection 415 optional features...

  • Page 634: P

    OS/390 documentation resources parameter introduction references 39 handling 75 key documents & other references 40 mapping POWER - JES2 225...

  • Page 635

    PL/I (continued) plan components (continued) storage management 345 tasks 47 subprograms 331 team VSAM support 131 applications programmers 47 PL/I...

  • Page 636

    POWER/JES2 detailed comparisons (continued) PRINTLOG utility 393 POWER/JES2 command equivalences problem determination considerations 153 control commands 233 problem determination tools...

  • Page 637: R

    project (continued) REALAD macro 290 plan s u m m a r y 56 reasons for migrating 4, 10 planning...

  • Page 638: S

    resources (continued) run-time options & LE/VSE 1.1 361 operation 187 run-time options & LE/VSE 1.4 & later releases 362 remote-resident...

  • Page 639

    setting up AFP resources (continued) SNA Network Interconnection (SNI) 189 migrating print applications (continued) SNAP macro 279 OS/390 dynamic allocation...

  • Page 640

    stand-alone systems 421 submitting jobs for batch execution 162 standard applications 195 using command procedures 163 standard labels 78, 103...

  • Page 641: T

    systems management (continued) test (continued) s u m m a r y 472 techniques JES2 225 Systems Management Recording terminology...

  • Page 642: U V

    U V UCS naming conventions 218 variables 73 understanding device allocation 448 vendor applications 154 understanding operational differences 242 verifying...

  • Page 643

    VSAM (continued) VSAM differences (continued) managed SAM files 122 programming languages support (continued) managed space 15 COBOL for OS/390 &...

  • Page 644: Y

    VSE (continued) year2000 (continued) virtual storage macros 289 transition definition 582 VSAM backup/restore 387 your hardcopy library 412 VTAM 188...

  • Page 645: ITSO Redbook Evaluation

    ITSO Redbook Evaluation VSE to OS/390 Migration Workbook SG24-2043-00 Your feedback is very important to help us maintain the quality...

  • Page 646

    VSE to OS/390 Migration Workbook SG24-2043-00 Printed in the U.S.A. IBML SG24-2043-00

  • Page 647

    /XRL/1 Artwork Definitions id File Page References WOLOGO 2043SU i WOLOGOS 2043SU i TILOGO 2043SU i TILOGOS 2043SU i...

  • Page 648

    /XRL/2 R2 REDB$EVA 621 621 R1 REDB$EVA 621 621, 621 Figures id File Page References VAE 2043CH01 6 1...

  • Page 649

    /XRL/3 274 29 273 F1010 2043CH13 279 30 278 F1011 2043CH13 295 31 294 F1012 2043CH13 295 32 294...

  • Page 650

    /XRL/4 JMPP 2043CH32 493 58 493 Headings id File Page References REDBCOM REDB$COM xxii Comments Welcome PLNG 2043IMBD 1...

  • Page 651

    /XRL/5 69 Chapter 4, Job Control Language (JCL) Differences and Considerations 209, 375, 482 JCLFIL 2043CH04 69 4.1, The...

  • Page 652

    /XRL/6 169 Chapter 8, Databases 18, 18, 366 DLIUTIL 2043CH08 173 8.1.6, Utilities 176 TELECOM 2043CH09 185 Chapter 9,...

  • Page 653

    /XRL/7 AFPPSF 2043CH11 235 Chapter 11, Advanced Function Printing and Print Services Facility/MVS 17, 17, 215 PSFINCN 2043CH11 236...

  • Page 654

    /XRL/8 17, 17, 258, 259 CONDIF 2043CH17 352 17.1.2, Conceptual Differences between LE/VSE and OS/390 Language Environment 361 LVMC...

  • Page 655

    /XRL/9 407 25.4, Set Up Standards, Procedures, and Documentation 100, 481 PUTRSU 2043CH25 414 25.5.1.2, Applying Preventive Service 411...

  • Page 656

    /XRL/10 482, 482, 483 IMPF 2043CH32 515 32.6, Implementation Phases 482, 483 CNVSRVS 2043CH33 519 33.1, Conversion Services 519...

  • Page 657

    /XRL/11 i (1) CICS 133, 133, 134, 135, 135, 136, 136, 136, 137, 137, 138, 138, 140, 140, 142,...

  • Page 658

    /XRL/12 72, 73 C040004 2043VARS i (1) JECL 89, 89, 89, 90 C100003 2043VARS i (1) JES2/POWER functional comparison...

  • Page 659

    /XRL/13 235, 235, 236, 243, 243, 243, 244, 244 C110004 2043VARS i (1) PSF/MVS operational differences 242, 242 C110006...

  • Page 660

    /XRL/14 ECH0003 2043VARS i (1) Assembler 131, 173, 196, 241, 267, 267, 267, 269, 269, 359, 359, 359, 364,...

  • Page 661

    /XRL/15 3, 3, 4, 4, 10, 10, 13, 18, 27, 28, 29, 35, 35, 35, 36, 39, 42, 43,...

  • Page 662

    /XRL/16 GENIND 2043VARS i (1) general 135, 136, 311, 351 HIGHIND 2043VARS i (1) high level 72, 242, 364,...

  • Page 663

    /XRL/17 i (1) p r o g r a m 33, 171, 192, 257, 503, 517, 526 PSFIND 2043VARS...

  • Page 664

    /XRL/18 i (1) changes between VSE and OS/390 24, 24, 25, 25, 25, 25 C020005 2043VARS i (1) approaches...

  • Page 665

    /XRL/19 D040007 2043CH04 76 (1) JCL differences (VSE and MVS) (2) operator intervention 76, 76, 77, 77 D040008 2043CH04...

  • Page 666

    /XRL/20 D080011 2043CH08 181 (1) SQL/DS to DB2 (2) other comparison areas 181, 182, 182, 182, 182 D090001 2043CH09...

  • Page 667

    /XRL/21 D100016 2043CH10 230 (1) POWER/JES2 detailed comparisons (2) exit comparisons 231, 231 D100017 2043CH10 231 (1) POWER/JES2 detailed...

  • Page 668

    /XRL/22 D150009 2043CH15 336 (1) PL/I compiler options (2) options specific to MVS compiler 336, 336, 336, 336, 337,...

  • Page 669

    /XRL/23 452 (1) managing remote operations (2) JES2 RJE operations 452, 452, 453, 453, 453 D280018 2043CH28 453 (1)...

  • Page 670

    /XRL/24 529 (1) customer migration example (2) environment 529, 529, 530, 530 D340002 2043CH34 531 (1) customer migration example...

  • Page 671

    /XRL/25 86 7 OSJCL 2043CH04 88 8 POWJECL 2043CH04 89 9 J2JECL 2043CH04 90 10 89 JESIN 2043CH10 212...

  • Page 672

    /XRL/26 358 OPTRC1 2043CH17 363 42 363 OPTRC4 2043CH17 363 43 363 CICOPT 2043CH17 367 44 367 TABDLY 2043CH25...

  • Page 673

    /XRL/27 Print cross reference page numbers ....................................................... YES Process value ............................................................................................. (none) Punctuation move characters ................................................................... ., Read cross-reference...

downloadlike
ArtboardArtboardArtboard