IBM OS/390 manual

IBML VSE to OS/390 Migration Workbook Cliff Bays ** Dave Greenough ** John Hutchinson Da n 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[...]

[...]

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

Take Not e! Before using this information and the product it supports, be sure to read the general information in Appendix D, “Special Notices” on page 553. First Edition (October 1998) This edition applies to Version 2 Release 3 of IBM Virtual Storage Extended/Enterprise Systems Architecture (VSE/ESA), Program Number 5690-VSE, and to all subse[...]

Contents Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi The Team That Wrote This Redbook ......................[...]

2.7.5 Project Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 2.7.6 Automated Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 2 .8 Cost Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2 .9 OS/390 Documentation Resources ....................... 39 2.9.1 Introduction Refe[...]

4.3.13 Summary of MVS JCL Statements .................... 88 4. 4 JECL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 4.4.2 Comparison of POWER and JES2 JECL - A Summary ......... 89 4.4.3 Summary of JES2 JECL - A Table ..................... 90 4 . 5 VSE and MVS JCL Comparison Example .................... 91 4.[...]

6.1.11 CICS UPSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 6.1.12 Application Programming . . . . . . . . . . . . . . . . . . . . . . . . 150 6.1.13 CICS/VSE and TS Coexistence Considerations ............ 153 6.1.14 Testing and Problem Determination Considerations ......... 153 6.1.15 Vendor Applications . . . . . . . [...]

9.4.1 Network Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 9.4.2 TCP/IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 9.4.3 TCP/IP Related User Data ......................... 195 9.4.4 TCP/IP Batch Jobs ............................. 195 9.4.5 User Written TCP/IP Applications .................[...]

1 1 . 5 Other Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 11.5.1 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 11.5.2 Installation Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 11.5.3 Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[...]

Chapter 14 . R PG I I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 1 4 . 1 Migration from VSE to OS/390 ........................ 329 14.1.1 Device Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 14.1.2 Print Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 14.1.3 Tape[...]

15.11.1 Storage Management in DOS ..................... 345 15.11.2 Storage Management in MVS ..................... 345 15.12 PL/I and CICS ................................. 346 15.12.1 File Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 15.12.2 Statements not Supported ....................... 346 15.12.3 CALLing DUMP .[...]

1 8 . 5 Migration Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 18.5.1 REXX and SAA ............................... 372 18.6 REXX Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 Part 4. Converting VSE Utilities to OS/390 Utilities ....................... 373 Chapter 19 . SORT . . . . . .[...]

25.2.1 Processor Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 402 25.2.2 Devices Supported by OS/390 ...................... 402 25.2.3 DASD Requirements ............................ 402 25.2.4 Other Hardware Requirements ..................... 403 25.2.5 Inter-Systems Connectivity . . . . . . . . . . . . . . . . . . . . . . . . 404[...]

28.2.2 Managing Display Consoles ....................... 444 28.2.3 Extended MCS Consoles ......................... 445 28.2.4 Understanding Message Formats and Replies ............ 446 2 8 . 3 Controlling the OS/390 System ........................ 447 28.3.1 Starting the System ............................ 447 28.3.2 Displaying System Status .....[...]

30.7.2 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 30.7.3 Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 3 0 . 8 Asset Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 30.8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[...]

32.5.1 Program Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 32.5.2 J C L Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 32.5.3 Phase 4: Initial Trial Conversion .................... 505 32.5.4 Phase 5: OS/390 Regression Tests and Repeated Trial Conversions . . . . . . . . . . . . . . . . . . . . .[...]

C . 1 Data Set Naming Guidelines .......................... 543 C . 2 Components of a Data Set Name ....................... 544 C.2.1 High-Level Qualifier (HLQ) ........................ 544 C.2.2 Relative Importance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546 C.2.3 File Contents ................................. 546 C.2.4 User Name [...]

Figures 1 . V A E with Three Address Spaces . . . . . . . . . . . . . . . . . . . . . . . . 6 2 . VA E wi th Four Address Spaces . . . . . . . . . . . . . . . . . . . . . . . . . 7 3 . VSE/ESA Storage Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4 . OS/390 Storage Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [...]

4 6 . Loading a Sequential DAM File under VSE ................. 319 4 7. Loading a Sequential DAM File under MVS ................ 320 4 8. Loading a Random DAM File under MVS .................. 320 4 9 . Loading a DAM File of U. or V. Length Records under MVS ...... 321 5 0 . Processing a DAM file under VSE ...................... 324 5 1 . Loading [...]

Tables 1 . Comparison of V S E Functions & Components to OS/390 Replacements 1 6 2. W h o ′ s Normal Activities ar e Affected? . . . . . . . . . . . . . . . . . . . . 26 3 . Nine Month Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 4 . C N V Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . .[...]

xx VSE to OS/390 Migration Workbook[...]

Preface The purpose of this document is to provide information and guidance to personnel involved in a VSE to OS/390 operating system change; that is, a VSE to OS/390 migration. The primary focus is on VSE program and file conversions, and on operational differences between the two systems. Chapters on each of the source languages are included. DB/[...]

Authors and Significant Contributors Riaz Ahmad IBM, Gaithersburg Boris Barth IBM, Germany Bette Brody IBM, Gaithersburg Jerzy Buczak IBM, Cary Charlie Burger IBM, San Jose John Casey IBM, Dallas Walt Farrell IBM, Poughkeepsie Steve Gracin IBM, Endicott Judson Howard IBM, Los Angeles Stanley Jones IBM, Endicott Bill Keene IBM, Dallas Ulrich Kettner[...]

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

2 VSE to OS/390 Migration Workbook[...]

Chapter 1. Why Customers Migrate This chapter discusses the following topics: 1.2, Traditional Reasons for Migrating 1.3, Functional Reasons for Migrating to OS/390 1.1 A Synopsis of This Book What do I need to read? Executives: Read the following: • Part 1, “Planning the Migration - An Introduction” on page 1 • Part 8, “Migration Experie[...]

• Pa rt 4, Converting VSE Utilities to OS/390 Utilities Conversion of the VSE utilities to their equivalent OS/390 utilities is discussed in this part. • Part 5, Setting Up the Migration Environment No two Information Processing environments are alike. Hardware, software, scheduling, personnel needs will be different in all cases. This part dis[...]

1.2.2 Mergers/Acquisitions As with corporate consolidations, mergers and acquisitions present an equal number of challenges when having to incorporate the I/S organizations of the companies involved. A challenge that clearly presents itself is when the organizations involved run different host based operating systems (such as OS/390 and VSE/ESA). I[...]

┌─────────────────────────────┐ ───── ││  │ SVA - 2,304K │ │ ││ │ ├─────────────────────────────┤ │ │ F1 - VSE/POWER - 832K │ 8,832K Shared Address ├─────────────?[...]

┌───────────────────────────────────────┐ ───── ││  │ SVA - 2,304K │ │ ││ │ ├───────────────────────────────────────┤ 5,184 K │ F1 - VSE/POWER - 832K │ ?[...]

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

┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┐ 2GB │ │ │ │ │ │ │ │ │ │ │ J │ C │ D │ R │ T │ V │ U │ B │ B │ │ │ │ │ │ │ │ N │ │ │ │ E │ I │ F │ A │ S │ T │ [...]

manner. That is, not concurrent with OS/390 and/or VM/ESA. This has lead users to ponder whether VSE is a viable and strategic S/390 operating system. This lack of confidence has forced these users to look at OS/390 as a more stable and strategic operating system with a viable long term outlook. An outlook that often catches the eye of upper I/S ma[...]

OS/390 systems managed storage (DFSMS) provide enhanced system resource allocation and management. The Hierarchical Storage Manager (HSM), Removable Media Manager (RMM) and basic storage device allocation of OS/390 provide functions not inherent in the VSE environment. However, some of these functions are available from independent software vendor [...]

1.3.5 Staff Availability In recent years S/390 application and system programming resources have become increasingly more difficult to acquire. This is particularly true for the VSE user. As the current information systems curriculums focus on the more current technologies, the traditional VSE system programming, and to some degree OS/390, skills a[...]

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 Changes Between VSE and OS/390? 2.4, Who is Affected by This Migration? 2.5, Approaches to Migration 2.6, Educational Requirements 2.7, Scope of Work and Challenges 2.8, Cost Considerations 2.1 I[...]

2.1.2 Areas of VSE and OS/390 Differences In order to properly assess and size the magnitude of the migration project, it is first necessary to understand some of the basic differences between the two operating systems. Once these differences are understood a realistic or more reasonable project outlook can be determined. The purpose of this sectio[...]

document is organized by source language type and goes into great detail at that level and includes the I/O considerations. The conversion of the CICS applications consists of two steps. First, the VSE version of the CICS application subsystem is replaced with an OS/390 version. The two different versions of CICS contain the interfaces to the respe[...]

Sequential DASD files are compatible between VSE and OS/390. However, OS/390 does not support sequential (SAM) files located within VSAM managed space. These files will have to be reloaded to different DASD areas before OS/390 can process them. DL/I databases are compatible with IMS databases 1 if the ″ IMSCOMP ″ parameter was specified during [...]

Table 1 (Page 2 of 3). Comparison of VS E Functions & Components to OS/390 Replacements VSE OS/390 Comment and Reference Languages LE/VSE HLASM COBOL PL/I RPG II REXX FORTRAN C Languages LE/MVS * HLASM * COBOL PL/I RPG II REXX FORTRAN C/C++ * See Part 3 page 247 Chapter 1 7 page 351 Chapter 1 3 page 267 Chapter 1 2 page 249 Chapter 1 5 page 333[...]

Table 1 (Page 3 of 3). Comparison of VS E Functions & Components to OS/390 Replacements VSE OS/390 Comment and Reference ADSM/VSE ADSM/MVS DITTO/ESA for VSE DITTO/ESA for OS/390 See Chapter 20 page 381 DFSORT/VSE DFSORT * See Chapter 19 page 375 Data Base Management DL/I DB2 (SQL/DS) QMF Data Base Management IMS/DB DB2 QMF See Chapter 8 page 16[...]

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 , GC28-1725 is recommended for a better understanding of OS/390. This book describes the information associated with OS/390 including OS/390 books and books for participating elements. 2.2.1.1[...]

• Distributed Computing − UNIX Application Services (Shell, Utilities, and Debugger) − UNIX System Services (included in the BCP) • Distributed Computing Services − DCE Base Services (OSF DCE level 1.1) − DCE DFS (OSF DCE 1.2.1 level) − DFSMS/MVS Network File System • eNetwork Communications Server − VTAM (includes the AnyNet func[...]

• Systems Management Services − DFSMS/MVS features (DFSMSdss, DFSMSrmm, DFSMShsm) − HCM − RMF − SDSF • Application Enablement Services − DFSORT − GDDM-PGF − GDDM-REXX/MVS − IBM C/C++ Compiler (with debug tool) − IBM C/C++ Compiler (without debug tool) − IBM High Level Assembler Toolkit − Language Environment Data Decryptio[...]

• Data Facility Storage Management Subsystem Complementary functions of MVS/DFP and other individual products of the Data Facility family which, together with RACF, provide a system-managed, administrator-controlled storage environment. • Systems Resources Manager (SRM) A system function that determines which address spaces should be given acce[...]

• System Modification Program Extended (SMP/E) SMP/E controls software changes to modules and macros in the operating system, using a standard format and method that help ensure system integrity. SMP/E is required for installation and service functions. 2.2.1.3 Supporting Products A typical OS/390 operating system environment also includes severa[...]

in your environment. Each should be researched individually for installation applicability. 2.2.2 Subsystem Level Comparison/Affinity Various sections in this publication deal with the VSE and OS/390 subsystems and detail their similarities and differences. Specifically, these subsystems are: • DB2/VSE and DB2/MVS • DL/I and IMS/DB • CICS/VSE[...]

2.3.1.2 Automation VSE customers who use OCCF and/or ISV products to provide console automation functions will find enhanced function in the OS/390 environment. Because of the availability of functions such as DFSMSrmm and DFSMShsm consideration will have to be given to how to best implement these functions, starting with the development of storage[...]

2.4 Who is Affected by This Migration? 2.4.1 Job Roles and Normal Activities The following table which lists job roles and activities is intended to link specific activities to the appropriate job role. As such, it is also intended to act as an aid in determining the impact of the migration project on the various I/S functions. For example, assigni[...]

5. Security 6. Performance 7. Capacity Planning 8. Testing 9. Backup/Recovery 10. Disaster Planning 1 1 . Project Plan Development 2. 5 Approaches to Migration 2.5.1 Disclaimer For the purpose of providing a more effective guide the mass migration method was adopted as an approach or strategy in migrating. The reasons for the choice are numerous, b[...]

• OS/390 production is realized at an early time in the migration. When the first kernel is completed it is cut over to OS/390 production. This could be at a very early time in the migration thus providing early OS/390 feedback. However, this may not be the advantage it appears to be. Dual OS/390 and VSE production environments exist as VSE produ[...]

A conversion team is normally chosen that will be dedicated to the project until its end. Included with this team will be (perhaps) two application programmers. Naturally, the number varies with the size and complexity of the project. The team is responsible for converting all VSE applications. (As previously mentioned a program conversion aid is n[...]

• Staff availability Deciding to use in-house staff as part of the migration makes it difficult to perform regular job responsibilities while they are involved with the migration project. This is particularly true of applications staff as current application development and maintenance has to be put on hold. • Staff Skills When using in-house s[...]

• Mass conversion - (Cortex-MS) • Program inventory - (IBM OPTI-AUDIT) 2. 6 Educational Requirements 2.6.1 Introduction The educational requirements for the migration project will generally take the form of developing OS/390 skills; that is, JCL and conversion techniques. With the latter, strategies will have to be developed to convert things s[...]

2.7 Scope of Work and Challenges When converting VSE applications to OS/390 several tasks have to be performed. The following sections describe the most important work items involved and some of the challenges which can be encountered during the execution of these tasks: • Application inventory • Program conversion • JCL conversion • File m[...]

2.7.2 Program Conversion The conversion of VSE application code to OS/390 is often (but falsely) believed to be the center, most challenging, most labor consuming and most critical part of the conversion, but it is not. With few exceptions (see VSE positioning), it is a simple code modification which does not change program logic, and can nearly al[...]

JCL: it is hidden inside the code (main or sub-program) associated with the step. Some of the file attributes coded in the VSE JCL are superseded by the disk or tape manager: the proper file attributes must be retrieved in the tape or disk manager ′ s catalog or in the VTOC listings. In short, it is not possible to understand the flowchart of the[...]

flows. For example: You can have hundreds of files with the same name, for example ″ WORK1 ″. WORK1 can exist in different jobs. Most of the time the WORK1 files will be different from and unrelated to each other. You can however have JobA use a file named WORK1 and JobB running at the same time and also using a file called WORK1. JobA WORK1 ge[...]

The main challenge is the identification and classification of files for the migration. All files that will be used as input to a job after the switchover to OS/390 operations must be migrated. Files recreated by the first OS/390 production cycles do not need to be migrated, and are better off not being migrated (at least temporary files, cataloged[...]

2.7.5 Project Management As with application inventory or JCL conversion, the management of a VSE to OS/390 conversion project is nearly always underestimated. The VSE to OS/390 conversion is one of the rare projects that require a coordinated effort from each of the three data processing departments: applications, technical support and operations.[...]

procedures. Most will simply try to reproduce with the new OS/390 product what they were doing in VSE with or without assistance of a product. The challenge is to: • Understand how OS/390 works, • Understand how the OS/390 job scheduler or report manager is best used, • Define specific local implementation rules and guidelines (standards), an[...]

The purpose here is not to predict or estimate project costs but to identify major cost elements and any relevant financial resource considerations. • Cost/Benefit Requirements  Reasonable and predictable timeframe  Reduced internal staff participation focused on learning OS/390  No delay/postponement of development and maintenance  C[...]

2.9.2 Key Documents and Other References • OS/390 V2R5 Planning and Installation , SK2T-2484 • CBIPO (System Pak) Custom Built Offerings Planning • CICS Up and Running • DB2 Release Guide 2.9.3 W eb URL http://WWW.S390.IBM.COM/OS390/ 40 VSE to OS/390 Migration Workbook[...]

Chapter 3. Developing the Plan This chapter discusses the following topics: 3.1, Overview 3.2, Plan Components 3.3, Progressive versus Mass Conversion 3.4, Plan Examples 3. 1 Overview 3.1.1 References These materials provide sources of supplemental information for this chapter. • MVS Migration System - Planning Guide , SB11-8077 describes the pla[...]

3.1.2.2 Take Advantage Of Conversion Tools and Automation Executing a migration with a mass conversion tool and automated processes can reduce both the time and people required to migrate from VSE to OS/390. Where it is not a large task to convert three programs and two strings of JCL, it is a large and difficult task to increase the scope by one t[...]

SISRO and is no longer available, but deserves mentioning. The product documentation is helpful in that it provides a very good project plan and description of the mass migration approach. When sold through SISRO, this tool is know as CORTEX-Migration System (CORTEX-MS) and currently is available. Although there have been many changes to the MVS an[...]

The hired conversion specialists can be deployed for converting the in-house developed applications, and leading the overall migration effort, including: • Following the migration methodology and the project plan • Identifying and addressing the conversion requirements • Converting the VSE applications to OS/390 • Design and delivery of a s[...]

3. 2 Plan Components 3.2.1 A ppro ach For the purposes of providing more specific guidance for conversion projects, an approach to the migration had to be determined. This is also true for the migration effort itself, an approach must be adopted. In these discussions, we will describe the environment associated with using the Mass Conversion method[...]

If a mass migration/conversion tool is used someone will need to become familiar with the product and the mass migration method. The team members should consult the product documentation related to their responsibilities and run the sample conversion. The functions and responsibilities of each member of the team depend to some extent on local condi[...]

3.2.2.3 Applications Programmers The applications programmers help the project manager to develop migrations procedures. They also test converted applications. They should be thoroughly familiar with critical applications (both online and batch) and understand both VSE and OS/390. Their tasks and responsibilities include: • Helping to design the [...]

7 Training personnel to work with the OS/390 system. 8 Planning and installing the OS/390 system products. 9 Developing standards for application conversion that reflect such things as naming conventions to be used in the new OS/390 system environment. 10 Collecting all VSE source materials and presenting same to the conversion process. 11 Translat[...]

3.2.5 Education OS/390, and to some degree migration/conversion skills are crucial factors to the success of the migration project. Identification of skill requirements and how these requirements will be satisfied is the main objective of the education plan. Listed are the key elements to effective education planning: • Identify personnel (who) ?[...]

3.3.2 Historical Perspective The progressive conversion approach was the only solution available until the early 80s. More recently modern VSE operations have substantially grown in size, complexity and integration, making it more difficult to implement a progressive conversion. It is also because the mass conversion approach, which was in a pionee[...]

separate operating systems, or the division of tape files and tape volumes between two tape managers running on two separate operating systems. 3.3.7 Standardized Conversion Deliverables and Automation A significant objective for today ′ s VSE or OS/390 mainframe installation is the standardization of their application components (JCL streams, ap[...]

automated conversion defects. The switchover of an entire VSE production to OS/390 over a weekend cannot be improvised: it requires perfect precision and planning by experienced conversion specialists. The complexity of powerful mass conversion tools makes it difficult to staff with internal non-conversion-expert staff exclusively, because of the l[...]

• Program clauses that restrict device independence are eliminated; that is, I/O assignment clauses removed from programs, placed in JCL. • Program console interactions (for example, COBOL DISPLAY/ACCEPTs) are removed from being executed at program runtime; rather this input is requested at job setup time via job preparation panels and prompts.[...]

3.4.1 Project Schedule 3.4.1.1 Estimated Project Schedule The following is an estimated schedule for Project 2 - VSE to MVS conversion. The project may begin upon completion of the Inventory Determination task of Project 1, estimated to be on or about June 1, 1996, and will last approximately nine (9) months with a switchover to MVS after approxima[...]

3.4.1.3 Estimated Schedule for ABC Responsibilities The following is an estimated schedule for the ABC responsibilities. The actual schedule will be determined at project start. Table 5. ABC Responsibilities Month Number Month Initial 123 456789 J J A S O N D J F 01 - Manage ABC Conversion Responsibilities ** ** ** ** ** ** ** ** ** 02 - Participat[...]

3.4.2 Project Plan Example The actual schedule will be determined at Project 2 start, based on the completion of the Project 1 Inventory Determination completion date, the expected switchover date, and any potential conflicts with ABC ′ s processing. 3.4.2.1 Project Plan - Summary Task Name ID Projected Actual Start End Start End Preparation Phas[...]

1998 Jan ↓ Fe b M a r Ap r Ma y Jun Jul Aug S ep Oct Preparation Phases Application Inventory Specifications Customization Conversion Phases Trial Conversion Onlne Testing Batch Testing Production Testing Implementation Phase Actual Conversion & Switch Initial MVS Operations ♦ Migration Completion ID 01 02 03 04 05 06 07 08 09 10 11 12 Task[...]

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 02 Application Inventory 01/09/98 08/24/98 03 Initial & Inventory Supplies 01/09/98 03/10/98 04 0 % Missing 03/10/98 03/10/98 05 General Inventory Supply Every 3 Weeks 03/10/98 08/24/98 06 Less than 2% Missing 02/01/98 02/01/98[...]

ID Task Name Projected Actual Start End Start End 38 Perform Online Application Tests 06/07/98 08/16/98 39 Perform Online Network & Stress Tests 08/16/98 08/30/98 40 Refine & Repeat Online Application Conversion 04/26/98 08/23/98 41 Batch Application Conversion 01/09/98 05/10/98 42 Install Conversion Tools 01/09/98 01/16/98 43 Install Conve[...]

ID Task Name Projected Actual Start End Start End 72 Batch Application Tests Can Start 06/07/98 06/07/98 73 Perform Critical Application Batch Tests 06/07/98 08/16/98 74 Non-critical Application Batch Tests 08/16/98 09/21/98 75 Refine New OS/390/DFSMS Standards 05/10/98 08/16/98 76 Identify Application Interfaces 06/14/98 08/02/98 77 Refine & R[...]

1998 Jan ↓ Feb M a r Apr M ay Jun Jul Aug Sep Oct ♦ Project Approval Application Inventory Application Inventory ♦ 0 % Missing General Inventory Supply Every 3 Weeks ♦ Less than 2% Missing Project Planning Project Plan Develop Project Plan ♦ Present Project Plan Review & Complete Project Plan Online Test Plan & Scripts ♦ Online [...]

1998 Jan ↓ Feb M a r Apr M ay Jun Jul Aug Sep Oct ♦ Switchover Test Orientation Refine Switchover Plan Online Application Conversion COBOL Program Conversion COBOL Online Conversion Specifications Automated COBOL Online Conversion Manual COBOL Online Conversion Map, Table, Data Conversion CICS Map Conversion Setup CICS Tables Migrate CICS Files[...]

1998 Jan ↓ Feb M a r Apr M ay Jun Jul Aug Sep Oct Install Conversion Software Batch Program Conversion COBOL Batch Conversion Specifications Automated COBOL Batch Conversion Manual COBOL Batch Conversion VSE JCL Conversion JCL Pilot Conversion VSE JCL Conversion Specifications VSE JCL Automated Conversion Manual PCL and JCL Conversion First Mass [...]

1998 Jan ↓ Feb M a r Apr M ay Jun Jul Aug Sep Oct Batch File Migration Procedures Migrate Batch Test Files COBOL VSE Positioning Identify COBOL VSE Positioning Perform & Implement COBOL VSE Positioning ♦ Batch Test Can Start Batch Application Tests & Corrections Sample Batch Tests ♦ Batch Application Tests Can Start Critical Applicati[...]

1998 Jan ↓ Feb M a r Apr M ay Jun Jul Aug Sep Oct Perform Production Tests Actua l Conversion Convert Development Code Mass Conversion JCL Supply JCL Mass Conversion ″ Fix & Freeze ″ JCL Last Program Supply Last Mass Program Conversion ″ Freeze & Fix ″ Programs ♦ Switchover Can Start OS/390 Switchover Final Switchover Preparatio[...]

66 VSE to OS/390 Migration Workbook[...]

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

68 VSE to OS/390 Migration Workbook[...]

Chapter 4. Job Control Language (JCL) Differences and Considerations The following sections describe the major tasks and considerations involved in converting VSE JCL to MVS JCL and the differences between them. These sections are divided into the following categories: • 4.1, The Philosophy of JCL in System/390 • 4.2, High Level Similarities ?[...]

OS/360 (PCP, MFT, MVT), the predecessors to MVS, and OS/390, specified Job Control Language but when JCL was needed for BOS and TOS, a much smaller implementation was required. Different JCL philosophies developed from this background. 4.1.1 VSE/ESA ′ s Job Control Language Philosophy Within the VSE/ESA philosophy for Job Control Language, severa[...]

Because there is no concept of permanent ASSGN or specification of standard label facilities, all resource requirements for each job step must be included explicitly in each job step. In OS/390, these definitions can be included as procedures which can reduce the repetitive coding of JCL statements (specifically DD statements). To understand the st[...]

Unlike VSE, the operator does not manipulate elements within a job stream, nor is he given the opportunity to correct JCL errors. The processes are much more automated in OS/390 under the theory that the system will be better utilized and jobs run more efficiently without operator intervention. 4. 2 High Level Similarities A high level comparison o[...]

4.2.1.7 Instream Data Both operating systems allow Instream Data in the middle of the JCL. This is data that will be processed by the executing program. 4.2.1.8 Variables The JCL in both operating systems will accept variables. These variables are set with the // SET statement in MVS, or SETPARM in VSE. 4.2.1.9 Conditional JCL Conditional JCL exist[...]

Instream data will always follow an EXEC statement, and it is the responsibility of the executing program which is reading the instream data to recognize the end of that data. By default, the instream data delimiter is the ″/ * ″ statement, although an application program can choose its own delimiter. This allows programs other than JCL to read[...]

4.3.1.2 Data Driven Segmentation of Output An artifact of this sequential processing in VSE is that the spooling system extracts its control statements (JECL) from the input as it is being spooled. When the input processing crosses the input stream position where the JECL statement was located, the spooling system will take the action specified by [...]

expansion for subsequent steps. In general, this is not possible in MVS JCL in the OS/390 environment. 4.3.2 JCL Expansion In VSE, JCL is expanded at execution time. The most current changes, even those changed two seconds before the job begins execution are included. The first step could change a procedure that is used by the third step. In OS/390[...]

// PAUSE mount tape 123456 on an available drive. // ASSGN SYS005,CUU - or - // ASSGN SYS005,Drive The operator gets an error message and enters the correct tape assignment, such as: // ASSGN SYS005,481 Another example is TLBL without VOLSER or a known invalid VOLSER. // TLBL 999999 Forcing error conditions in VSE JCL that require operator interven[...]

There is no equivalent function in OS/390. Many users write their own routine to replace the PAUSE function, if needed, or use the existing automation functions of OS/390. 4.3.4 Allocation of Resources The allocation of resources in OS/390 occurs at step initialization time. This is a big difference from VSE where allocation of resources occurs at [...]

the conversion of the JCL which may have to be converted differently, depending on in which partition the job normally runs. There is no equivalent to standard labels in OS/390. Labels must be spelled out in each step. One way to keep a common set of labels in OS/390 is to use the JCL INCLUDE statement. In rare cases another possibility is to use d[...]

Understanding tool provides a graphical analysis of your VSE/ESA JCL job stream. You can find further details at the following World Wide Web sites: http://www.software.ibm.com/ad/va2000 http://www.software.ibm.com/ad/cobol The JCL Analyzer is shipped as part of VSE Central Functions in VSE/ICCF library 59. It consists of a number of members, inclu[...]

• For unlabeled tapes - the DEVADDR is the only link between the program and the JCL (there is no TLBL). Either the DEVADDR or the DTFname can be used as DDNAME. • For card devices - the DEVADDR links the DTF to a card reader or puncher; Either the DEVADDR or the DTFname can be used as DDNAME. • For print devices - the DEVADDR is the only lin[...]

In OS/390 the DATE function can be replaced by a control card, a parameter on the EXEC statement, or a date simulation tool. 4.3.9.2 UPSI The UPSI switches that were on the 1401s got a second life in DOS with the System/360. UPSI can be tested in RPG, Assembler and in COBOL. For more information on the manipulation of UPSI with Assembler see Chapte[...]

The VSE file-id (the label), which can be up to 17 characters long, is equivalent to the MVS DSname, which can be up to 44 characters long. 4.3.10.4 M TC Statement Magnetic Tape Control statements provide control over tape processing including writing tape marks and unloading tapes. MTC has no direct equivalent in MVS: OPEN automatically positions [...]

location for these. In OS/390 these duplicate names need to be resolved somehow. Refer to Chapter 5, “Disk and Tape Storage Considerations” on page 9 7 . 4.3.10.9 Conditional JCL VSE/ESA added conditional JCL processing in the early 1980s, with VSE/SP Version 2. This conditional JCL is characterized by several new JCL statements, including // I[...]

COND Parameter on the EXEC Statement To indicate the results of its execution, a program can issue a return code. Using a COND parameter, you can test the return code and, based on the test, either bypass or execute a step. The COND parameter can be specified on either a JOB or EXEC statement. See the JCL User ′ s Guide for explanation and exampl[...]

4.3.12 Comparison of VSE and MVS JCL - A Summary Below is a summary of VSE JCL statements and possible equivalents in MVS. Table 7 (Page 1 of 2). VSE J ob Control Statements Summary VSE Statement Function M V S Equivalent ASSGN Used at execution time to assign a specific device address to the symbolic unit name used. // DD UNIT= CLOSE Closes either[...]

Table 7 (Page 2 of 2). VSE J ob Control Statements Summary VSE Statement Function M V S Equivalent ON Causes specified action to be done if the specified condition is true after any step in the following job stream. // EXEC COND= or //IF/ENDIF OPTION Sets one or more of the job control options. // EXEC PARM= PAUSE Causes a pause immediately after p[...]

4.3.13 Summary of MVS JCL Statements Table 8. MVS Jo b Control Statements JCL Statement Purpose // command Enters an MVS system operator command through the input stream. The command statement is used primarily by the operator. Use the COMMAND statement instead of the JCL command statement. // COMMAND Specifies an MVS or JES command that the system[...]

4.4 JECL JECL is very important in VSE and is commonly used. The difficulty from a conversion standpoint is to determine where the job is due to having two different job cards in JCL. The JECL statement is a POWER job, the DOS Job or VSE Job is the // JOB. The POWER job is like the MVS JOB. This is where the class and priority information is specif[...]

Table 9 (Page 2 of 2). Overview of POWER JECL Statements POWER Statement Function JES2 or MVS Equivalent * $$ FLS Indicates that a VSE/POWER job should be terminated by internal flushing. /*PURGE if INTRDR * $$ JOB Indicates the beginning of a VSE/POWER job and specifies the routing of jobs, output, and notify messages. / / JOB * $$ LST Provides ha[...]

Table 10 (Page 2 of 2). JES2 Control Statements Statement Purpose Comments /*ROUTE P RT or /*ROUTE PU N Specifies the default print or punch destination for the job. Use the // OUTPUT DEFAULT=YES instead. /*SETUP Requests mounting of volumes needed for the job. Seldom used. (Similar to VSE PAUSE statement) /*SIGNOFF Ends a remote job stream process[...]

job (all definitions available to all steps). OS/390 operation does not perform this ″ carry-over ″ ( unique to VSE). 4.5.1 Sample VSE JCL This example shows one POWER job containing three VSE jobs. * $$ JOB JNM=MYJOB,CLASS=F,USER= ′ ITSO SAMPLE ′ * $$ LST LST=SYSLST,JSEP=0,CLASS=W,COPIES=3 // JOB JOB1 extract records from tape // ASSGN SYS[...]

4.5.2 S am ple MVS JCL The task surrounding the conversion of JCL is more than mapping between VSE JCL using this syntax and MVS JCL using that syntax. At the base of these two JCLs are different philosophies. A parameter by parameter comparison is insufficient. Comparing the VSE DLBL/EXTENT to a DD Statement is only part of the story. These exampl[...]

A method that used two SYSOUT devices and output two DCBs in the program could also work. 3. PROGRAM2 Changes PROGRAM2 has to change for OS/390 to simulate the imbedded LST cards in the VSE job (for DEST=KCJONES and DEST=HERBERT). PROGRAM1 was OK as far as file assignments. 4.5.3 Sample VSE plus Carry-Over In this example the job cards for JOB2 and[...]

** JOB JOB3 PRINT REPORT // EXEC PROGRAM2,SIZE=300K * $$ LST LST=SYS010,DEST=KCJONES 01 ENDICOTT * $$ LST LST=SYS010,DEST=HERBERT 02 BOEBLINGEN /* /& * $$ EOJ Chapter 4. Job Control Language (JCL) Differences and Considerations 95[...]

96 VSE to OS/390 Migration Workbook[...]

Chapter 5. Disk and Tape Storage Considerations The VSE/SP and VSE/ESA systems and MVS and OS/390 systems have some conceptual similarities and data compatibilities for disk and tape files. This chapter will discuss the similarities and differences between the VSE and OS/390 environments in the following areas: • 5.1, Access Method Similarities a[...]

DAM (or BDAM) Direct Access Method (or Basic Direct Access Method) -- used for disk devices. Still in some use, but often replaced by VSAM functions in many VSE shops. Generally requires complex application handling for processing, and may be dependent upon physical device characteristics. Not supported on Fixed-Block Architecture disks. In OS/390,[...]

In OS/390, the application program linkage is handled through the SVC interfaces of the operating system. In either case, the application program functional request (GET, PUT, and so on) will cause the next logical record to be retrieved from a buffer or from external media. Channel programs are created, and the operating system will cause the chan[...]

As it is desirable from both performance and integrity perspectives to separate user data sets into several user catalogs, it is critical that data set names be defined with the above information in mind. If, for example, all data set names begin with CUSTOMER as the first node, then all the data sets will be defined in only one user catalog. If th[...]

functional components as well as RACF and DFSORT. For details, see section 1.3 in the DFSMS/MVS General Information , GC26-4900. • DFSMSdfp is an OS/390 base element and functional component of DFSMS/MVS. It provides the storage, program, data, and device management functions of MVS. DFSMSdfp provides the foundation for distributed data access, u[...]

For more information on the benefits of system-managed storage, refer to the following publications: DFSMS/MVS General Information , GC26-4900 Implementing System-Managed Storage , SC26-3123 DFSMS/MVS Planning for Installation , SC26-4919 RACF General Information , GC23-3723 Getting Started with DFSORT , SC26-4109 5.3.4 Implementing DFSMS Implement[...]

DFSMS FIT is documented in the following IBM International Technical Support Organization publications (Redbooks): Get DFSMS FIT: Fast Implementation Techniques , SG24-2568 DFSMS FIT: Fast Implementation Techniques Process Guide , SG24-4478 DFSMS FIT: Fast Implementation Techniques Installation Examples , SG24-2569 In conjunction with DFSMS FIT, yo[...]

Note: UHL and UTL processing are user standard labels. Under VSE, standard label write processing when FILABL=STD is specified in the DTF includes: ┌──────┬──────┬─────┬────────────────┬─────┬──────┬─────┐ │ VOL1 │ HDR1 │ TM │ D[...]

• block length • record length • tape recording technique (seven-track only) • tape density • record format to the OS/390 system. This information was coded in VSE programs. However, it is strongly recommended that this data be removed from VSE programs as they are being converted to OS/390 versions. Place the above data in the DCB subpar[...]

statement. If a tapemark might precede the first data set and you specify the LABEL subparameter LTM, OS/390 tests for and bypasses a leading tapemark, if present. If a tapemark precedes the first data set and you do not specify LTM in the LABEL parameter field, you must add one to the data set sequence number. If a multivolume data set has a leadi[...]

A. VSE: With Tapemark Before Data Records ┌─────┬───────────────────┬─────┬─────┐ │ TM │ Data Records 1-n │ TM │ TM │ └─────┴───────────────────┴─────┴─────┘ B. VSE: Without Tapemark B[...]

5. 5 DASD Similarities and Differences 5.5.1 Volume Interchangeability DASD file label conventions, requirements, and handling techniques differ between VSE and OS/390 systems. However, OS/390 should be able to read and process DASD volumes that have been created on a VSE system. Similarly, VSE systems should be able to read volumes created by OS/3[...]

maintaining the accuracy of the Format-5 DSCB. The Format-5 DSCB , sometimes called the ″ free space DSCB ″, is used only by OS/390 . OS/390 keeps track of unallocated space on a volume by creating one or more Format-5 DSCBs; that is, each Format-5 contains up to 26 extents of free space information. VSE, although it doesn ′ t keep track of f[...]

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 VSAM and other OS/390 access methods are provided by the OS/390 Data Facility Product (DFP). The term ICF refers to the Integrated Catalog Facility. The term AMS refers to Access Method Services and/or the prog[...]

• OS CVOL catalogs - these are a carry-over from the past (pre-OS/390) and are non-VSAM in structure. It has also been announced that OS CVOL catalogs will not be supported after December 31st 1999. For these reasons, they should not be implemented in your OS/390 system. 5.6.2.1 Integrated Catalog Facility (ICF) The architecture of an ICF catalog[...]

If access to a disk volume is lost, DFSMShsm can be used to perform a full-volume restore with update. You specify ICF catalog format by including the ICFCATALOG keyword in the AMS DEFINE MASTERCATALOG or DEFINE USERCATALOG command. ICFCATALOG is the default when defining a catalog in OS/390. VSAM data sets cataloged in ICF catalogs have the UNIQUE[...]

Item G023729 Last updated....: 10/13/1997 Abstract........: WSC FLASH 9741 VSAM CATALOG AND CVOL SUPPORT ENDS IN YR2000 Access to an MVS or OS/390 non-ICF VSAM catalog or CVOL will not be possible after 1999. The following text was taken from the DFSMS/MVS 1.4 availability announcement made on June 6, 1997 (297-192): ″ NOTE: On October 31, 1995, [...]

When the system date is on or after 1/1/2000, the following reason code will be issued: ″34 - Explanation: An attempt was made to open a VSAM catalog for use as a catalog. The request was denied. Programmer Response: VSAM catalogs may not be used beginning Jan 1, 2000. ″ Please note that CVOL support will also be removed effective 1/1/2000 but [...]

IPL unit_address LOADPARM where LOADPARM bytes contain: bytes 1--4 5--6 7 8 ┌──────────────┬────────────┬─────────────┬─────────────┐ │ IODF DASD │ LOADxx │PROMPT FEAT. │ ALT NUCx │ └─────────────?[...]

The data set names of the user catalogs are contained in the OS/390 master catalog. Information necessary to locate the user catalogs is also defined in the master catalog. The high-level-qualifiers of data sets that are to be cataloged in each user catalog are also identified in the OS/390 master catalog. OS/390 data set names are divided into qua[...]

Do not use JOBCAT or STEPCAT statements in OS/390 In predecessors of today ′ s OS/390 systems, it was not uncommon to use JCL DD statements specifying user catalogs to be used for a job or a step (JOBCAT or STEPCAT). This procedure was obsoleted with the advent of the Integrated Catalog Facility and its ALIAS mechanism, and it should not be used.[...]

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 catalogs from the OS/390 system. Under no circumstances should you attempt to share VSAM catalogs or data sets between OS/390 and VSE/VSAM concurrently. There is no system data integrity provided for concurrent access shar[...]

5.6.4.3 Moving a VSAM Catalog to a Different DASD Type VSE/VSAM provided no facility for moving a catalog to a different device type or volume serial number. OS/390 VSAM provides this facility for ICF catalogs via the AMS REPRO and EXPORT/IMPORT commands. Using the REPRO function, you may specify the old catalog as the input and the new catalog as [...]

• VSE/VSAM-managed SAM files − Default models − NOALLOCATION data sets − Implicit JCL DEFINE • Reusable data sets • Partition independent file names • VSE/VSAM BACKUP/RESTORE and VSE FASTCOPY • IKQVDU - volume cleanup • IKQVCHK - catalog check • Space classes • VSAM SHAREOPTIONS (SHR(4) and SHR(4 4) differences) 5.6.5.2 FB A D[...]

maintain the ″ VSAM Ownership Bit ″ in the VTOC, and the list of volumes owned by the catalog. Under VSE, multiple VSAM catalogs can own space on the same DASD volume, as long as only one recoverable catalog owns space on that volume. This support has been provided by adding a VSE unique ″ bit map ″ in the VSAM catalog, identifying the spac[...]

VSE/ESA Version 2.2 included new VSAM support for compression of VSAM data sets. The implementations of the two VSAM systems are not compatible, due to the differences between VSAM catalogs used by VSE, and ICF catalogs used by OS/390. COMPRESSED data sets defined in VSE will have to be unloaded from VSE and reloaded in OS/390. REPRO or EXPORT/IMPO[...]

VSE SAM/VSAM data sets may also be converted to VSAM ESDS data sets. However, this is not recommended as it requires changes to the programs. Default Models Both VSE and OS/390 VSAM support the MODEL parameter of the DEFINE command. This allows the attributes of an existing file to be used during the define of a new file. VSE/VSAM also supports thr[...]

• acts as an ACB without RESET (add new records to existing file) • DISP=OLD overrides IDCAMS REPRO with REUSE To rewrite a reusable data set - / / DLBL .....,VSAM,DISP=NEW • acts as an ACB with RESET (delete old records, add new records) • DISP=NEW overrides IDCAMS REPRO with NOREUSE Partition Independent File Names VSE/VSAM partition inde[...]

in the VTOC. This equivalent function is performed in OS/390 VSAM by the AMS command ALTER REMOVEVOLUMES. The volume cleanup function of ″ ALTER REMOVEVOLUMES ″ should only be used when the catalog is not accessible or totally unavailable. This command may also be used to remove candidate volumes as in VSE/VSAM. IKQVCHK - Catalog Check This VSE[...]

5.6.6.1 Cross-Region Sharing - Single CPU Environment Whenever a VSAM data set (ACB) is opened by more than one control block structure concurrently, data integrity must be considered. OS/390 VSAM offers two levels of protection and/or sharing within a single CPU. 1 . O S/ 3 9 0 will prevent concurrent update/update or update/read access to a VSAM [...]

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 lock the record, CI, or CA as appropriate to protect the file and user data from corruption by possible concurrent update activity. SHR(4) data sets can have inserts or updates which may cause CI and CA splits, and secondary allocation[...]

5.6.6.2 Single Region Data Set Sharing Single ACB Open - Multiple String Processing Full write integrity is provided within a single region provided the user uses a single ACB to process the data set. In high level languages an ACB equates to: 1. a SELECT statement in COBOL 2 . a file DECLARE i n PL/I 3. an ″ F ″ statement in RP G I I If multip[...]

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 any operating system to access the same DASD volume concurrently. This includes multiple OS/390 guests running under VM or PR/SM. You must not attempt to update via DASD sharing between VSE and OS/390 systems . The methods of[...]

• Planning for Installation • DFSMSdfp Storage Administration Reference • Using Data Sets SHAREOPTIONS (X 4) Cross-system SHR(x 4) provides the same limited protection across systems as cross-region SHR(4). Extensions of the data set ′ s high-used RBA are prohibited. To provide complete integrity protection it is the user ′ s responsibili[...]

This provides cross address space sharing as well as journaling and recovery for the batch applications. It also allows existing files to be accessed with new application tools such as QMF without having to rewrite existing applications. 5.6.7 Programming Languages and VSAM Support For additional information on program languages and VSAM considerat[...]

perform a DFSORT COPY function to copy the temporary data set back into the original SORTIN VSAM data set. 2. Sorting multiple VSAM data sets in the same step. VSE SORTs allow multiple inputs through multiple SORTIN(n) DLBL or TLBL statements. DFSORT allows only one input to sort, the SORTIN DD statement. Through OS/390 JCL, multiple sequential dat[...]

Chapter 6 . CICS 6.1 Introduction This section is directed to individuals with a working knowledge of both CICS for VSE/ESA and CICS Transaction Server. Without this knowledge, a reader may find this section less fulfilling. Also, you should understand that the scope of this section is to provide general migration tasks and considerations, and shou[...]

• Enhanced interface to the World Wide Web (WWW) adds support for 3270-based transactions. • The CICS Gateway for Java has been ported for execution on OS/390 as an OpenEdition (R) application with CICS TS as the CICS server in a two-tier configuration. • REXX for CICS (Development and Runtime) added as two new elements of CICS TS. • Suppor[...]

Please contact your local IBM Representative for more information on how to access IBM manuals via the INTERNET. Another useful INTERNET location ′ http://www.hursley.ibm.com/cics ′, is the CICS home page. The CICS Internet Home page provides a service/support segment that allows easy access to a wide range of material that complements the CICS[...]

application programs may be placed above the 16 megabyte line if they are written in VS COBOL II, PL/I, C++ or HLASM. If you have a need to combine systems or you are adding new CICS applications that could introduce additional virtual storage constraints, you should consider the use of CICS Multiple Region Operation (MRO). In addition to providing[...]

to SYSLST, access to CICS system control blocks. You should consider what impact each of the removed service or support will have on your migration. Macro-level programs You need to convert macro-level programs to command level. Please account for and anticipate the additional CPU requirements for the converted programs. BTAM devices and controller[...]

Access to CICS system control blocks CICS management modules are provided as pregenerated systems for MVS. All the functional areas in CICS are provided completely in object-code only form (OCO), without licensed source materials. Thus, you can not modify the CICS source as in your present releases. Hence, if your present system includes source mod[...]

┌────────────┐ ┌───────────────────┐ ┌───────────────────┐ │ ├────┤ Parameter manager │ │ Application ├────┤ │ │ domain (PA) │ │ domain (AP) │ │ │ └──────────────?[...]

CICS data table services RDO for VSAM files and LSR pools Some EXEC CICS system programming functions Autoinstall terminal model manager Partner resource manager SAA Communications and Resource Recovery Some of the file control functions Recovery manager connectors interfaces. Domains never communicate directly with each other. Calls between domain[...]

Also, you should remove the parameters such as REUSE, RSL, and DEVICE from the DCT specification; these parameter are obsolete. Note: CICS TS provides a facility that allows an extrapartition data set to be used to submit jobs to MVS. FCT Remove the CSD entry from FCT (it is now in the SIT), plus all VSAM entries (VSAM resource entries are autoinst[...]

TCT review the entire table, particularly for BTAM changes. Add CONSLID=console designation for MVS Multiple Console Support (MCS). You must remove any spool parameter associated with CICS/VSE Report Controller Feature (RCF). SIT review all the entries since there are VSE and MVS only parameters. Plus, there are new and different suffixes for the p[...]

JCT The CICS log manager does not support journal data sets, making the journal control table obsolete. The CICS system log and journals are mapped to MVS system logger log streams (or, for some journals, SMF data sets) by means of JOURNALMODEL resource definitions. JSTATUS CICS log manager does not support journal data sets, on either disk or tape[...]

Warning: When you migrate your CSD entries you must ensure that you do not copy over IBM supplied definitions in groups that you have defined. The reason is that some of the groups and resources were changed and/or deleted. Thus, you should see that your user groups with IBM defined resources are copied from the newly defined CSD. Once, you have im[...]

TRANSACTION/RESTART this option now governs restart in two separate types of situation. TYPETERM/RECOVNOTIFY the scope of this parameter is extended to cover VTAM persistent sessions. In CICS/VSE this parameter was meaningful for CICS regions running with XRF only. 6.1.8 CICS System Data Sets Requirements Before you install your CICS data sets you [...]

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

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 the ability to access and modify CICS system information. SPI should be considered for CICS applications that presently modify and/or access CICS internal blocks. Although, SPI commands will not grant a[...]

Your program must be in primary-space translation mode when you invoke the XPI. (For information about translation modes, see the IBM ESA/370 Principles of Operation manual.) Notes: 1 . Yo u cannot use all o f these calls at every global user exit point. You will find an indication of when these calls cannot be used both with the description of eac[...]

You must rewrite all user-replaceable modules except for DFHACEE, DFHUAKP, DFHXSP and DFHXSE user-replaceable modules, which are obsolete. Also, the DFHNTRY is replaced by a new user-replaceable module DFHREST. Note: VSE/ESA System Package (SP) supplied a number of user exits and user replaceable modules, that are part of the packaging of VSE/ESA. [...]

Bit 0 SYSIPT overrides yes or no. All overrides are passed as execution parameters to DFHSIP. Bit 1 This is no longer required for CICS/OS or CICS/VSE 1.6 or later. Bit 2 Operator prompt for overrides yes or no. The parameter ′ CONSOLE ′ as the last PARM in the EXEC statement indicates that the operator is to be requested to enter overrides. Bi[...]

• RPG II is not a supported language for CICS/OS. RPG II programs should be converted to a supported application language (that is, COBOL, PL/I, C++, and or Assembler). • Programs that directly invoke operating system services. • Programs that directly access operating system control blocks. • Programs that access internal CICS control bloc[...]

functions are provided by the Application Support Facility for MVS (ASF), 5685-043. Some CICS programs written in assembler language may have to be reworked. These applications are more prone to violate the CICS API restrictions. Also, be sure to review all EXEC CICS commands for changes in VALUES. The name of the CSECT within module DFHECI changed[...]

programs use CICS macros, which is very useful when you must determine your scope-of-effort. The CICS Application Migration Aid (5695-061), should be used to assist customers migrating macro-level programs to command-level programs. Please review the manual CICS/VSE Application Migration Aid Guide V2 , SC33-1901 for more detail. COBOL and CICS Comm[...]

• handling output from CICS dumps. • handling output from CICS trace. • handling output from CICS statistics. • problem determination. • restart and recovery requirements. • security administration. • application of software services. Identify and understand the different IBM and vendors support structures and procedures. You should h[...]

Chapter 7. ICCF and TSO DOS/VSE users of the Interactive Computing and Control Facility (ICCF) who migrate to OS/390 will find a very powerful interactive system available via OS/390 ′ s Time Sharing Option (TSO/E) and related products, particularly the Interactive System Productivity Facility (ISPF). This section addresses the TSO/E and ISPF imp[...]

You may choose to assign account numbers to your users for accounting or other purposes. This account number can be from 1-40 alphameric characters, not containing a blank, tab, quotation mark, apostrophe, comma, semicolon, or line control character. You use the RACF ACCTNUM resource class to authorize use of account numbers. Please refer to the TS[...]

7.1.2 LOGON Procedures In ICCF, a logon procedure may be specified in the user profile. This entry references an ICCF procedure or macro used to define the environment for this logon. These optional procedures or macros are normally defined by the user if they are present. In TSO/E, the LOGON procedure is not optional. The LOGON procedure defines t[...]

ICCF provides another level of security by defining ICCF libraries within DTSFILE as either PUBLIC, PRIVATE, or COMMON. All ICCF users have read access to data stored in the single COMMON library supported by ICCF. However, only ICCF users with a System Administrator level profile have write access to this library. Multiple PUBLIC ICCF libraries ar[...]

7.2.1 Accessing the System Since LOGON to TSO/E is dependent on the telecommunications access method used with TSO/E, the System Standards implemented by the Systems Programmer, and the related program products installed, you should reference the TSO/E Primer and your Systems Programmer for information on logging on to TSO/E. 7.2.2 Entering and Man[...]

Each field of a data set name consists of 1-8 alphameric characters and begins with an alphabetic or national ($, @, and #) character. The fields must be separated by periods. The total length of the name, including periods, must not exceed 44 characters. The data set naming conventions simplify the use of data set names. If the data set name confo[...]

7. 3 Executing Programs at a Terminal Both ICCF, TSO/E, and ISPF provide commands to compile, link-edit, and execute (or compile and load) your source program at the terminal. They also allow you to use other programs, such as utilities at the terminal. Under ICCF programs that expect input from the console will read input from your terminal. Card [...]

7.4 Submitting Jobs for Batch Execution ICCF allows users to submit jobs for batch execution through the SUBMIT procedure and an ICCF supplied program, DTSSUBMT. Tailoring of the SUBMIT procedure allows the ICCF System Administrator to provide system standards for execution and list and punch output. Listed output from the batch execution may be vi[...]

7.4.1 Using Command Procedures Both ICCF and TSO/E provide the capability of storing frequently executed commands or lists of commands. In ICCF these stored commands are called Procedures or Macros. They are stored as an ICCF library member. In TSO/E they are called Command Lists (CLIST) or REXX execs. Besides issuing TSO/E commands, CLISTs can per[...]

method over the first would be the total flexibility available in creating the tape input to IEBUPDTE and the JCL necessary to execute this MVS utility. The advantage of the first method is its ease of implementation. In order to write an ICCF procedure to create a ″ SYSIN ″ format tape for the execution of IEBUPDTE, you will need to answer que[...]

&&IF &&PARAM1 EQ ′′ && GOTO TAG3 &&SET &&VARBL3 &&PARAM1 &&LABEL TAG3 &&TYPE ENTER THE DESCRIPTIVE QUALIFIER FOR THE PDS TO BE CREATED &&TYPE THE DEFAULT WILL BE &&VARBL4 &&READ &&PARAMS &&IF &&PARAM1 EQ ′′ && GOTO TAG4 &a[...]

&&OPTIONS 1100001 /LIB FULL ALL &&OPTIONS 0010001 /LOAD DTSPROCS /OPTION NOPROMPT &&OPTIONS 0010001 /LIST 1 1 IEBUPDTE &&IF &&RETCOD NE *READY &&GOTO TAG11 /PURGE IEBUPDTE &&LABEL TAG11 /INPUT NOPROMPT DUMMY LINE /END /SAVE IEBUPDTE /EDIT IEBUPDTE NEXT GET $$PUNCH TOP DEL 1 L SYSIN NEXT DEL 2 [...]

delete the first character of each record, and will delete the END OF MEMBER statements. The last statement placed on the output tape will be the IEBUPDTE statement ./ ENDUP. This tape will then become the input to the IEBUPDTE utility on an MVS system. Information about the PDS to be created will be contained in the MVS JCL used to invoke IEBUPDTE[...]

168 VSE to OS/390 Migration Workbook[...]

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 (Data Language/One DOS/VS) Release 1.8 and IMS/ESA (Information Management System/Enterprise Systems Architecture) Versions 5 and 6. In the context of this chapter, references to DL/I may be used interchange[...]

8.1.2 MVS System Requirements IMS/ESA requires a Type 2 SVC in the MVS nucleus and a Type 4 SVC in LPALIB. IMS/ESA Resource Clean-up Module and ABEND Dump Formatting Routine must be link-edited into SYS1.LPALIB. IMSESA.RESLIB must be APF authorized. 8.1.3 Data Base Descriptor (DBD) 1 Automatic field start calculation Must code START= in the IMS/ESA[...]

SEQFLD= SRCH= of XDFLD SEQVAL= SUBSEQ= of XDFLD SUPVAL= NULLVAL= of XDFLD SUPRTN= EXTRTN= of XDFLD The non-ACCESS statement approach consists of an LCHILD and XDFLD following the target segment, SEGM statement, in the data portion of the database. Associated FIELD statements are needed in data DBD if /sx or /ck are used. An index DBD defining the i[...]

8.1.5.4 Statement Compatibility All batch programs using the calls, GU - GHU - GN - GHN - GNP - GHNP - ISRT - DLET - REPL, are transportable to MVS with no modification to the DLI calls. Of course, these programs may need changes for other reasons and they must be recompiled on the MVS system. VSE JCL is changed to MVS JCL, and the DL/I parameters [...]

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 exist in IMS/ESA. Their functions are similar, but it is necessary to change the JCL from VSE to MVS and utility control statements from DL/I to IMS/ESA. There are variations in the utilities between DL/I and IMS/ESA [...]

8.1.7.2 Backout Utility/Disk Logging IMS/ESA supports both DASD and tape logging in batch. The archive utility DFSUARC0, is used to copy disk logs to tape. Disk is acceptable as input to all IMS/ESA utilities including backout. 8.1.7.3 UPSI The use of the UPSI byte is not supported by MVS. The equivalents for the various bits are: • Bit 0: Readin[...]

8.1.8 Database Portability There are two fundamental approaches to making your DL/I databases available to IMS/ESA. One is to unload the database using DL/I utilities and reload it using IMS/ESA utilities. The other is to ″ position ″ your DL/I databases using DL/I and IMS/ESA compatibility options in the DBD during a normal database reorganiza[...]

Recovery of DL/I - IMS/ESA compatible databases require special procedures . Image copy, change accumulation, and log files are not compatible between DL/I and IMS/ESA. The recovering of database changes performed under DL/I must be performed using DL/I image copy, change accumulation, and log files with DL/I utilities; and the recovering of databa[...]

┌───────────┐ │ DL/I DBD │ └─────┬─────┘ ┌───────────┐ │ │ MVS GEN │ │ └─────┬─────┘  │ ┌───────────┐ │ │ UNLOAD DB │  └─────┬─────┘ ┌──────────?[...]

8.1.9 DL/I Multiple Partition Support Conversion to IMS/ESA BMPs (Batch Message Processing programs) running under DBCTL should be considered as an alternative to CICS/OS Shared Data Base or IMS/ESA Data Sharing support. 8.1.10 Additional Information A recently announced Redbook, Interoperability between VSE DL/I and OS/390 IMS DBCTL , SG24-5249, c[...]

systems and security folks. This is not to say that differences do not exist, just that they are minor and should not be perceived by most end users. QMF users should see virtually no differences. The one possible exception is the TRANSLATE scalar function which is not supported by DB2. 8.2.1.2 Application Developers While end users will see little[...]

8.2.1.3 Database Administrators (DBAs) As with the previous two groups discussed, there are really more similarities than differences between the two products for the DBA. The design methodology is the same, whether you prefer normalization or some other technique. The optimizer selects access paths basically the same way, relieving the DBA from ma[...]

At the physical level, in DB2 each tablespace is stored in a pageset, which consists of one or multiple VSAM ESDS data sets or LDSs. In SQL/DS, data is stored in storage pools that are composed of one or more dbextents. In VSE, a dbextent consists of one VSAM ESDS data set. While this may seem similar, the difference is that in DB2 one VSAM data se[...]

• 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 Considerations DRDA level of functions in SQL/DS are upward compatible to DRDA functions in DB2. DB2 has more DRDA functions than SQL/DS. For the DRDA Remote Unit of Work (RUW) level, DB2 is compliant as an [...]

7 Migrate the user queries 8 Migrate user profiles and authorizations 9 Change operational procedures to reflect new backup/recovery, problem determination and startup/shutdown procedures Chapter 8 . Databases 183[...]

184 VSE to OS/390 Migration Workbook[...]

Chapter 9. Telecommunications Subsystems VSE and OS/390 platforms rely on the same set of communications products and protocols. Although the product sets are the same, some differences exist in product implementation and usage. The differences are primarily related to the operating systems and their file structures. This chapter will discuss the s[...]

9.1.1 Product Installation The VTAM installation procedures for OS/390 are very different from those for VSE, since this is the area where the operating system differences are most influential. To install OS/390 VTAM you must perform the following steps: • Allocate data sets for VTAM. OS/390 VTAM can make use of a large number of data sets, depen[...]

(from ACF/SSP) and user-written VTAM exits. In our example STEPLIB points to the ACF/SSP library which contains the NCP loader. Any libraries defined by STEPLIB are PDSs containing load modules, and have similar DCB characteristics to SYS1.LINKLIB. 4 VTAMLIB contains VTAM tables which are assembled and linked, such as the subarea Class of Service t[...]

The current supported levels of VTAM on VSE are V3R4 and V4R2. VSE VTAM V4R2 is available in three different functional level packages: • Client/Server • MultiDomain • InterEnterprise Packages are priced according to the amount of function provided and are password enabled via the VTAM start procedure. The eNetwork Communications Server for O[...]

 The 3174 with a Token-Ring or Ethernet adapter provides direct connection to Token-Ring and Ethernet LANs.  The Open Systems Adapter (OSA) on the CMOS processors provides direct connection to Token-Ring, Ethernet and FDDI LANs. It also supports native ATM connections for VTAM V4R4 and above.  The 3172 Interconnect Controller provides dire[...]

without disruption. Sessions are simply taken over by a new copy of the application running in the same, or a different, processor. 9.1.2.1 Resource Definition The OS/390 VTAM resource definitions are stored in the VTAMLST data set. Most of the VSE/VTAM resource definitions (B-books), typically stored in the PRD2.CONFIG VSE library, can be moved di[...]

9.1.3.2 Programming Any coding done under VSE, such as VTAM exits, will almost certainly need rewriting (and will certainly need re-linking) for the OS/390 environment. Also, some VTAM exit routines may be implemented differently under VSE and OS/390. User-written VTAM programs and exits must be reviewed carefully for compatibility. Please refer to[...]

9 . 2 ACF/NCP ACF/NCP in a 37XX controller may itself be completely independent of the operating system in the host, but the generation and loading of such an NCP is very much dependent on the operating system. 9.2.1 Product Installation Differences in the installation procedures of NCP for VSE and OS/390 are basically the same as those for VTAM. T[...]

• On the PCCU statement there are DUMPDS, MDUMPDS and CDUMPDS keywords which refer to various data sets which will contain NCP dumps. Code the names of the DD statements in the VTAM procedure which will point to the actual data sets. • On the BUILD statement, the LOADLIB keyword specifies the DD name of the data set which VTAM will use to find [...]

One of the reasons why TCP/IP is so popular is that there are many simple and useful standard applications available. The TCP/IP on VSE/ESA for example provides standard applications such as Telnet, FTP, LPR/LPD and the HTTP Web server. Using these standard TCP/IP applications and standard TCP/IP APIs for user written applications also allows an ea[...]

9.4.2 TCP/IP Configuration First of all, configure the UNIX System Services (part of the OS/390 base product) in order to enable TCP/IP on OS/390. As a second step you will have to customize TCP/IP on OS/390. 9.4.2.1 TCP/IP Customization On VSE/ESA, almost all TCP/IP customization information is located in one file, the IPINIT.L initialization file[...]

9.4.5.1 TCP/IP Applications using the Sockets API for Assembler VSE/ESA applications based on the SOCKET Assembler macro cannot be used on an OS/390 system. They have to be recoded for the OS/390 TCP/IP. 9.4.5.2 TCP/IP Applications using the Preprocessor API The HLL preprocessor API which is available on VSE/ESA for PL/I, Assembler and COBOL is not[...]

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 as a Web Server SC33-6686 Writing Interlanguage Communication Applications OS/390 SC28-1890 OS/390 OpenEdition MVS Planning SC28-1906 OS/390 OpenEdition MVS Communications Server Guide GC28-1920 OS/390 Security Ser[...]

• your MQSeries based applications. In the next sections each of these topics will be addressed at a general level. No detailed checklists or migration guidelines are given. This would go beyond the scope of this chapter. The purpose of this discussion is to make you aware of the areas which need to be studied in detail when you intend to migrate[...]

The following list shows the required products with product numbers: • VSE/ESA Version 1.4 (5750-ACD) in ESA mode, with:  CICS for VSE/ESA Version 2.3 (5686-026)  IBM Language Environment (LE) for VSE Runtime Library (5686-067)  ACF/VTAM for VSE/ESA V3.4 (5666-363) or • VSE/ESA Version 2.1 (5690-VSE), with:  CICS for VSE/ESA Version[...]

The following languages and compilers are supported for MQSeries applications: • Assembler  Assembler H (5668-962)  IBM High level assembler MVS (5696-234) • COBOL  VS COBOL II (5668-958)  IBM COBOL for MVS & VM Release 2 (5688-197) • C  C/370 Release 2.1.0 (with APAR UN37741) (5688-187)  IBM SAA AD/Cycle C/370 (5688-216[...]

• install required CICS and IMS adapters • define queues • set up distributed queuing Customization is described in detail in the MQSeries for MVS/ESA System Management Guide . Only the steps which are related to migration are discussed in some more detail in the following sections. After the installation and customization has been completed,[...]

an MQSeries termination, and automatic resource resynchronization after a restart. The CICS adapter is supplied with MQSeries as the CICS transaction CKQC. 9.5.1.4 Data Sets MQSeries for VSE/ESA uses the following data sets: • the System Setup file: a VSAM ESDS file containing system setup information. It is only used once to initialize the Syste[...]

9.5.2 Networking Definitions You will have some other systems with an MQSeries product installed which are connected to your VSE/ESA to allow MQSeries applications to communicate. When you migrate your VSE/ESA to OS/390 you will have to re-establish connection to those systems. In this section we will discuss the networking considerations. There ar[...]

4. namelists 5. process definitions 6. storage classes These objects can be manipulated, that is, defined, deleted, changed, by the MQSeries commands. Commands can be issued from: • the initialization input data sets • the MVS console • the system-command input queue • the COMMAND function of the CSQUTIL utility • the operations and contr[...]

• for channel definitions under CICS/ESA find matching channel attributes in MQSeries Distributed Queuing Guide , SC33-1139 • define the channels using the CKMC CICS transaction. Note: Make sure that you use the same queue names in your OS/390 related definitions which you used under VSE/ESA whenever possible. This will minimize application cha[...]

No special considerations apply to the compile and link step under VSE/ESA except that the product library which contains MQSeries for VSE/ESA has to be in the library chain during compilation. You have to set up jobs to compile and link the program under OS/390. General considerations how to do this for a CICS COBOL application are described in th[...]

Chapter 10. POWER and JES2 10.1 JES2 Introduction VSE uses POWER as a spooling system. MVS uses either JES2 or JES3 as spooling systems. This chapter only addresses migrations from POWER to JES2. While POWER and JES2 are similar in their overall function, they are very different in design and specific implementations. Because of these differences i[...]

10.1.1.2 Time Event Scheduling for Jobs POWER supports the scheduling of job submission based on a one-time or repetitive schedule such as daily, weekly on a given day and time, and so on. JES2 has a primitive ″ automatic command scheduling ″ facility, but you will probably need an automated job scheduling package in OS/390 to do the same thing[...]

can write your own using JES2 exit 1. (For PSF controlled printers, use PSF exits APSUX01 and APSUX02.) For separators between individual data sets or data set copies, you must specify SEPDS=YES on the PRT(nnnn) statement and provide a JES2 Exit 15 for JES2 controlled printers. (For PSF controlled printers, use PSF exit APSUX03.) 10.1.1.6 End-of-pa[...]

POWER | JES2 ┌──────────────┐ | ┌──────────────┐ │ │ │ Checkpoint │─┐ │ Queue file │ | │ Data set │ │ │ │ │ (Incl. Job & │ │ │ │ | │ Output Queue│ │ └──────────────┘ └─────────────[...]

JES2 initialization options described in Chapter 1 of the OS/390 JES2 Initialization and Tuning Guide . 10.2.2.1 The JES2 Procedure Similar to the POWSTRT procedure, the JES2 member of SYS1.PROCLIB is used to initialize JES2. (It must be in SYS1.PROCLIB, not in any other procedure library.) You must tailor the JES2 proc to include your JES2 load li[...]

• Network Job Entry (NJE) • Application Programming Interfaces • Accounting • RAS Characteristics • Testing Techniques Note: The comparison is based on the functions provided within VSE/POWER. Therefore, it is not a complete overview of all functions available in JES2. 10.3.1.1 Multiple System Support In POWER, the Spool File can be share[...]

10.3.3 Job Scheduling POWER and JES2 both manage the job input queue and manage the job selection for execution according to job classes, priority and in the order they were submitted. In addition, OS/390 V2R4 provides additional capability with the workload management of batch jobs according to installation specified performance objectives. Table [...]

10.3.3.2 Serializing Job Execution JES2 does not guarantee that jobs will run in the order they are submitted. If you need to make certain jobs run in order or you need dependent job control, you should submit them one at a time or use an automated job scheduling product such as OPC/A. 10.3.3.3 Time Event Scheduling POWER supports the scheduling of[...]

10.3.4 Output Service As with POWER, JES2 supports line-mode printers, whereas PSF controls AFP Printers. (See Chapter 11, “Advanced Function Printing and Print Services Facility/MVS” on page 235 for AFP printing.) Table 13 (Page 1 of 2). POWER/JES2 Output Service Comparison Output Service Function POWER JES2 JES2 Comments Local Line Printer (3[...]

Table 13 (Page 2 of 2). POWER/JES2 Output Service Comparison Output Service Function POWER JES2 JES2 Comments End-of-Page sensing Y N Se e 10.1.1.6, “End-of-page Sensing” on page 2 0 9 Counting Line Mode Output Y (Pages = skip to Ch.1) Y (Lines) S e t PRINTDEF NEWPAGE=1 Counting Page Mode Output Y (Pages) Y (Pages) Restart capability for interr[...]

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 PSETUP” on page 208 for some alternatives. 10.3.4.5 Separator Page Differences The IBM provided separator pages are different with JES2. See 10.1.1.5, “Separator Page Difference” on page 208 for more informati[...]

FCB Specification POWER users specify the full eight-character FCB name, whereas OS/390 users only specify the last four characters. POWER supports device-independent specification of FCB-image phases in the * $$ LST statement by allowing ″ $$$$ ″ as the first four characters. POWER then replaces the dollar signs by a character string depending[...]

Jobs can be submitted with the TSO/E SUBMIT command, any ISPF EDIT panel, or SDSF using the SJ command on any job display. Output can be browsed with the TSO/E OUTPUT command, the ISPF 3.8 panel, or SDSF using the O (output) or H (Held output) panels. The preferred interface is through SDSF. Table 15. POWER/ICCF, VM/CMS, and JES2/TSO Functional Com[...]

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 Table 19 on page 228, and Table 20 on page 229 for a comparison of POWER PRMT macros and JES2 RMT parameters. 10.3.6.3 R J E Operations See 28.6.1, “JES2 RJE Operations” on page 452 and JES2 Commands [...]

10.3.7.1 NJE Definitions Use the following JES2 initialization statements to define your NJE network and networking options: TPDEF BSC & SNA Buffer Sizes, and Number of SNA Sessions NJEDEF Number of Nodes, Transmitters, Receivers, and other NJE options NODE Individual NJE node definitions APPLID VTAM Applid of NJE nodes (if not the same as Node[...]

Job Information Services Current Job Identification If you have code that is called by an MVS application, you can obtain information about the job currently running in an address space with the IAZXJSAB macro. You can retrieve information such as: • Name of the subsystem that scheduled the job • Job identifier • Job name • User ID associat[...]

Subsystem Version ID You can obtain version-specific information about a subsystem with SSI function code 54. See Using the Subsystem Interface . Command Interface You can also use the MGCR service to submit JES2 or MVS operator commands to control jobs. See OS/390 MVS Auth Assembler Services Guide , GC28-1763. 10.3.9 Accounting Comparisons 10.3.9.[...]

NJE Network Management Records JES2 records the following information reflecting network events: • SMF 55 Network Signon • SMF 56 Network Integrity (invalid password) • SMF 58 Network Signoff See System Management Facilities for details. NJE Accounting Most NJE related information is carried in the NJE headers as the job is routed from node t[...]

• Operator Monitor Spool Utilization • Spool Full Condition - $S SPL upon warning (Output limits minimize this) • An external message-based automation product can also delete, offload or reroute spool files. 10.3.11 JES2 Testing Techniques Just as it is important to test new levels of OS/390 in your environment before using them in production[...]

Table 17 (Page 1 of 2). POWER Macro to JES2 Parameter Mapping POWER Parm Description JES2 Parm Comment or Recommendation ACCOUNT Job Accounting Information to be collected/recorded. JOBCLASS TYPE6, TYPE26 SMF records are collected based on SYS(TYPE(nn:nn)) parm in PARMLIB(SMFPRMxx) CLRPRT Clear 3800 page buffer at EOJ N/A Option not supported by JE[...]

Table 17 (Page 2 of 2). POWER Macro to JES2 Parameter Mapping POWER Parm Description JES2 Parm Comment or Recommendation SECNODE VSE Security ″ Zone ″ N/A (Use RACF NODES class profiles for security.) SHARED Shared systems and accounting file N/A JES2 always assumes shared systems. Accounting files cannot be shared. SNA= wscount, password, appl[...]

Table 18. PLINE MACRO to JES2 Parameter Mapping PLINE Parameter Description JES2 LINE Parameter Comment ADDR= Unit address of the BSC emulator port or CTC adapter UNIT= ″ SNA ″ or unit address (4-digit addresses supported) CODE EBCDIC is the only value allowed. (ASCII is not supported) LINECCHR= EBCDIC or USASCII supported INTRPT Selector chann[...]

Table 19 (Page 2 of 2). PRMT MACRO to JES2 Parameter Mapping PRMT Parameter Description JES2 R M T Parameter Comment MSGSPCE Suppress four space-3 commands after messages N/A PUN Width of card punch records N/A (always 8 0 ) PUNROUT default punch routing ROUTECDE Same for print and punch in JES2 REF Short form for replication N/A Use ranges: RMT(m-[...]

10.4.1.5 Define NJE Nodes This table shows the conversion of POWER PNODE parameters to JES2 parameters. Table 21. PNODE MACRO to JES2 Parameter Mapping PNODE Parm Description JES2 Parm Comment NODE= Name of the NJE node NODE NAME= LOCAL This is the local node. NJEDEF OWNNODE= APPLID VTAM Appl-ID APPL(name) NODE= Defaults to node name. (Use LOGONn f[...]

Table 23. POWER Exit t o JES2 Exits POWER Exit Description JES2 Exit Comment JOBEXIT Job input - Scan JCL & JECL (POWER exits allow access to SYSOUT data.) EXIT(2) EXIT(3) EXIT(4) JOB statement scan JOB accounting field Other JCL & JECL (No access to SYSIN data.) NETEXIT Input from NJE node EXIT(47) NJE Headers Received (No access to SYSIN [...]

10.4.3.1 Queue Management Commands Table 24. Queue Management Commands POWER Command Code PWR Short Form Function JES2 Command Verb PALTER A Alter processing attributes of a POWER job or a POWER controlled partition $T PDELETE L Delete queue entries $P PDISPLAY D Display the status of jobs, messages, resources, and the network $D PHOLD H Put a job [...]

10.4.3.3 Control Commands Note: There is no equivalent function in JES2. See 10.1.1.4, “Printer Forms Alignment via PSETUP” on page 208. Table 26. Control Commands POWER Command Code PWR Short Form Function JES2 Command Verb PACCOUNT J Save account file records. (SMF) PBRDCST B Transmit a message. $DM, $M PINQUIRE I Display the status of a BSC [...]

N/A = No available operator command File Control The following table shows the various operator commands that control jobs (SYSIN or SYSOUT, ″ files ″ to RSCS) on the various systems. Note that there are also global ($G..) commands for JES2 which can be used to control jobs on other nodes. Sending Commands and Messages The following commands ar[...]

Chapter 11. Advanced Function Printing and Print Services Facility/MVS 11.1 Introducing PSF/MVS Print Services Facility (PSF) is the Advanced Function printing (AFP) printer-driver program for VSE and OS/390, as well as AIX, OS/2, VM and OS/400. PSF has similar capabilities in all environments, plus differences unique to the operating system on whi[...]

• 11.2, “Installing and Configuring PSF/MVS” • 11.3, “Setting up AFP Resources” on page 2 4 0 • 11.3.4, “Migrating Print Applications” on page 2 4 1 • 11.4, “Understanding Operational Differences” on page 2 4 2 • 11.5, “Other Differences” on page 2 43 Other tasks are similar between the two platforms. 11.2 Installing a[...]

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 print from PSF to LAN connected printers through TCP/IP: • IP PrintWay • MVS/Download and PSF/6000 and InfoPrint Manager • MVS/LANRES • TCP/IP for MVS Network Print Facility • Directly attach Network IPDS pri[...]

11.2.5 FSS Procedure and PRINTDEV Statements Below is the sample FSS proc shown in the PSF/MVS Systems Programming Guide . //SAMPPROC PROC //STEP01 EXEC PGM=APSPPIEP,REGION=4096K,TIME=1440 //STEPLIB DD DSN=PSF.LINKLIB,DISP=SHR //JOBHDR OUTPUT PAGEDEF=V06483, /* JOB HEADER PAGE */ // FORMDEF=A10120,CHARS=GT12 /* FORMDEF: ALTERNATIVE BIN*/ //JOBTLR O[...]

Table 30. PRINTDEV Parameter Comparison PSF/VSE PRINTDEF Parameter OS/390 Equivalent Parameter Description and Comment ASA (not necessary) ASA control records do not need conversion CKPTPAGE JES2 parm: PRT(nnnn) CKPTPAGE Number of pages to be printed before a checkpoint is taken. FONTPR PSF APSUX07 Exit (Resource management exit) Whether font pruni[...]

11.3 Setting up AFP Resources PSF/MVS supports resources in the system libraries defined in the PRINTDEV statement, and dynamically on a per-job basis via the USERLIB JCL statement. 11.3.1 Migrating Resources from VSE to OS/390 11.3.1.1 Defining Resources If you have the source definition files for these resources, you can use the same process to d[...]

PSF/MVS utility APSRMARK against these ported VSE resources in order for PSF/MVS to consider these resources ′ marked ′ for printer residency. (Printer resident fonts shipped with PSF/MVS are already ′ marked ′ with the APSRMARK program.) 11.3.3 Transferring Print Streams - VSE and OS/390 Coexistence You can use NJE to transmit AFPDS (also [...]

OS/390 Dynamic Allocation and Output Descriptor Macros Traditional SYSOUT attributes can be specified on the DYNALLOC macro. AF P attributes can be specified on the OUTDES macro. 11.3.4.4 High Level Language Programming Interfaces COBOL Applications Creating AFP in COBOL is essentially the same between MVS and VSE. V S E code will run in MVS unchan[...]

Table 31 (Page 2 of 2). VSE - OS/390 C om m a nd Comparison VSE or POWER Command JES2 Command Comment PSTOP devname [ ,EOJ | RESTART | FORCE. ] $P PRTnnnn $I PRTnnnn F FSSx,FORCE,PRTnnnn Drain the printer - wait for current job to finish - interrupt current job, restart from ckpt - Only use if nothing else works PXMIT devname [ ,CLASS= ] [ ,LOGDEST[...]

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, this data is recorded by SMF in the Type 6 records written by PSF. 11.6 References 11.6.1 PSF/VSE Publications • VSE/ESA Program and Workstation Guide , SC33-6509 (moving VSE files) 11.6.2 PSF/MVS Publi[...]

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 support, software solutions and so on. Specifically, the following tools are available from the http://www.printers.ibm.com/tools.html site or FTP from ftp://ftp.software.ibm.com/printers/tools/vs[...]

246 VSE to OS/390 Migration Workbook[...]

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

248 VSE to OS/390 Migration Workbook[...]

Chapter 1 2 . COBOL 12.1 Introduction This chapter introduces IBM COBOL for OS/390 and VM (program number 5648-A25), which is the COBOL compiler available with OS/390. It also outlines the differences between the three COBOL compilers that are available on VSE and COBOL for OS/390 and VM. Various strategies for converting your VSE COBOL application[...]

12.1.2 Comparison of IBM COBOL Compilers Figure 18. Comparison of IB M COBOLs DLL Support Extensions for: Object-Oriented COBOL C Interoperability Intrinsic Functions Amendments to ′85 Std Support for: Language Environment Debug Tool Intrinsic Functions Amendments to ′85 Std Support for: Language Environment Debug Tool COBOL 85 Standard No Intr[...]

Under VSE/ESA version 1 release 4, and VSE/ESA version 2 and above, the COBOL compilers available were DOS/VS COBOL, VS COBOL II, and COBOL for VSE/ESA; CCCA/VSE is available to aid the conversion process. Now, only the COBOL for VSE/ESA product is available. If you are running DOS/VS COBOL, you will have to convert your code to a new COBOL compile[...]

Table 32. Useful COBOL Publications Publication Title Form Number COBOL for OS/390 and VM Compiler and Run-Time Migration Guide GC26-4764 COBOL for OS/390 and VM Language Reference SC26-9046 COBOL for OS/390 and VM Programming Guide SC26-9049 COBOL for VSE/ESA Migration Guide GC26-8070 COBOL for VSE/ESA Programming Guide SC26-8072 OS/390 Language E[...]

12.3.2 DOS/VS COBOL Programs Containing REPORT WRITER Statements COBOL for OS/390 and VM does not support the REPORT WRITER statements. However, you can keep your REPORT WRITER statements by using the COBOL Report Writer Precompiler prior to the new compiler. Alternatively, you can use the COBOL Report Writer Precompiler to convert your REPORT WRIT[...]

Fo r 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 COBOL for OS/390 and VM you will receive the message: IGYDS1064-E A ″ REDEFINES ″ clause was found in the definition of a level-01 item in the ″ FILE SECTION ″. The clause was discarded. This coding practice is documented [...]

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 VM, program switches can be tested by use of a one-byte switch in the SPECIAL-NAMES paragraph, specified as UPSI-0 through UPSI-7 . In VSE, the setting of these program switches at execution time is ac[...]

ASSIGN Clause The format of the ASSIGN clause has become simpler. COBOL for OS/390 and VM may sometimes allow the DOS/VS COBOL format but may produce unexpected results at run-time. Refer to the COBOL for OS/390 and VM Compiler and Run-Time Migration Guide for more information. 12.4.3 DATA DIVISION - FILE DESCRIPTION (FD) BLOCK CONTAINS In OS/390 i[...]

12.4.4.1 Program Termination There are three COBOL program termination statements: • EXIT PROGRAM • GOBACK • STOP RUN There are some differences in the effect of these statements between DOS/VS COBOL and COBOL for OS/390 and VM. Table 33 gives a comparison of the behavior of these COBOL program termination statements, for DOS/VS COBOL and COB[...]

12.4.5.2 File Attribute Mismatches DOS/VS COBOL file open processing does not always check that the attributes of the file definition in your program exactly match the file attributes of the physical file (for example, as defined for a VSAM file in the LISTCAT). To conform with ANSI 85 requirements, COBOL for OS/390 and VM open processing carries o[...]

12.5.1 V S COBOL II CICS Programs COBOL for OS/390 and VM and OS/390 do not support CICS macro-level programs. If you have any programs written in macro-level CICS you must convert them to command-level CICS. If you need to change your programs to cater for these differences, you can do so before you migrate them to OS/390. Then, if you prefer, you[...]

12.8 Compiler Options This section discusses some of the compiler option considerations when converting from the various VSE COBOL compilers to COBOL for OS/390 and VM. DOS/VS COBOL has many compiler options that are not available with COBOL for OS/390 and VM. Compiler options with VS COBOL II or COBOL for VSE/ESA are generally the same as COBOL fo[...]

Figure 19. Compiler Options Comparison DOS/VS COBOL and COBOL fo r OS/390 an d VM 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 FLAG(E)/FLAG(W) FLOW/NOFLOW None LANGLVL(1/2) None. COBOL for OS/390 and VM supports only the [...]

Figure 20. Recommended COBOL for OS/390 an d V M Compiler Options f or Converted V S COBOL II Programs COBOL for OS/390 and VM Option Comments PGMNAME(COMPAT) If compiling with COBOL for OS/390 and VM use this option to ensure that COBOL for OS/390 and VM processes program names in a similar manner as VS COBOL II. RMODE(AUTO) Use RMODE(AUTO) or RMO[...]

Figure 21. Compiler Options Comparison VS COBOL I I and COBOL fo r OS/390 an d V M VS COBOL II Option Comments FDUMP/NOFDUMP COBOL for OS/390 and VM does not provide the FDUMP compiler option. For existing applications, FDUMP is mapped to the COBOL for OS/390 and VM compiler option TEST(SYM). This provides equivalent function and more. Language Env[...]

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 RECURSIVE ANY END-INVOKE INVOKE REFERENCE BINARY END-MULTIPLY KANJI REPLACE CANCEL END-PERFORM LENGTH REPOSITORY CLASS END-READ [...]

12.9.2 Reserved Word Considerations for VS COBOL II and COBOL for VSE/ESA There are two reserved words in COBOL for OS/390 and VM that are not reserved in VS COBOL II. These are shown in Figure 25. They are reserved in COBOL for VSE/ESA. FUNCTION PROCEDURE-POINTER Figure 25. Reserved Words in COBOL fo r OS/390 a nd V M an d n ot i n VS COBOL II The[...]

266 VSE to OS/390 Migration Workbook[...]

Chapter 1 3 . Assembler 13.1 Assembler Products In OS/390, the High-Level Assembler for MVS and VM Program Product (5696-234) is required for system generation (SYSGEN) and maintenance activities. It can also be used for application programming projects, and must be used when assembler routines are designed for 31-bit addressing facilities. See Hig[...]

The selection of a particular option of MVS may require redesigning the application programs. In addition, a program logic change may also be forced by attempting to simulate a VSE function under MVS. Examples of these possibilities include multitasking, interrupt handling, and communication region accessing. The input and output components of the [...]

13.2.1.1 Initiation Under VSE, main programs (those programs that are invoked by the operating system directly) are not required to save any registers upon entry. VSE assembly programs are not required to provide a save area unless that program invokes (calls) another program. In MVS, all programs are executed as subroutines including the program t[...]

PROGA START PROGB CSECT PROGC CSECT BALR (VSE) (VSE) USING . . .. . . ST 13,SAVEB+4 ST 13,SAVEC+4 .. . Application Application Application Program Program Program Logic Logic Logic .. . LA 13,SAVEA LA 13,SAVEB . CALL PROGB CALL PROGC . EOJ(Return) Return(PROGA) Return(PROGB) SAVEA DC 18F ′0′ SAVEB DC 18F ′0′ SAVEC DC 18F ′0′ END END END[...]

contained in register 13. Therefore, you must specify a save area to receive the registers. PROGA START PROGB CSECT PROGC CSECT (MVS) (MVS) (MVS) . . . . . . STM 14,12,12(13) STM 14,12,12(13) STM 14,12,12(13) ST 13,SAVEA+4 ST 13,SAVEB+4 ST 13,SAVEC+4 LA 11,SAVEA LA 11,SAVEB LA 11,SAVEC ST 11,8(13) ST 11,8(13) ST 11,8(13) LR 13,11 LR 13,11 LR 13,11 [...]

VSE CALL Entrypoint ,(PARAMETER LIST) (15) MVS CALL Entrypoint ,(ADDRESS),VL (15) ,ID=number Call is used the same way in MVS as it is in VSE, except when it is used with the LOAD macro. For a discussion of this difference, see the topic “LOAD Macro” on page 277 in this section. In addition, if a variable number of parameters may be passed, the[...]

Under MVS, the RETURN macro returns control to the calling program and signals normal termination of the returning program. Control returns after restoring the address of the calling program ′ s save area into register 13. The return is made by executing a branch instruction using the address in register 14. You can write the RETURN macro to rest[...]

When this program received control from MVS Reg. 13 contained address of MVS save area. Reg. 14 contained address of MVS return. Reg. 15 contained address of this program ′ s entry point. PROGA START SAVE (14,12),,* Store Regs in MVS save area + B 10(,15) + DC AL1(5) + DC CL5 ′ PROGA ′ + STM 14,12,12(13) LR 12,15 Load start address in Reg 12 [...]

region in register 1. The first eight bytes of the communication region is the date in the form MM/DD//YY (month/day/year) or DD/MM/YY (day/month/year). Job Name The VSE communication region contains the job name that appears in the JOB control statement. This name remains for the duration of the job and can be used in a job by using the COMRG macr[...]

is an explicit request. If a separate module is requested, then the additional virtual storage requirement is implicit in that request. The MVS GETMAIN macro is an explicit request for additional virtual storage. You can use GETMAIN to obtain a single block or multiple blocks of virtual storage. You can specify either a fixed or variable amount of [...]

programs. You can also leave the tests in your program and provide an UPSI constant in your COMRG macro that would always satisfy the tests. • The MVS macro instruction TIME provides the system date (Julian or Gregorian) in a user work area. The date is in packed decimal digits, such as X ′19980323′. For details, see the section “GETIME Mac[...]

(MVS) LOAD EP=PROGB LOAD the load-module LR 15,0 pass address CALL (15),parm1,parm2 invoke PROGB FETCH Macro The VSE FETCH macro loads the phase specified in the first parameter and passes control to the address specified by the second. The MVS LINK and XCTL macros pass control to a specified entry point. When modifying programs from VSE to MVS, us[...]

The MVS TIME macro has an additional operand MIC,address that causes the time of day to be returned in the eight-byte area specified by the address. The time of day is in microseconds, with bit 51 equivalent to one microsecond. Register 0 contains 0, and register 1 contains the date. System Operand Register Content VSE STANDARD H HM MS S MVS DEC HH[...]

┌─────┬──────┬──────────────────────────────────────────┐ │ VSE │ PDUMP│ address1 , address 2 ,MFG=area │ │ │ │ r1 r2 (S,area) │ ││ │ r 3 │ ├─────┼──────┼──────────[...]

CANCEL Macro ┌───────┬───────────┬────────────────────────────────┐ │ VSE │ CANCEL │ ALL │ ├───────┼───────────┼──────────────────────────?[...]

CHKPT Macro ┌─────┬────────┬────────────────────────────────┐ │ │ │ res─ar─ address │ │ │ │ SYSnnn, (r1) │ │ │ │ , end address , ─poin─er │ │ VSE │ CHKPT │ (r2) (r3) │ │ │ │ dpoin─er , filename │ │ ?[...]

13.2.2 Multitasking Macros Under VSE, when you specify asynchronous processing at system generation time, the multitasking group of macros is supported to permit more than one task to execute within each partition. Each subtask must be initiated by the main task: control then passes to the subtask. The storage protection key and priority of the par[...]

ENTRYPOINT In VSE, it defines the storage address of the entry point of the subtask. The entry point must be in storage before the subtask can be successfully attached. The EP, EPLOC or DE parameter in MVS causes the required module to be loaded into storage (if it is not already in storage) and begins execution at the entry specified. The entry-po[...]

terminate normally. MVS does not permit the subtask to issue its own DETACH. If neither ECB nor ETXR is specified in the ATTACH, the subtask is removed from the system automatically at normal termination. In this case, no DETACH should be issued. 13.2.2.2 WAIT/POST Macros The two operating systems provide macros that synchronize task execution if o[...]

as complete. This number may be less than or equal to the number of ECBs specified in the macro. 13.2.2.3 RCB/ENQ/DEQ Macros This set of macros enables you to protect data files or other resources when processing a multitasking environment. The VSE RCB macro generates an aligned doubleword resource control block that functions much like an ECB. The[...]

13.2.3 Interrupt Handling Routines Interrupt routines take care of the interval timer, abnormal conditions, and operator communication interrupts. Abnormal condition interrupts will not be addressed in this publication. 13.2.3.1 Interval Timer Interrupts Basically, the two ways of utilizing the interval timer in your programs are routine handling a[...]

Wait Handling This method of using the interval timer allows you to set the timer and wait for the time to elapse. The job or task is prevented from executing until the interrupt occurs. ┌─────┬──────────┬──────────────────────────┐ │ │ TECB │ │ │ ?[...]

The preceding combination of VSE macro instructions allows you to execute a routine when an operator attention interrupt occurs and to return to the program that was being executed before the interruption. MVS has no equivalent function. It is possible, however, to simulate this function by using the WTOR macro. This MVS macro writes a message requ[...]

13.2.4.2 RELPAG Macro The MVS PGRLSE and PGSER RELEASE macros have functions similar to the VSE RELPAG macro. ┌─────┬────────┬─────────────────────────────┐ │ VSE │ RELPAG │begin addr , end addr,777 │ │ │ │ (2-12) (2-12) │ │ │ │lis─na[...]

• CATALOG=YES/NO - NO is used if the catalog is to be processed as a normal cluster with normal GET/PUT macros. Programs must be APF-authorized to process a catalog as a data set. • MACRF=( − ICI - Improved-Control-Internal-Processing (ICIP) is to be used. ICIP is a VSAM ″ fast-path ″ that reduces CPU utilization. However, the functions t[...]

• MSGLEN=length - The length of the MSGAREA specified above. The size of a message is 128 bytes. • OPTCD=(  ASY - Asynchronous access; VSAM returns control to the program after scheduling the request so the program can do other processing while the request is earned out. SYN is the default and specifies that VSAM will return to the processin[...]

13.2.6.1 List and Execute Macro Forms The list and execute forms of data management macro instructions, used together provide the same services available from the standard form of the macro. The list form of the macro provides a parameter list to be passed to either the control program or another problem program, depending on the micro instruction.[...]

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 given control. You can use this routine to analyze exceptional conditions or uncorrectable errors. The error can be skipped or accepted, or processing can be terminated. If an input/output error occurs during data transmi[...]

VSE DTFCD MVS DCB DSORG=PS DEVADDR = SYSxxx DDname (in DD statement) IOAREA1 = xxxxxxxx BUFNO = 1 or IOAREA1 = xxxxxxxx BUFNO = 2 or more IOAREA2 = xxxxxxxx ASOCFLE = xxxxxxxx UNIT=AFF=ddname (in DD statement) BLKSIZE = nnn BLKSIZE = nn CONTROL = YES MACRF = (..C..) for input only CTLCHR = YES RECFM = (...M) ASA (...A) SSELECT = n DEVD = ..,..,STAC[...]

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 MVS GET CARD,WORK . CLOSE CARD CARD DCB DSORG=PS,MACRF=(GM), C DDNAME=SYSIPT,EODAD=END, C RECFM=FB,LRECL=80 Figure 33. Card File Programs in V S E and MVS 13.2.6.6 LIOCS Printer File Definition The[...]

VSE DTFPR MVS DCB DSORG=PS DEVADDR = SYSxxx DDname (in DD statement) IOAREA1 = xxxxxxxx BUFNO = 1,MACRF =(..M..) or IOAREA1 = xxxxxxxx BUFNO = 2 or more 1OAREA2 = xxxxxxxx ASOCFLE = xxxxxxxx UNIT=AFF=ddname (in DD statement) BIKSIZE = nnn BLKSIZE = nnn CONTROL = YES MACRF = (PC) CTLCHR = YES RECFM = (..A) ASA (...M) DEVICE = nnnn UNIT = (in DD stat[...]

Note: You can specify any number of dcbaddresses and associated options in the OPEN macro instruction. CLOSE Macro 1. Options REREAD LEAVE REWIND DISP 2 . I f yo u omit t he option, the following positioning occurs: If TYPE=T is coded, LEAVE is assumed (BSAM only). If TYPE=T is not coded, DISP Is assumed (BSAM only). 3 . Yo u can code CLOSE w i t h[...]

Notes: 1 . T he codes are as follows: ┌──────┬────────────────────────────────────────────────────────────┐ │ VSE │ MVS (BSAM only) │ ├──────┼────────────────[...]

Notes: 1. VSE : Th e address is that of a four-byte storage location containing the required record identification in the same form as it is obtained from the NOTE macro. 2. MVS: Th e blockaddrcss is the address o f a fullword on a fullword boundary containing the required record identification in the same form as it is obtained from the NOTE macro[...]

FEOV Macro The basic functions of the VSE and MVS FEOV macros are the same. In MVS, volume positioning can be specified by the option operand; if no option is coded, the positioning specified in the OPEN macro is used. The MVS FEOV macro is valid for BSAM and QSAM. GET / PUT Macros The functions of the VSE and MVS GET/PUT macros are the same. Figur[...]

VSE DTFMT MVS DCB DSORG=PS BLKSIZE = nnnnn BLKSIZE = nnnn DEVADDR = SYSxxx N/A EOFADDR = xxxxxxxx EODAD = xxxxxxxx FILABL = xxxx LABEL = (in DD statement) IOAREA1 = xxxxxxxx BUFNO = 1 or IOAREA1 = xxxxxxxx BUFNO = 2 or more IOAREA2 = xxxxxxxx ASCII = YES OPTCD = Q BUFOFF = nn BUFOFF = (n) ERREXT = YES SYNAD = xxxxxxxx ERROPT = IGNORE EROPT = ACC SK[...]

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 RECFORM=FIXBLK,BLKSIZE=2000, C RECSIZE=100,REWIND=NORWD MTMOD RECFORM=FIXBLK OPEN (TAPE,(OUTPUT,LEAVE)) LA 5,RECORD1 MVS PUT TAPE,(5) . CLOSE (TAPE,(LEAVE)) RECORD1 DS CL100 TAPE DCB DDNAME=TAPEDD,D[...]

VSE DTFDI MVS DCB DSORG=PS DEVADDR = SYSxxx DDname (in DD statement) IOAREA1 = xxxxxxxx BUFNO = 1 or IOAREA! = xxxxxxxx BUFNO = 2 or more IOAREA2 = xxxxxxxx EOFADDR = xxxxxxxx EODAD = xxxxxxxx ERROPT = xxxxxxxx SYNAD = xxxxxxxx ERROPI = IGNORE EROPI = ACC SKIP SKP ABE MACRF =(G...) = (p...) RECFM = FA = FM BLKSIZE = nnnn IOREG = (r) MACRF = (..L..)[...]

Options Option 1 Option 2 QSAM INPUT ,REREAD OUTPUT ,LEAVE UPDAT ,DISP EXTEND INPUT EXTEND OUTPUT ,REREAD BSAM INOUT ,DISP UPDAT ,LEAVE OUTIN OUTINX Note: Any number of dcbaddresses and associated options may be specified in the OPEN macro instruction. CLOSE Macro 1. Options REREAD LEAVE FREE DISP 2 . I f yo u omit t he option, the following positi[...]

CNTRL Macro There is no equivalent for the VSE CNTRL macro. The MVS CNTRL does not support DASD devices. RELSE Macro The VSE and MVS functions of this macro are the same. RELSE causes the remaining records in a buffer to be ignored. TRUNC Macro The VSE and MVS functions of this macro are the same. TRUNC causes the next logical record to be written [...]

ACC Specifies that the problem program accepts the block causing the error. This action can be specified when a data set is opened for INPUT, RDBACK, UPDAT, or OUTPUT (OUTPUT applies to printer data sets only). SKP Specifies that the block that caused the error is skipped. Specifying SKP also causes the buffer associated with the data block to be r[...]

Notes: 1 . T h e decbaddress must be the same as used in the READ o r WRITE macro (decbname). 2 . I f the I/ O operation did not complete successfully, th e error analysis routine (SYNAD) is given control if you have provided one. 3 . Th e following conditions ar e also handled: • When the system is reading, volume switching is automatic. The end[...]

N OT E Macro The MVS NOTE macro is valid only for BSAM and BPAM. NOTE returns the following information: VSE-register 0: 00nn VSE-register 1: CCHR MVS-register 1: TTR0 where nn = Unused space remaining on the track following the end of the identified record. C = Cylinder number. H = Track number. T = Relative track number. R = Block number of that [...]

VSE DTFSD MVS DCB DSORG=PS BLKSIZE = nnnn BLKSIZE = nnnn EOFADDR = xxxxxxxx EODAD = xxxxxxxx DELETFL = NO DISP = (in DD statement) DEVADDR = SYSxxx N/A DEVICE = nnnn UNIT = (in DD statement) ERROPT = IGNORE EROPT = ACC SKIP SKP (QSAM only) (in DD stmt) ABE ERROPT = xxxxxxxxx SYNAD = xxxxxxxx ERREXT = YES SYNAD = xxxxxxxx FEOVD = YES Not required HO[...]

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 SDMODW OPEN SAMFILE,(OUTPUT)) . WRITE DECB,SF,SAMFILE,DATA MVS CHECK DECB . CLOSE SAMFILE SAMFILE DCB DDNAME=SAMDD,RECFM=F,DSORG=PS, C BLKSIZE=80,MACRF=(W) Figure 39. Seq[...]

VSE DTFDA MVS DCB DSORG=DA BLKSIZE = nnnn BLKSIZE = nnnn DEVICE = nnnn UNIT = (in DD statement) ERRBYTE = xxxxxxxx (See description of SYNAD routine) IOAREA1 = xxxxxxxx Area address (READ/WRITE macro) SEEKADR = xxxxxxxx Not required (READ/WRITE macro) TYPEFLE = xxxxxx OPEN macro option AFTER = YES MACRF = (..WA..) DEVADDR = SYSnnn UNIT = (in DD sta[...]

ERROR VSE MVS Byte Bit Byte Bit Wrong-length record 0 1 2 1 Nondata transfer error 0 2 2 6 Space not found on track 0 4 2 2 Reference outside extents of data set or file 0 7 3 3 Data check in count area 1 0 2 4 Track overrun 1 1 ** ** End-of-cylinder 1 2 ** ** Data check when reading key or data 1 3 2 4 Record not found 1 4 2 B End-of-file 1 5 2 5 [...]

WRITE Macro Notes: 1. TYPE = D A , DAF, DI, DIF, DIX, DK , DKF, o r DKX. 2. ′ S ′ - system supplies the operand if you specify ′ S ′. 3 . I f the key is not written or used as a search argument, zero is specified instead of keyaddress. CNTRL Macro There is no equivalent in MVS BDAM to the VSE CNTRL macro. The MVS CNTRL macro does not suppor[...]

13.2.6.12 Track and Record Addressing Track Addressing In VSE and MVS, you can make track references by using either the actual or relative addressing technique. The track reference field for actual addressing in VSE and MVS is of the form MBBCCHHR. The contents of the M byte is different in VSE and MVS. In VSE, M represents volume number, starting[...]

Record Addressing by KEY Supply the key as follows: Keyaddress points to a field containing the key of the record for which you are searching. Blockaddress points to a field containing sufficient information to identify the track on which the search is to begin. Reference Methods The following paragraphs describe record reference by ID and record r[...]

Figure 42. Record Reference by I D in V S E and MVS Reference Method VSE MVS Relative Track Addressing Assumed if DSKXTNT is specified. RELTYPE=HEX (the default) requires the hexadecimal form TTTR. RELTYPE=DEC requires the zoned decimal for TTTTTTTTRR. In both cases, the R byte(s) must contain the actual record number of the record on the track. As[...]

Figure 43. Record Reference by K E Y i n V S E and MVS Reference Method: VSE MVS Relative Track Addressing Assumed if DSKXTNT is specified. RELTYPE=HEX (the default) requires the hexadecimal form TTTR. RELTYPE=DEC requires the zoned decimal form TTITTTTTRR. RR must be 00. Assumed if OPTCD does not contain A. The field specified by blockaddress must[...]

OPEN (DAMFILE,(OUTPUT)) . . WRITE DECBADD,DI,DAMFILE,DATA, ′ S ′, KEY,BLOCKADDRESS CHECK DECBADD . . DAMFILE DCB ..MACRF=(WICS),DSORG=DA,OPTCD=R... . . Figure 45. Adding to a D AM File under M VS Loading a DAM File (Fixed-Length Records with keys) Figure 46 and Figure 47 on page 320 illustrate an example of sequentially loading a DAM file consi[...]

OPEN (DAMFILE,(OUTPUT),TAPE,(INPUT)) GET GET TAPE . WRITE DECB1,SF,DAMFILE,(10) CHECK DECB1 . WRITE DECB2,SD,DAMFILE,DUMMYREC CHECK DECB2 . TAPE DCB ....... . DAMFILE DCB DDNAME=OSDAMDD,DSORG=PS, C MACRF=(WL),SYNAD=DATRTST, C RECFM=F,KEYLEN=3,BLKSIZE=47 Note: DSORG=PS must be specified in the DCB. However, DSORG=DA must be specified in the DD state[...]

Notes . OPEN (R0FILE,(OUTPUT),TAPE) WRITER0 WRITE DECBR0,SZ,R0FILE STC 15,RC (1) CHECK DECBR0 CLI RC,X ′00′ BE WRITER0 (2) OPENDAM OPEN (DAMFILE,(OUTPUT)) CLI WC,X ′10′ (3,8) BE WRITE GET GET TAPE,WORK PACK PKEY(2),KEY CVB 9,CVBKEY SR 8,8 (4) D 8,=F ′37′ LTR 8,8 BNZ *+10 BCTR 9,0 IC 8,=C ′37′ STH 9,TT STC 8,R WRITE WRITE DECBLOAD,DA[...]

Notes RC DS CL1 WC DC CLI ′0′ COUNT DC H ′0′ THREE DC H ′3′ * R0FILE DCB DDNAME=R0DD, (9) C DSORG=PS, C MACRF=(WL), C SYNAD=OSDAERR1, C BLKSIZE=47, C KEYLEN=3, C RECFM=U * DAMFILE DCB DDNAME=DAMDD, (9) C DSORG=DA, C MACRF=(WAC), C OPTCD=F, C SYNAD=OSDAERR2 * TAPE DCB DDNAME=TAPEDD, C DSORG=PS, C MACRF=(GM), C EODAD=EOF * //GO.TAPEDD DD [...]

4. Since 3 7 records (b l oc ks ) will f i t on one 3340 track, the three-byte key (ranging from 001-999) is divided by 37 to get the relative track number and the remainder will be the number of the record on this track. If a remainder of O is computed, this record will still fit on the previous track; therefore TT = n, R = 0 will be reset to TT =[...]

To create a file using this method under MVS, you would normally initialize each track by writing a capacity record (R0) and erasing the 2.sp of the track. I n VSE, you would do this by using the WRITE RZERO macro; in MVS you use the WRITE SZ macro. However, in MVS, you need not update the track address because this is done automatically by the WRI[...]

When updating records, it is convenient to use the list and execute forms of READ/WRITE macros rather than the standard forms and to request dynamic buffering. To update a direct access file that was created sequentially, as in Figure 51 on page 325, use coding similar to that of the example in Figure 4 4 o n page 318, which uses the list and execu[...]

In MVS, to make a request for feedback, insert the letter F in the type code of a READ/WRITE macro (DIF, DAF and so on). The format of the blockaddress field after feedback, however, is determined by the OPTCD parameter. If the OPTCD parameter does not contain an F, feedback will be in the form of MBBCCHHR. If you code an F in the OPTCD parameter, [...]

13.2.6.14 PIOCS EXCP is often used in VSE in association with card files (for example, SYSIPT), print files (for example, SYSLST) or the operator console (for example, SYSLOG). In MVS, EXCP can not be used for spool files or to dialog with the operator. VSE programs that use EXCP should be converted to use standard access method such as QSAM or the[...]

DTFPH Macro Figure 54 shows the correspondence between the operands of the DTFPH macro and their MVS equivalents: Figure 54. Relationship between DTFPH Macro and MVS equivalents DTFPH OPERAND M VS EQUIVALENT TYPEFLE ASCII CCWADDR DEVICE DEVADDR LABADRR HDRINFO MOUNTED XTNTXIT OPEN macro OPTCD=Q Channel program address field of IOB UNIT parameter of[...]

Chapter 1 4 . RP G II 14.1 Migration from VSE to OS/390 The aim has been to make it easy to convert programs running under VSE to run under OS/390, with the minimum of changes to the source code. In fact, the source programs will run unmodified, except for the following: • The command level interfaces with CICS/VS and DL/I VSE are not supported b[...]

• With the device type PRINTER or with a blank entry for device type and symbolic device SYSLST (DOS/VS RPG II only) − LRECL is the record length specified in the file description specification plus 1 (for the machine control character) − The first position of each record contains the machine control character. The RECFM in the DCB is the fil[...]

Direct access method files are processed with BDAM. VSAM files are handled in the same way as under VSE. 14.1.7 Calling COBOL Subprograms In OS/390 RPG II, a CALL statement for a COBOL subprogram must not be preceded by a CALL ′ ILBDSET0 ′. 14.1.8 Calling PL/I Subprograms It is not possible to call PL/I subprograms from an OS/390 RPG II program[...]

332 VSE to OS/390 Migration Workbook[...]

Chapter 1 5 . PL/I The PL/I language compiler implemented on VSE is the DOS PL/I Optimizing Compiler (5736-PL3). In MVS, the PL/I language is implemented by the OS PL/I Optimizing Compiler Version 1 (5734-PL3), and OS PL/I Version 2 Optimizing Compiler (5668-910). As the OS PL/I Version 2 Optimizing Compiler implements more of the PL/I language tha[...]

15.1.2 Extended Precision Available with the MVS version of the PL/I compiler, extended precision floating point allows working with variables of two double-words. This extended precision is requested by specifying a precision greater than 16 for decimal float variables and 53 for binary float variables. DOS PL/I does not support extended precision[...]

15.1.6 Parameters Passed to a Main Program It is possible to pass parameters to a PL/I program having the option MAIN by declaring the entry point as follows: P:PROCEDURE(PARAM) OPTIONS(MAIN); DCL PARAM CHAR(100) VARYING; When control is passed to the program, the character string PARAM will contain the parameter passed from the PARM field of the E[...]

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 LIMSCONV An option of DOS PL/I to generate strong external references to PL/I conversion library modules only for those conversions deemed ″ reasonable ″ for the data types of variables that appear in GET DATA and GE[...]

15.2.2.5 SMESSAGE or LMESSAGE This option requests the compiler to supply messages in short or long format. This is particularly useful for interactive users using only slow terminals (printers). 15.2.2.6 IMPRECISE This is used for 360/91 and 360/195 only. 15.2.2.7 INTERRUPT This option requests that control be given to an ATTENTION type of ON- UNI[...]

15.2.3.4 SPIE STAE As user-program execution options they authorize PL/I to issue SPIE and STAE macros to intercept program checks and abends. It is possible with NOSPIE and NOSTAE to prevent this and in this case it is no longer certain that the management of errors will be handled by system ABEND or by an interruption handling program. This, ther[...]

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. The error severity is 8 and gives correct execution. In MVS PL/I the name of the DD statement (DDname) is the name of the file as specified in the DCL. If some other name must be used, it can be supplied via the TITLE option on th[...]

15.4.1.10 NOTAPEMK NOLABEL These are specified in the JCL in the LABEL parameter of the DD statement. 15.4.2 Supported but to be Avoided In OS most of the environment parameters can be specified in the DCB. At OPEN, MVS merges the information from the program, from the label if the file exists already, and from the DCB parameters in the DD statemen[...]

15.5.2.1 SORT FIELDS SORT data: a character string containing an image of the SORT statement. This card image must begin and end with a blank. It will contain the sort criteria and the description of these criteria. 15.5.2.2 RECORD RECORD information: A character string containing a card image of the RECORD control statement. It too must begin and [...]

15.5.2.9 SORT TECHNIQUES The user can specify a particular sort technique: PEER Peerage sort BALN Balanced CRCX Criss-cross OSCL Oscillating POLY Polyphase The sort call is, therefore, little different to that of DOS PL/I. In all cases, reading the Programmers ′ Guide for the appropriate version of the sort is recommended. 15.6 Checkpoint-Restart[...]

15.6.3 PLICANC Another possibility offered in the MVS PL/I optimizer is the ability to annul a request for an automatic restart. The function PLICANC provides this service. In checkpoint-restart MVS PL/I offers more facilities than DOS PL/I. The conversion of PL/I programs poses few syntax problems. On the other hand, to take advantage of automatic[...]

15.7.3 Options Specific to MVS The options A, E and 0 are used only in a multitasking environment: A Dump all tasks O Dump only the task requesting the dump E Use of an exit 15.7.4 Compatibility Parameters unsupported by the PL/I dump routines are ignored if they are used when calling dump facilities. 15.8 Return Codes in PL/I 15.8.1 Setting Return[...]

15.9.2 Automatic Restart An automatic restart in the case of an ABEND can only take place if an ABEND is actually detected; it must therefore be forced. This is the role of PLIREST. 15.10 Overlay Structures Overlay structures defined in DOS PL/I optimizer programs can remain valid in MVS PL/I optimizer programs. However, the CALL PLIOVLY statements[...]

large enough ISA to reduce subsequent GETMAINs and FREEMAINs to zero (or some very small number). This is one of the most important things a user can do to improve the performance of a PL/I program. 15.12 PL/I and CICS 15.12.1 File Support The only PL/I file supported by PL/I under CICS is SYSPRINT, and its usage must be limited. The functions LINE[...]

15.12.7 PL/I Return from ON-units and CICS Transaction Backout If a CICS transaction ABEND begins but is intercepted in a PL/I ON-unit, and the program takes ″ normal return ″ from the ERROR ON-unit (that is, quits) PL/I will reissue the CICS ABEND. If ERROR was raised without a CICS ABEND and the program takes ″ normal return ″ from the ER[...]

348 VSE to OS/390 Migration Workbook[...]

Chapter 1 6 . FORTRAN 16.1 V S FORTRAN in OS/390 VS FORTRAN is the compiler and library to use on OS/390. VS FORTRAN expands greatly on what you can do with FORTRAN in accessing system services and/or hardware features. If you have used VS FORTRAN on VSE, you may be aware of the extensions that VS FORTRAN provides over DOS FORTRAN, such as executio[...]

350 VSE to OS/390 Migration Workbook[...]

Chapter 17. Language Environment (LE) 17.1 Introduction This chapter introduces OS/390 Language Environment (program number 5645-001). OS/390 Language Environment is the language run-time environment distributed with OS/390. Various strategies for migrating your applications to the Language Environment run-time are considered. These strategies depe[...]

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. These differences do not affect the running of your migrated LE/VSE applications in an OS/390 Language Environment but you may want to take advantage of the extra facilities offered by th[...]

17.2.2 Useful Publications Table 35 lists some publications that you may find useful when planning your conversion. Table 35. Useful Publications Publication Title Form Number OS/390 Language Environment Migration Guide SC28-1944 OS/390 Language Environment Programming Reference SC28-1940 OS/390 Language Environment Programming Guide SC28-1939 OS/3[...]

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 can (subject to certain restrictions) be migrated to OS/390 without change. You can transfer the compiled object code from VSE to OS/390, link-edit it with OS/390 Language Environment and run it there. This is discu[...]

Table 36. REPORT a n d I SASIZE Options, C/370 and DOS PL/I REPORT option, C/370 and DOS PL/I The information supplied by the REPORT option in C/370 and DOS PL/I is supplied in LE/VSE by the RPTSTG option. The RPTOPTS option may also be of use in determining storage use. ISASIZE option, DO S PL/I In LE/VSE 1.4 the ISASIZE option maps to the STACK o[...]

Table 38 on page 356 lists some migration considerations you should be aware of when migrating from VS COBOL II. Table 38. VS COBOL II Migration Considerations Migration Consideration Comments Abends In VS COBOL II, a severe unhandled error condition always resulted in an abend. With OS/390 Language Environment, you use the ABTERMENC run-time optio[...]

Table 40. DOS PL/I Migration Considerations Migration Consideration Comments Dumps The output produced by PLIDUMP is different when running under OS/390 Language Environment. Condition Handling In general, PL/I condition handling continues to function in the same way when running under OS/390 Language Environment; however, you should consider the f[...]

17.4.6 V S FORTRAN If your VSE applications are currently written in VS FORTRAN, you must convert them to another version of the FORTRAN compiler before you can run them under OS/390. There is currently no LE/VSE-conforming FORTRAN compiler, so you must convert your VS FORTRAN applications to the OS/390 version of VS FORTRAN. You should read the La[...]

Table 41 (Page 2 of 2). ILC Migration Considerations To Migrate: You Need To: A phase containing one or more VS COBOL II programs, with calls to or from C/370 1. Upgrade th e C/370 source code, and compile with OS/390 C/C++. 2. Transfer th e VS COBOL II object code to OS/390. 3. Link-edit th e load module with OS/390 Language Environment. 17.4.8 Mi[...]

ABPERC In LE/VSE you can specify the abend code to the option ABPERC in one of three formats. These formats are: • S hh • I hh • U dddd In OS/390 Language Environment you can only specify S hh or U dddd . I hh is not allowed, and if you specify it you will receive an error message similar to: CEE3616I The string ′ I12 ′ was not a valid su[...]

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: LE/VSE 1.1 NOTEST(NONE,*,NOPROMPT,*) LE/VSE 1.4 NOTEST(ALL,*,NOPROMPT, ′′) OS/390 Language Environment NOTEST(ALL,*,NOPROMPT,INSPPREF) You should read the OS/390 Language Environment Programming Reference for information ab[...]

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 usage in OS/390 Language Environment is sometimes different. They were not available in LE/VSE 1.1. ARGPARSE This option only applies to C and can only be specified with the C #pragma runopts directive. #pragma runopts is not a[...]

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 Environment Migration Guide . The recommended settings for options for LE/VSE 1.4 are described in the LE/VSE Run-Time Migration Guide Release 4 . For LE/VSE 1.1, where IBM made recommendations for the [...]

Table 43 (Page 2 of 2). Option Recommendations Differing between LE/VSE 1.4 and OS/390 Language Environment Language Option Recommendation PL/I ABTERMENC RETCODE DEPTHCONDLMT 0 STACK 128K,128K,BELOW,KEEP TERMTHDACT TRACE 17.5.2 User Exits and Abnormal Termination Exits This section discusses migration considerations for user and abnormal terminatio[...]

In OS/390 Language Environment a sample job, CEEWHLLX, is provided that contains an SMP/E USERMOD to replace the IBM-supplied HLL user exit with your HLL user exit. 17.5.2.3 Abnormal Termination Exits Language Environment provides the ability to invoke an abnormal termination exit before it terminates a thread due to an unhandled condition of sever[...]

CEE5ABD CEE5GRN CEE5MDS CEE5SPM CEE5CIB CEE5GRO CEE5MTS CEE5SRC CEE5CTY CEE5LNG CEE5PRM CEE5SRP CEE5DMP CEE5MCS CEE5RPH CEE5USR CEE5GRC Figure 56. Callable Services in LE/VSE 1.4 with Differing Names in OS/390 Language Environment Note: Three further callable services are available in LE/VSE releases later than 1.4, and in LE/VSE 1.4 via APAR PQ085[...]

The recommended settings for run-time options for CICS, are the same for OS/390 Language Environment and for LE/VSE, with the following exceptions, listed in Table 44 on page 3 6 7 . Table 44. Option Recommendations for CICS Differing between LE/VSE and OS/390 Language Environment Language Option Recommendation COBOL LIBSTACK 1K,1K,FREE TERMTHDACT [...]

368 VSE to OS/390 Migration Workbook[...]

Chapter 18. Procedure Language REXX The REstructured eXtended eXecutor language, or REXX language, is a versatile, easy to use structured procedure language that is part of: • VM/ESA • VSE/ESA • TSO/E REXX was designed as a replacement for the EXEC and EXEC2 languages that provided a way to bundle Conversational Monitor System (CMS) commands [...]

18.4 Environments The system under which REXX procedures run is assumed to include at least one environment for processing commands. An environment is selected by default on entry to a REXX procedure. You can change the environment by using the ADDRESS instruction: address cms /* VM/ESA CMS environment */ address POWER /* VSE/ESA POWER host command[...]

18.4.3 TSO/E Environment TSO/E provides among others the following host command environments: • TSO allows you to invoke TSO/E commands and services. • CONSOLE allows you to invoke MVS system and subsystem commands during an extended MCS console session. • ISPEXEC and ISAREDIT allows you to invoke ISPF commands and services, and ISPF edit mac[...]

18.5.1 REXX and SAA Issuing commands to the surrounding environment is an integral part of REXX. REXX is the only procedure language supported by the SAA to help provide cross-system consistency. Procedures written in REXX according to the SAA specifications can be transported to other SAA environments. For example, a REXX exec in CMS can also run [...]

Part 4. Converting VSE Utilities to OS/390 Utilities In addition to this part of the book on converting utilities, also see Chapter 2 9 , “Orientation for Utilities” on page 455 which discusses more OS/390 Utilities that you can use.  Copyright IBM Corp. 1998 373[...]

374 VSE to OS/390 Migration Workbook[...]

Chapter 1 9 . SORT This chapter addresses considerations for migrating to the OS/390 Sort product, DFSORT (5740-SM1) from the VSE Sort products: • DOS/VS SORT/MERGE V2 (5746-SM2), referred to as Sort/Merge • DFSORT/VSE V3 (5746-SM3), referred to as DFSORT/VSE DFSORT/VSE is based on and replaces Sort/Merge. It offers additional features not avai[...]

//MYJOB JOB ... //SORTIT EXEC PGM=SORT //SYSOUT DD SYSOUT=* //SORTIN DD DSN=... //SORTOUT DD DSN=... //SYSIN DD * SORT FIELDS=(5,4,CH,A) /* The JCL statements you will commonly need when migrating are: JOB: Must be the first statement for a job. EXEC: Must be the first statement for a step. Specifies the program to be executed. For DFSORT steps, us[...]

19.2 Control Statements DFSORT was designed to be functionally compatible with Sort/Merge at the control statement level, and for the most part, the control statement syntax of the two products is compatible. However, there are differences in some of the control statements that you will need to address. Here are the actions, if any, you should cons[...]

• ERASE: Can be used with no changes. DFSORT ignores ERASE. Use a security product, such as RACF, to erase the work data sets. • NOERASE: Can be used with no changes. DFSORT ignores NOERASE. DFSORT does not erase work data sets. • FILNM: Must be removed. DFSORT terminates if this operand is specified. Use DFSORT ′ s SORTIN, SORTOUT or SORTD[...]

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. All of the migration considerations discussed previously for Sort/Merge apply to DFSORT/VSE as well. Migration considerations for additional features of DFSORT/VSE are discussed below. 19.3.1[...]

• p,m,Y2x: Must be removed. DFSORT terminates if this operand is specified. p,m,Y2x can be specified in the OUTREC operand of DFSORT ′ s OUTFIL statement. • p,m,PZ: Must be removed. DFSORT terminates if this operand is specified. p,m,PZ can be replaced by p,m,PD0,M11 in the OUTREC operand of DFSORT ′ s OUTFIL statement. • p,m,PSI: Must be[...]

Chapter 2 0 . DITTO Data Interfile Transfer, Testing, and Operations Utility (DITTO) is IBM ′ s best known storage media and data maintenance utility program for the OS/390, MVS, VSE, and VM environments. DITTO is a key resource for data processing professionals due to many versatile functions working with tapes, disks, VTOCs and catalogs, VSAM d[...]

double asterisk (**) represents any number of characters in any number of qualifiers. Under VSE and CMS, an implicit rewind was previously performed by each function that works with labeled tapes. Labeled tape functions could only work with the first file on a tape. The implicit rewind is no longer performed. This lets you work with multifile stand[...]

Function Description Replacement SD, SDD Split-Cylinder Disk Dump - SDU SAM to Diskette - SIS SAM File to ISAM File - SP, SPD Split-Cylinder Disk Print - SRS Split-Cylinder Disk Record Scan - TDD Tape Dump Deblocked TP TDU Tape to Diskette - TDV Tape Dump Variable TP TIS Tape to ISAM File - TPD Tape Print Deblocked TP TPV Tape Print Variable TP VDU[...]

20.4 DITTO Function Code Synonyms The following table lists supported synonyms for DITTO function codes. Function Synonym(s) Description BS BQ, BSQ Create Sequential Data BT BTP Create Tape File BV BVS Create VSAM File CS CQ, CSQ Card to Sequential Data CV CVS Card to VSAM DUMP DUM Dump CMS File to Tape FP FPR CMS File Print FT FTP CMS File to Tape[...]

20.6 Batch Keywords that are Not Recommended The following table lists obsolete keywords from previous releases of DITTO that are still recognized by DITTO/ESA in batch mode. It is recommended that you use the indicated replacement, if any. Function(s) Keyword Description Replacement BS, BT, CS, CT, FT, SS, ST, TFT, TS, TTR, VS, VT BLKFACTOR= Outpu[...]

386 VSE to OS/390 Migration Workbook[...]

Chapter 2 1 . VSAM Backup/Restore 21.1 VSAM Backup/Restore The following describes the methods and utilities used in OS/390 as compared to VSE VSAM Backup/Restore procedures. 21.1.1 OS/390 VSAM Backup/Restore There are several tools that can be used in an OS/390 system to back up and restore VSAM files. Considerations for which tool you may want to[...]

Operations: 1. Handle several VSE/VSAM files w it h a single command, either with a generic name or as files of one catalog. 2. Restore VSE/VSAM files to locations, volumes, and device types that a re different from those where the files were before. 3. Exclude files from a collective backup or restore operation. 4. Tune t he performance of VSE/VSA[...]

Chapter 2 2 . Librarian Both VSE and OS/390 have facilities to help you define, organize, and manage libraries of system data. In VSE these system facilities are called the Librarian . In OS/390, the equivalent function is provided by Partitioned Data Sets (PDS) and the newer Partitioned Data Set-Extended (PDSE), and the group of utilities used for[...]

functional enhancements of the VSE Librarian. The Librarian functions can be invoked through a console or through job streams (JCL). In OS/390, each of the different utilities used to create and maintain PDS (or PDSE) data sets and their members has a different set of commands and somewhat different syntactical requirements. Combined with OS/390 JC[...]

22.1.2 OS/390 Library Management The Software Configuration Library Manager (SCLM), a component of ISPF, introduces an object-oriented approach to library management and software development. The objects SCLM can control are members in partitioned data sets. SCLM keeps track of objects by means of multiple distinct VSAM files containing the account[...]

392 VSE to OS/390 Migration Workbook[...]

Chapter 23. LISTLOG/PRINTLOG - Printing Log Streams Both VSE and OS/390 provide facilities to capture system log data in a hardcopy file, and means to display, print and archive it. There are two utilities in VSE that help you print copies of your system hard-copy file and information about jobs that run in your system: PRINTLOG and LISTLOG. In OS/[...]

23.3.1 SYSLOG The system log (SYSLOG) is a data set residing in the primary job entry subsystem ′ s spool space. It can be used by application and system programmers to record communications about problem programs and system functions. The operator can use the LOG command to add an entry to the system log. SYSLOG is queued for printing when the n[...]

23.5 JES2 System Data Sets - Job Log and System Messages The job ′ s hardcopy log and any system messages related to the job are managed by JES2 as the ″ System Messages ″ for each job. Based on installation specifications and overridden on the job ′ s JCL, they can also be saved or not based on the normal or abnormal termination of the job[...]

396 VSE to OS/390 Migration Workbook[...]

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 VSE/Fast Copy (Online and Stand-Alone) In VSE/ESA Version 1, VSE/Fast Copy runs stand-alone only. The on-line functions of VSE/Fast Copy have been incorporated into the program ″ VSE/Fast Copy Data Set (V[...]

24.2 DFSMSdss - OS/390 Component DFSMSdss has four functions to help you manage your DASD space: • COMPRESS Compresses your partitioned data sets by taking unused space and consolidating it at the end of the data set. To make the unused space available for other data sets, you must use the RELEASE command. This does not apply to PDSEs. • RELEAS[...]

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

400 VSE to OS/390 Migration Workbook[...]

Chapter 25. Prepare the Migration Environment 25.1 Introduction Setting up the OS/390 environment, similar to setting up the VSE environment, involves installing the prerequisite hardware and software, and tailoring the system for your environment. As an example, we can describe it with the following steps: 1. Install a nd configure the required ha[...]

25.2 Install and Configure Required Hardware VSE and OS/390 operating systems both use the same basic S/390 hardware platform, although you will find that OS/390 may require more processor power, storage and DASD resources. On the other hand, OS/390 also provides more function, supports more devices, and is easier to manage as your applications and[...]

A beginning rule of thumb shows 12 volumes of 3390-3 (or equivalent) DASD, allocated as follows: (Your mileage will vary!) These numbers are very dependent on the installation, and will increase dramatically at the end of a ″ mass migration ″ in order to duplicate user data files. Table 45. OS/390 DASD Layout Volume Use Number System Libraries [...]

OS/390 through cross-domain resource definitions. They are also useful for data transfer via NetView FTP or NJE. OSA (Open System Adapters) are often the most economical solution. You will want access to other devices in your installation. They can be switchable or connected via a common local area network (LAN). See the OS/390 MVS Recovery and Rec[...]

25.2.5.4 Data Transfer and NJE You will want to set up an NJE connection between the two systems for remote job submission and for routing print files or bulk data between the two systems. Use the same communication controllers, real Channel to Channel adapter (CTC) controlled by VTAM or virtual CTCs. You have several choices with ESCON CTCs, virtu[...]

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 IBM. You can use this to tailor OS/390 to your environment (such as DASD layout, migration of MVSCP/IOCP to IODF, and naming conventions) based on information provided to IBM. With this offering, selecte[...]

25.3.2.2 CBPDO Custom-Built Product Delivery Option is a software delivery package consisting of uninstalled products without integrated service. You must use SMP/E to install the individual OS/390 elements and features, and their service, before you can IPL. This method is not recommended for the new OS/390 installation. 25.4 Set Up Standards, Pro[...]

Related Redbooks Here is a list of DFSMS ″ Fast Implementation Techniques ″ ( FIT) Redbooks: • DFSMS FIT: Fast Implementation Techniques Process Guide , SG24-4478 • Get DFSMS FIT: Fast Implementation Techniques , SG24-2568 • DFSMS FIT Forms and Foils , SG24-2570 • DFSMS FIT: Fast Implementation Techniques Installation Examples , SG24-25[...]

Other MVS Names There are many other objects which require naming in OS/390. Here is just a sample: • Users (TSO, online, batch, operators) • Job names • Job step names • JCL procedure names and proclibs • Application program names • WLM service classes • WLM resource environments 25.4.1.3 JCL Standards You should set up JCL (job cont[...]

25.4.2.1 Enforcing Installation Standards You will continue to refine the standards developed above, and should use RACF to protect critical resources. You can also use installation exits to enforce standards not controlled by RACF, but keep in mind that it is often easier to enforce them through other procedures. 25.4.2.2 Implementing System Secur[...]

25.4.2.5 Setting Up Critical Operations Procedures You should set up, test, and document procedures that are critical to the smooth operation of your system. Here is a sampling: • System IPL, JES2 warm-start • JES2 checkpoint reconfiguration • JES2 ABEND and hot-start • System shutdown • VTAM startup and shutdown • VTAM vary node active[...]

25.4.3 Documentation You should already have the following planning publications which are available as part of the OS/390 Installation Planning Kit , GK2T-6710: • OS/390 Planning for Installation , GC28-1726 • OS/390 Introduction and Release Guide , GC28-1725 • OS/390 Information Roadmap , GC28-1727 The Information Roadmap will then list the[...]

25.5 Customize Your New OS/390 System Before you start using your new OS/390 system, you must complete the installation and tailoring process by customizing the system for your use. Depending on what method you used to install the software, some of the items listed below may already have been completed for you or you may have contracted for some ad[...]

IBM ′ s comprehensive testing does not replace the need for this testing in your own environment. Here are some sample steps copied from the OS/390 Checklist: 1. Initialize th e system (IPL) 2. Initialize JES2 3. Lo g o n t o TSO/E 4. Ru n the installation verification programs (IVPs) 5. Submit a job a nd check its output 6. Sign o n t o a termin[...]

25.5.1.4 NetView FTP Access You can also use the same VTAM connections to send bulk data between the two systems with NetView FTP. See NetView FTP V2 MVS Installation, Operation, and Administration , SH12-5657. 25.5.1.5 Providing NJE Connection to the OS/390 System You can connect VSE/POWER and OS/390 JES2 systems together via NJE to route jobs and[...]

25.5.2.3 Tailoring Other Components Other features of OS/390, such as JES2 are described in other chapters of this book. The elements of OS/390 are listed below and each has its own set of books on installation and customization. 25.5.3 Other OS/390 Elements OS/390 is made up of base elements and optional features. Here is a list of the pieces you [...]

25.5.3.3 Independent Software Vendor Products If you chose to use ISV (non-IBM) products, you should recognize the additional implementation, customization, maintenance and tuning requirements that accompany them. Chapter 25. Prepare the Migration Environment 417[...]

418 VSE to OS/390 Migration Workbook[...]

Chapter 2 6 . Test Environments This chapter describes the different needs for test systems during and after the migration to OS/390. There are many valid test configurations which vary according to your installation ′ s testing and maintenance philosophies, as well as your environment. Here are some of the discussion points: • VM, LPAR, or sta[...]

Application Development & Test System A system that is expected to stay up without disruption at least during ″ normal working hours ″. Understand that any outages to this system will affect your applications conversion and testing activities. This logical image may eventually become your production OS/390 system when you cut-over. Maintena[...]

3 Final System Test on OS/390 Just before you migrate to OS/390, you should run all your important applications in parallel, using the same environment as above. Compare the results of both systems to make certain there are as few surprises as possible. 4 Final Production Cut-Over to OS/390 ( ″ D ″ Day?) When you finally migrate your production[...]

evaluate each of the alternatives mentioned, but that would be beyond the scope of this book, and not necessarily relevant to the task at hand. Since this document is directed toward migration of VSE systems to OS/390 primarily on CMOS processors, we will not consider the choices of physically partitioning one or more processors, since this option [...]

Recent advances in the PR/SM LIC have solved some of the real storage management difficulties encountered in the past concerning assigning contiguous storage chunks to LPARs. In addition, ESCON Multi Image Facility (EMIF) channels have reduced the number of physical channels that must be installed to support multiple partitions by allowing for the [...]

central storage as if it were running natively on the processor. While storage is dedicated to a particular virtual machine, it is unavailable to other virtual machines, and also VM/ESA itself. VM/ESA however, provides much more than simply hypervisor, and virtualization functions. It also provides a full function, interactive, virtual machine oper[...]

installed. This support exists in VM/ESA Version 2 Release 3 on Multiprise 2000, 9672 G3, and G4 processors. If you are currently using VM/ESA as a hypervisor for your production VSE guest(s), as well as for test VSE guests, then proceeding with the migration process involves nothing more than defining additional guest virtual machines for OS/390 i[...]

VM/ESA distribute that communication capability among the guest images using virtual channel to channel devices. Similarly, any DASD that is shared between the VSE LPAR(s) and the VM/ESA LPAR can be defined through R/O minidisk definitions owned by a place holder virtual machine, and accessed through R/O links from the OS/390 guests. 26.3.3.3 The A[...]

new vendor package that runs under AIX. As guests of VM/ESA, all three can run efficiently while sharing one processor. • You have production applications that need to be reworked to comply with Year 2000. With VM/ESA ′ s Guest Support you can bring up a duplicate of your production system, set the clock to a date and time beyond the year 2000 [...]

VM/ESA and its customers exclusive technical advantages not available in any other operating system platform. Operations Management With PROP (VM/ESA ′ s PRogrammable OPerator) you can cut your console traffic substantially. This saves time and reduces errors. Recovery Management You can build guest virtual machines to simulate systems at your or[...]

distributed servers. VSE, OS/390, TPF, AIX and others are discovering the enormous value VM/ESA brings to the table. DB2 Guest Sharing With DB2, VM, VSE and OS/390 users can now share a DB2 database among several VSE and/or OS/390 guests. For most customers, consolidating several guest databases into one DB2 database reduces administrative work, si[...]

26.3.3.5 OS/390 Guest Considerations The considerations for defining OS/390 guests are no different from those associated with defining VSE guests. From the VM/ESA point of view, the actions taken to maximize the performance of a VSE guest, would be the same as those taken to maximize an OS/390 guest. For example, specifying resource goals is done [...]

26.5.1 OS/390 Maintenance Environment Early in the project a test SMP/E environment needs to be designed and built. This process involves ″ cloning ″ the OS/390 system libraries to provide a new target to apply OS/390 maintenance without compromising the OS/390 production environment. Since OS/390 was installed at the beginning of the project, [...]

26.6 Shared DASD vs. Cloned DASD The issue of whether to share DASD volumes and data sets between systems is decided on the basis of DASD space availability, need for multiple versions of a file, and the ability to manage updates between the two systems. 26.6.1 Shared DASD between OS/390 Test Systems (vs. Cloned DASD) The decision to share data set[...]

26.6.2 Shared DASD between VSE and OS/390 (vs. Cloned DASD) As mentioned in the previous section, it is risky to share DASD between VSE and OS/390 because there is no mechanism such as GRS to guarantee serialization between the two systems. If you decide to share, you must strictly control updates from the two systems, or be prepared to restore vol[...]

434 VSE to OS/390 Migration Workbook[...]

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

436 VSE to OS/390 Migration Workbook[...]

Chapter 27. Orienting ICCF Users to TSO/ISPF There are many facets of VSE/ICCF that are done differently in OS/390. TSO along with ISPF and SDSF provide functions that were previously done using VSE/ICCF. 27.1 TSO/ISPF and SDSF ISPF is a dialog manager and runs under TSO on OS/390. ISPF provides a powerful environment that can be used for both deve[...]

also build lists of personal data sets. Personal data set lists are a good way to group (by project, for example) those data sets that you use frequently. • Ability to run foreground and batch processors such as Assembler H, VS COBOL, VS FORTRAN, PL/I optimizing compiler, Binder/Linkage editor, C/370, REXX/370, and C/C++ for MVS/ESA. • Ability [...]

• finding specific character strings in the data, changing them to other character strings or to exclude the lines that contain strings, • setting HEX mode on to allow you to display data in hexadecimal format, • using language sensitive coloring, which highlights program constructs based on the programming language, improving readability, ?[...]

27.1.4 Creating and Executing ISPF Applications Since ISPF is a dialog manager, many other products have written dialogs, connect themselves through the main menu and run as additional ISPF functions. Products such as SDSF, IPCS, RACF, SMP/E and QMF all provide dialogs that run with ISPF. Users or system programmers can also write their own dialogs[...]

For more information see the OS/390 ISPF Software Configuration and Library Manager Developer ′ s Guide, OS/390 ISPF Software Configuration and Library Manager Project Manager ′ s Guide, and OS/390 ISPF Software Configuration and Library Manager Reference. 27.1.6 Tracking J o b s SDSF allows you to monitor any job in the system or sysplex. Valu[...]

442 VSE to OS/390 Migration Workbook[...]

Chapter 28. Orientation to OS/390 Console Operation 28.1 Introduction There are enough differences between VSE and OS/390 operations to warrant each operator and systems programmer attending a class on the subject. This chapter is intended only to provide the reader with an overview of OS/390 console operations on a single system. (Multi-system or [...]

• NetView Consoles • TSCF Consoles • Programmed Operator Subsystems This chapter will only deal with MCS and SDSF consoles. 28.2.1 Controlling Consoles There is more to operating an OS/390 system than just entering commands and reading the messages. You should also be familiar with various console configuration options. See Chapters 2 and 3 i[...]

28.2.2.2 Display Areas These may be handy for operating a console with a lot of traffic, when you want to see a multi-line display without having it roll off the screen. However, operators need to be able to manipulate these display areas for efficient operation. Enter ″ K A,NONE ″ to get rid of display areas, or ″ K A,nn ″ to create an are[...]

28.2.3.2 Using SDSF for System Operation Below is the Primary Option Menu for SDSF showing you the basic panels you can use as a full-screen system operator.   HQX1800 ----------------- SDSF PRIMARY OPTION MENU ------------------------- COMMAND INPUT ===> SCROLL ===> CSR LOG - Display the system log DA - Display active users in the sysp[...]

28.3 Controlling the OS/390 System The OS/390 System commands are only a subset of the commands necessary to operate the system. JES2, VTAM, and many other OS/390 components also have a command language which is used to operate their subsystems. We recommend that systems programmers and operators attend a class on basic OS/390 (MVS) and JES2 facili[...]

28.3.3 Stopping the System There are several ways to stop or halt the system, and important subsystems. Here is a simple example of commands to stop the system: $Pxxx Drain all active JES2 printers, initiators and so on P TSO Stop Time-sharing Z NET,QUICK Stop VTAM C APPC Stop APPC (if active) D A,L Display active jobs to see what else needs to be [...]

28.4.3 JES2 Devices Devices such as printers, punches, TP lines, and spool offload tapes can be allocated by JES2 dynamically. The following JES2 command verbs are used to control JES2 devices and are followed by the device name such as PRT1, PUN(12), LINE(5). $D Display the device $S Start the device $P Stop the device when it is through with the [...]

28.5.1.1 MV S Commands Use the DISPLAY JOBS, J, A, or TS command to display information about current system activity, including time-sharing users, batch jobs, and started tasks. The MVS ″ TRACK ″ and ″ MONITOR ″ commands also provide assistance with periodic updated displays in a display area. 28.5.1.2 JES2 Commands There are many JES2 co[...]

28.5.2 Controlling Time Sharing Users TSO/E users logon through terminals controlled by VTAM. You can use MVS or JES2 commands to control TSO users and their output: • Send a Message to a TSO User with the MVS ″ SEND ′ message_text ′, U=userid ″ command. Be careful not to omit the ″, U=( ) ″ operand, or your message will be sent to al[...]

28.6 Managing Remote Operations As with VSE, remote systems and workstations can communicate through NJE or RJE via commands and messages. Some remote workstations and systems have console operators, while others may not. The remainder of this chapter describes how to communicate via JES2 commands. 28.6.1 JES2 RJE Operations There are many kinds of[...]

$D MMn, ′ Please restart my printer ′ Send a message to the operator on member n See JES2 Commands for details. The “Remote Job Entry” section in Chapter 2 has good guidance information for RJE operations, and Chapter 5 has detailed command syntax descriptions. Remotes Without Consoles If you don ′ t have a console on your remote workstat[...]

$D PATH(node_name) Display the path(s) to another node $D Nxx. ′ $D NODE(yy) ′ Send a command to node xx to display the status of node yy $D MNn, ′ Please drain your session ′ Send a message to an operator on another node See JES2 Commands for details. Chapter 4 has good guidance information for NJE operations, and Chapter 5 has detailed co[...]

Chapter 29. Orientation for Utilities 29.1 IEBxxx or IEHxxx There are many utilities in OS/390 provided by DFSMS/MVS to assist you in organizing and maintaining data (most of them start with ″ IEB ″ or ″ IEH ″). These are simple programs which perform commonly needed functions. See ″ Guide to Utility Program Functions ″ in Chapter 1 of [...]

• Reblock or change the logical record length of a data set. • Copy user labels on sequential output data sets. • Supply editing facilities and exits for your routines that process labels, manipulate input data, create keys, and handle permanent input/output errors. Information on IEBGENER is provided in DFSMS/MVS Utilities , SC26-4926. 29.5 [...]

Chapter 30. Systems Management Philosophy and Methodology Many VSE installations have small staff and have mature systems which are changed relatively infrequently. As a user migrates from VSE to OS/390, their entire system -- hardware, software, and connections -- will be subject to more frequent changes. The workloads supported by their system wi[...]

In many smaller computer installations, where at most a few people are involved in system changes, ad-hoc and informal techniques have often proved adequate. All or us have seen a case where the complaint is lodged: ″ It doesn ′ t work right. ″ Oh, what seems to be the problem? ″ Payroll doesn ′ t work right. ″ ″ What did you change? [...]

• Places a stronger emphasis on service, as it promotes keeping one ′ s ″ eye on the ball. ″ • Provides more effective and productive processes. Challenges in this approach are not just to segment the activities, but also to recognize how the disciplines interrelate and how they cross functional boundaries. Also, all responsibilities must[...]

well, and the disciplines should include those to avoid ″ the hole in the boat isn ′ t on my side of the ship, so all is well ″ syndrome that can develop. 30.1.3 The Role of Automation Automation involves the ability to correct, bypass, or circumvent failed system and network elements and applications, based on defined policies and using hard[...]

• Scheduling - occurs during the planning process, and aids in identifying conflicts and impacts, and determines target dates for changes. • Distributing - this depends on the type of change, for example rolling out new levels of software across several systems. • Installing - the actual installation of changes. Installation should be able to[...]

30.3.2 Tasks The problem management process includes the following: • Problem determination - the detection of the loss or impending loss of availability of a system resource to its users, and the isolation of the detected problem to the failing hardware, software, or microcode component. • Problem diagnosis - the determination of the specific [...]

update and manage problem management records, but use of a searchable database technology, such as DB2 or a custom problem management package such as TME 10 Information Management will be very helpful. 30.4 Performance Management 30.4.1 Overview Performance management addresses the effectiveness with which information system components work togethe[...]

⇒ Establishing performance specifications and policies. • Performance execution and measurement ⇒ Response time monitoring - what is the response time as seen by the user? ⇒ Availability monitoring - what ′ s broken? ⇒ Utilization monitoring - who are the biggest users? What is the service times and queue lengths for key components and [...]

Projected trends recorded in this way represent accurate growth measurements. These projections can be used to identify needed changes in system configuration with sufficient lead time to permit orderly procurement and installation of new resources. This will provide the capacity required over time as your system grows. 30.5 Operations Management 3[...]

• Automated Operations - handles the complex operations job scheduling procedures to ensure that work is completed in a timely manner. ⇒ Verifying that the resources needed for a scheduled workload are available; for example, that the required disk or tape volumes are available for a backup operation. ⇒ Planning to ensure the availability of [...]

the MPF list can be customized to carry this out. For other automation tasks, IBM provides several products to support workload and operational planning and control: • TME 10 NetView, while many think of it as a network management product, is also a robust automated operations product for detecting and reacting to messages and alerts (for a wide [...]

The following books contain planning information for automation and illustrate sample automated operational scenarios using IBM Systems Management products: • TME 10 NetView Automation Guide , SC31-8225 • Integrated Centralized Automation/Advanced Operation , GG24-2599 Using the products below to support operational tasks will allow you to supp[...]

30.6.3 Methodology In VSE, users with security needs frequently use one or another vendor security package, as IBM provides only simple access control and logging security. In the OS/390 environment, in addition to vendor program offerings, IBM provides the OS/390 Security Server (a follow on to the highly regarded RACF product). The Security Serve[...]

• Configuration creation - building and maintaining a configuration description that is resource-specific. • Updating configuration information - providing vital product data, topology data, and other configuration data when a change is made to the configuration. • Accessing configuration information - providing information on the actual or p[...]

30.8 Asset Management 30.8.1 Overview Asset management provides for managing the information technology inventory of resources, including both physical and intellectual assets. The components that you will use to support your workloads in the OS/390 environment all have business attributes - just like any asset in your company - that have to be acc[...]

30.9.2 Tasks Accounting management activities include the following: • Measurement - collection of actual usage and service-level data. • Cost allocation - creation of billing and charge-back transactions, including interfaces to other administrative applications or processes. • Allocating and tracking project and other support costs. • Cre[...]

Chapter 31. Diagnosing System Problems 31.1 Problem Determination Tools Several tools are available under OS/390 to help the system programmer diagnose problems. The majority of these tools are intended for system problems rather than application problems and are often activated under the guidance of the IBM or ISV support center. 31.2 Dumps There [...]

• Reduce the size of a stand-alone dump. You can reduce the size of a stand-alone dump as you transfer it from tape to a direct access storage device (DASD) for IPCS processing. 31.3.2 Traces There are a number of traces available in the OS/390 environment: • OS/390 System Trace. A low overhead trace that uses a System 390 architected instructi[...]

31.4 JES2 Diagnosis There are some JES2 mechanisms that can be used for problem determination. • $TRACE: JES2 internal tracing can be activated via $S TRACE; $T TRACEDEF; $P TRACE commands. These are typically requested by IBM service personnel. • SYMREC: Symptom records are recorded in the LOGREC file for some JES2 internally discovered proble[...]

addition, IPCS can be used to format the in-storage LOGREC buffers while analyzing a dump. 31.8 SYSLOG All system and job related messages along with all operator commands are written to the SYSLOG JES spool data set. SDSF (under TSO) can be used to view the SYSLOG to aid in problem determination. 31.9 DFSMS/MVS Diagnosis DFSMS/MVS provides many to[...]

No matter what utility is used to perform the backup and recovery of a catalog, the process isn ′ t complete until the catalog is resynchronized with the data sets as they currently exist. Between the time the catalog was backed up and restored, data sets have been deleted and defined and the catalog has to be updated to reflect these changes. Th[...]

31.9.3 DFSMSrmm The diagnosis document for DFSMSrmm is the DFSMS/MVS DFSMSrmm Diagnosis Guide , SY27-9615. It documents how to obtain diagnostic information, eliminate common sources of errors, using the DFSMShsm Problem Determination Aid (PDA) trace formatter program, and building keyword search strings. Maintaining the DFSMSrmm control data sets [...]

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

480 VSE to OS/390 Migration Workbook[...]

Chapter 3 2 . Conversion Process Converting a data processing installation from VSE/ESA to OS/390 is a complex process that affects all areas of an installation. Personnel must learn different procedures; operations work changes in many ways and applications that run under VSE require conversion before they run under OS/390. Even managing the migra[...]

• Refer to MVS MS - Production Standards , LB11-8080. 6 Translating the programs, taking into account the differences between VSE and MVS for each programming language. • Refer to Part 3, “Converting VSE Languages to OS/390 Languages” on page 2 4 7 . • Refer to the specific program, utility or database section in this book. • Refer to 2[...]

2 Conversion Phases • Initial Trial Conversion • Regression Testing and Repeated Trial Conversions 3 Implementation Phases • Actual Conversion and Switchover • Initial OS/390 Operations This chapter will address these phases along with the key tasks to be completed in those phases. This chapter has been sectioned as follows: 32.1, “Conver[...]

32.1.2 Prerequisites There are two key requirements that need to be satisfied before embarking on a migration: 1 . T h e source code must be available for your applications. I f the source code does not exist then it must be rebuilt. 2 . A method t o transfer the source code to the OS/390 system. 32.1.3 Recommendations The following are recommendat[...]

32.1.3.5 Migrate the SNA Network Early If the migration plan includes converting an SNA communications network, then consider migrating ownership of the network from VSE to OS/390 within the two months that precede operating system switchover. At this time, switchover minus two months, the OS/390 system should be positioned for and nearly productio[...]

32.1.3.7 Two Phase Approach The migration project can be broken into a few logical pieces that may help its execution. One method that has been successful is to begin with a mini project, phase 1, to identify and resolve your inventory. Proceeding with a known inventory will allow more precise cost analysis (time, people resources and so on). The c[...]

32.2.2 Mass Conversion Overview / Benefits Mass conversion is the major distinction of the CORTEX-MS process. It results in a single switchover of the entire VSE application portfolio to OS/390 over a weekend. Until the switchover weekend, all converted applications run in production under VSE. By the end of the switchover weekend, all converted ap[...]

32.2.2.1 Automated Conversion There are several ways to automate some or all of the conversion. The automation that Cortex-MS provides is unique in that it is a mass conversion. After an extensive period of analysis, which includes running both pilot conversions and dummy conversions, you can, in a final mass conversion, convert all of your VSE app[...]

OS/390. Therefore, it is not required to freeze or follow up development, enhancement, or maintenance of applications during the conversion. 32.2.2.3 Mass Conversion (Switchover) The actual mass conversion, called the switchover, often takes place over a single weekend. Before switchover, the production workload runs under VSE. After switchover, th[...]

routines must allow users to custom adapt the tools to specific local conversion requirements. These requirements, not addressed by standard processing, are always identified. The conversion tools must be custom modified by positioning execution options, coding exit routines, and possibly developing some ad-hoc pre- or post-processors. Finally, too[...]

functional descriptions of batch applications (standards and system independent). EZ-PCL (Easy PCL) A PC/MS-Windows based graphic user interface (GUI) to the PDB, which enables definition or modification of batch applications in their flowchart representation. PREP (Preparation) An interactive system of preparation, submission, backout, and restart[...]

• Inventory Validation • Translate the Languages/Programs • Translate the JCL • File Transfer 32.2.5.1 Inventory Validation The Cortex tool cross references the run JCL, the procs, the FCBs and various includes. Then it cross references the source programs, copy books, macros, subroutines, PSBs, the CICS tables and maps for CICS; basically [...]

32.3 Mass Conversion Phase Overview Built on the principles of mass, automated, and repetitive conversion, a mass conversion project is organized in phases, as shown on Figure 58. The figure shows the specific phases and includes an approximate schedule with durations. Figure 58. Project Phases 32.4 Preparation Phases The project phases included in[...]

• Refer to Chapter 3, “Developing the Plan” on page 41 for information on project staffing, assignments and responsibilities. • Refer to Appendix C, “DFSMS Naming Conventions” on page 543 for information on data set naming conventions. • Refer to Appendix A of the MVS-MS Planning Guide for help developing the Migration Plan. • Refer[...]

• At project start • Before the start of online application tests • Before the start of batch application tests • Before switchover During those sessions, the Project Manager and perhaps, hired conversion specialists, provide the conversion team with instructions and guidelines for planning, organization, and implementation of the activitie[...]

The key terms associated with determining your application inventory are: 1. Determination 2. Collection 3. Supply 4. Analysis a nd r esolution of exceptions 32.4.2.1 Determination Determination is the task of understanding what runs in production on the VSE side. It includes finding out all the places where the production JCL is stored and determi[...]

be performed on the VSE side and then sent to OS/390. The determination and collection procedures are developed once and then repeated. The supply is done once per month. Also unique to the Cortex MS environment is that the analysis and resolution work is on going throughout the project. The Cortex tool produces reports listing missing and unrefere[...]

names. This is because naming conventions can facilitate or impair the implementation of OS/390 system components (such as DFSMS) and other automated operations tools. It is recommended that you understand how a production item will be stored, used and managed under OS/390 before giving it a name. Because new OS/390 JCL streams will be generated, n[...]

and parameters), and library members for control cards. This is because many of the VSE names are syntactically incorrect under OS/390. But the conversion of in-house developed applications doesn ′ t require changing any of the names associated with the source code. In fact, it is recommended to leave the program, entry-point, copybook, code incl[...]

References you can consult for additional information about the conversion specification phases include: • Refer to Appendix C, “DFSMS Naming Conventions” on page 543 for information on data set naming conventions that relate to an DFSMS environment. • Refer to Appendix A of the MVS-MS Planning Guide for help developing the Migration Plan. [...]

32.4.4.2 Design the MVS Target Output All the material in this book, including the charts that show functional comparisons of products, is for aiding the analysis of the VSE system to help determine the target OS/390 system. It is during conversion team meetings that these items are presented, challenged and designed. For project organization and p[...]

• tailoring and custom modifying the conversion tools through installation options and exit routines according to the conversion specifications • performing a pilot conversion of a subset of the conversion inventory after having custom modified the conversion tools • auditing the messages and OS/390 material (source code and JCL) produced by [...]

cannot be converted entirely automatically, and for which the unresolved conversion requirement cannot be addressed through VSE positioning. 32.5 Conversion Phases The specific phases included in the Conversion Activities are: • Initial Trial Conversions • OS/390 Regression Tests and Repeated Trial Conversions The objective of the conversion ph[...]

VSE 2.1 for the EXEC statement), or change the program ′ s logic to read and process a ″ control record ″ which would supply any variable information to the program. Additional programming changes and considerations can be found in their respective programming chapters and in the POWER-JES2 differences chapter. The Cortex Migration System can[...]

work, cataloged temporary, handoff, backup, transmit, master sequential, master VSAM, and so on. File classification is a large JCL-related task done to define the life cycle of all of the data sets. This task does not have a high degree of difficulty but typically involves thousands of files. Each file must be classified and this can be very time [...]

The first trial conversion starts with a complete fresh supply of the VSE conversion inventory. Every three to four weeks, the mass conversion starts from a fresh copy of the entire conversion inventory, in order to take into account the last VSE maintenance modifications. Between two supplies, additional mass conversions may be executed from the s[...]

• Simulated production (or acceptance) tests: in conjunction with batch production tests • Network and performance tests with actual connection to future end users OS/390 batch application tests include: • Unit (or technical) tests: on a representative sample of jobs • System (or Functional) tests are scenarios of chained job executions cor[...]

• Application personnel should be made responsible for providing test data, and for evaluating, and approving application test results. (Obtaining test data can be a problem - early plans should be made to define and obtain test data.). Involvement of applications to some degree in the test process can prove beneficial at OS/390 switchover and in[...]

test phase will have its own test plan. The key application development people at the installation must be involved when the test team is assembled. Testing should not be something that just happens. Testing activities are an integral part of any migration plan and must be designed and controlled. When some plans are drafted, all too often, the wor[...]

• Migrating copies of VSE production files, needed for regression tests, to OS/390 • Migrating copies of VSE production databases, needed for regression tests, to OS/390 The conversion project team meets regularly to review the progress and status of the OS/390 tests. OS/390 tests typically take three to five months. The OS/390 test phase is co[...]

The large number of inactive and non-critical or obsolete tape files is not migrated. They are either eliminated, or the VSE volumes are set aside together with a last copy of the VSE tape file catalog at switchover time. Any automated operations product, which will be used for actual production after switchover, must be installed, loaded with data[...]

32.5.6.1 Online Unit Testing Prior to this task, an online test plan, and possibly detailed test scripts, have been developed with and presented to the test team, together with organizational instructions, during a pre-test orientation session. CICS testing is an ideal place to begin the testing process. At least in theory, CICS transactions are fa[...]

the beginning of staggered and overlapping testing. Online system testing may overlap batch unit testing. 32.5.7 System Testing In system testing the goal is to go through the online applications and verify that the outputs from each operating system are similar. In the systems test phase each application is tested in more detail and each applicati[...]

the third job in the sequence is missing due to being treated as a temporary data set. The management of transition files is very different between VSE and OS/390. In OS/390 there are only a couple of possibilities. In VSE it depends on the type of organization, the products used and the traditions followed. These problems don ′ t show up until t[...]

J ob Simulation The goal is to get through as many days as possible. It is a comfort to know at switchover, that a week ′ s jobs can be processed. There are significantly fewer monthly jobs than weekly jobs. There are significantly fewer yearly jobs than monthly jobs. Plan the cutover to not occur at month end. The final phase of parallel testing[...]

32.6.1.1 Converting the Development Material This is the code that the systems programmers are working on. It is recommended that the conversion of these materials take place as early as possible. This conversion is not normally done at switchover time. It is not production material. This task generally coincides with the transfer of a significant [...]

procedure in order to apply jobset maintenance concurrently with maintenance to VSE production. 32.6.2.2 Final Program Conversion There are two key tasks associated with the translation and compilation of all the VSE source materials for the final program conversion. First is the final mass translation with the objective to translate all of the sou[...]

32.6.3.2 Additional Switchover Tasks These tasks may also need to be addressed during switchover: • RJE workstation configurations • NJE end users must change their JCL for job submission • Configuration of PC workstations • Migrate the tape manager to MVS • Migrate the database manager to MVS • Migrate the Report Manager database to MV[...]

Chapter 33. Conversion Services and Tools The actual process of converting JCL and programs from VSE to OS/390 can be a very tedious, time-consuming and labor intensive set of tasks. Fortunately, there are tools available from both IBM and non-IBM sources to help automate most, if not all, of the conversion process. The purpose of this chapter is t[...]

AMS is an IBM Business Partner • Call 1-800-482-6267 or, • Contact AMS through IBM 33.2 Conversion Tools 33.2.1 VSE/ESA Facilities VSE/ESA 2.3 added a new function useful for developing an inventory of a VSE/ESA system ′ s jobs, including the so-called hidden JCL found in standard label areas and in standard assignments. The VSE/ESA JCL Analy[...]

• Program status • Program usage • File cross-referencing • Job cross-referencing 33.2.2.1 Product Highlights IBM OPTI-AUDIT for VSE Version 1.1.0: • Captures and builds an inventory of all programs running on your VSE system • Monitors the execution of batch jobs extracting job/program/file cross-referencing information • Provides a [...]

• REPORT 1 - ACTIVE phases (lists all ′ executed ′ phases by library). • REPORT 2 - INACTIVE phases (lists all ′ dormant or yet to be activated ′ phases by library). • REPORT 3 - Y2KREADY phases (lists all phases flagged as Y2K ready by library). • REPORT 4 - DUPLICATE phases (lists all ′ duplicate ′ phases by library). Log File[...]

33.2.3.1 Product Positioning COBOL and CICS Command Level Conversion Aid for VSE Release 1 is positioned as a COBOL migration aid designed to provide: • Automated conversion of most COBOL syntax differences. • Programmer productivity for the migration process. • Reduction of manual conversion errors. • Flexibility through an open converter [...]

Driver: This component reads the COBOL source program, extracts copy members from the input source file, and executes the conversion process according to the corresponding compiled LCPs. The driver produces four types of output: • New COBOL source code in new source library (optional). • New COBOL copy module in new copy library (optional). •[...]

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 operating systems. CA-Convertor converts VSE COBOL and Assembler language programs and VSE JCL to true MVS programs and JCL, while automatically creating applicable documentation. It performs the burdensome [...]

33.2.6.1 Recovery/SRC This is the basic service provided by SRC. The basic recovery utilizes a proprietary technology that generates the source code from the load module supplied by the client. Data names and labels within the programs recovered are generic. 33.2.6.2 Rename/SRC This is a service that is sold in addition to the basic recovery servic[...]

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

528 VSE to OS/390 Migration Workbook[...]

Chapter 34. Customer Migration Example This chapter describes an actual user experience with migration. Since every customer environment is unique, care should be taken when drawing comparisons, especially in areas of resource and capacity. 34.1 Background Cust1 is a relatively fast growing company that evolved from a small 4341 to a 3-way 9672 in [...]

34.3 Inventory • 1500 COBOL programs - mix of DOS/VS COBOL and COBOL II • 2600 RPG programs • 80 Assembler programs • 8000 JCL steps 34.4 Resources In this project it was sometimes hard to get the various groups to focus on the migration when needed. This was because of other priorities with day to day problems and projects. This is not all[...]

34.5 Duration Due to the data sharing requirements, the availability requirements, and, in general, the dynamic environment of the business, it was decided the mass conversion method was the way to migrate to MVS. In the past years of rapid growth not much time was spent defining and enforcing systems management disciplines which resulted in uncert[...]

about the same after switchover, with MVS showing a couple of percentage points higher. Since the workload at this installation is not the typical online on prime shift and batch on second and third, it was not as easy to make comparisons on a batch window length. Overall it appeared that throughput was much better. There were other performance ben[...]

Part 9. Appendixes  Copyright IBM Corp. 1998 533[...]

534 VSE to OS/390 Migration Workbook[...]

Appendix A. Education Information The task of providing the right training, to the right people, at the right time, at the right location is a small project of its own. There are many variables to consider, including costs, not the smallest of which is simply determining if a particular course is available. A good training plan will be the right ba[...]

It is recommended that a class on TSO and ISPF, to help navigate through panels, be taken prior to the MVS Installation and SMPE class. The IBM SMPE class is a good and necessary prerequisite to the MVS install class. SMPE is similar to VSE MSHP. It provides key information on installing products and applying PTFs and is good for VSE systems progra[...]

A.3 Who will Provide the Training? Hiring a skilled MVS person for the migration, whether temporary or permanent, helps with the skill level of that one person. Don ′ t assume that the person is a skilled educator or will have time to teach a curriculum to other team members in his/her spare time. It is likely that this person will have a list of[...]

538 VSE to OS/390 Migration Workbook[...]

Appendix B. Mapping ISV Products and Functions This is a frequent topic of discussion with customers considering migrating. How a customer ′ s ISV products map to those contained in base OS/390 is always discussed. It is a common migration task to ensure there is equality. This equivalent function mapping will grow in importance as coexistence is[...]

Table 46 (Page 2 of 3). S/390 Software Product Mapping Vendor Vendor Product I B M Product PID # Primary Function(s) Migration Services BMC Unload Plus IMS Utilities 5685-093 I MS utility IGS CA CA-ADS/Online CSP/AD CSP/AE High Level Language (IDMS) CA CA-Alert/CICS RACF 5645-001 CICS Security Tivoli Migration Team CA CA-ASM2 DFSMS/hsm 5645-001 Hos[...]

Note: PID #s and Product Functions should be checked by the user prior to ordering any software. Table 46 (Page 3 of 3). S/390 Software Product Mapping Vendor Vendor Product I B M Product PID # Primary Function(s) Migration Services Mobius Infopac report RMDS 5648-048 Report distribution Electronic Archive Solutions Mobius Infpopac Schedule OPC 569[...]

542 VSE to OS/390 Migration Workbook[...]

Appendix C. DFSMS Naming Conventions This chapter was written by John Tyrrell of IBM ′ s Storage Systems Division. John is one of the original senior architects of DFSMS. He also invented TMM (Tape Management Methodology) and is the author of the Volume Mount Analyzer program which is part of DFSMSdfp. He is the senior architect/inventor of the D[...]

There are two basic pieces of information that one should be able to obtain from the data set name: 1 . W h o owns i t ? 2. What i s i t? The following section will highlight all of the basic components that could potentially be used in a data set naming standard. C.2 Components of a Data Set Name Not all of the following levels of qualification ar[...]

individuals keep a standard LOGON ID, and change the set of filters instead of the IDs. As an example of this set of conventions, consider a common problem of constantly shifting workloads. If the Storage Administrator was always faced with getting the data for a given application and moving it to another system, then it would make good sense to ha[...]

− E3380D − E3380S − E3990M3 − E3990M2 The above example would allow various filtering techniques the flexibility of recognizing different sets of data easily. Some examples of this follow: • HLQ = E* -- All of the Engineering Data • HLQ = E3090* -- All of the 3090 CPU Family of Designs • HLQ = E3380* -- All of the 3380 DASD Family of [...]

readable, such as, a file called MASTER.PAYROLL.WEEKLY . This might be just too tempting to your average system hacker. A better choice might be MR.PY.WK. C.2.4 User Name This qualifier should allow the end creator to assign their own unique name to identify the particular set of a certain type of data; for example, with a master circuit file, ther[...]

C.3.2 Application Location If this application ever got moved to another site, then all of the data sets would have to be renamed. In some cases, it could be important to name the data by a location name, for example, CHICAGO. This could be perfectly acceptable in certain cases. Suppose there were two telephone directory files, ″ TELPHDIR.CHICAGO[...]

C.3.6 Access Method At one point in time, many installations adopted a policy of distinguishing VSAM data from non-VSAM data. The reality behind this standard was that there were many functions that were not supported for VSAM and this was an easy way to recognize that data. The main reason for this distinction was because of old VSAM catalogs and [...]

usability of the system and the need to manage it differently based on what set of data this actually is. C.4.2 VSAM Data Set Naming Conventions Many companies have decided that it is a good idea to associate all of the VSAM components with the base cluster by some recognition pattern. Some of the reasons behind this have to do with billing, and al[...]

within the data set name so that ACS Routines can easily ascertain one piece of data from another. The only alternative to this is to place a very restrictive convention on the qualifiers that can be specified. For example, you could break down the table space name by having positional characters represent different levels of qualification for the [...]

552 VSE to OS/390 Migration Workbook[...]

Appendix D. Special Notices This publication is intended to help customers and IBM technical personnel to migrate from VSE to OS/390. The information in this publication is not intended as the specification of any programming interfaces that are provided by VSE or OS/390. See the PUBLICATIONS section of the IBM Programming Announcement for VSE/ESA [...]

including these reference numbers is to alert IBM customers to specific information relative to the implementation of the PTF when it becomes available to each customer according to the normal IBM PTF distribution process. The following terms are trademarks of the International Business Machines Corporation in the United States and/or other countri[...]

The following terms are trademarks of other companies: 1-2-3 is a trademark of Lotus Development Corporation ADE is a trademark of Loral/Rolm Mil-Spec ATM is a trademark of Adobe Systems, Incorporated C-bus is a trademark of Corollary, Inc. C++ is a trademark of American Telephone and Telegraph Company, Incorporated CA is a trademark of Computer As[...]

OMEGAMON is a trademark of Candle Corporation ONC is a trademark of Sun Microsystems, Incorporated Open Software Foundation is a trademark of The Open Software Foundation, Incorporated Oracle is a trademark of Oracle Corporation OSF is a trademark of Open Software Foundation, Incorporated PC Direct is a trademark of Ziff Communications Company and [...]

Appendix E . Related Publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. E. 1 International Technical Support Organization Publications For information on ordering these ITSO publications see “How to Get ITSO Redbooks” on page 561. E.1.1 [...]

E.2.1 Planning Books The following hard-copy books are part of the OS/390 Installation Planning Kit which can be ordered by publication number GK2T-6710: Other OS/390 Books: There are many other introductory and planning books available in the OS/390 library. Here are some of the most important ones you should be familiar with: Book Title Publicati[...]

E. 3 Other Publications Book Title Publication Number RACF General Information GC23-3723 Getting Started with DFSORT SC26-4109 Get DFSMS FIT: Fast Implementation Techniques SG24-2568 DFSMS FIT: Fast Implementation Techniques Process Guide SG24-4478 DFSMS FIT: Fast Implementation Techniques Installation Examples SG24-2569 E. 4 Other Sources E.4.1 Bo[...]

560 VSE to OS/390 Migration Workbook[...]

How to Get ITSO Redbooks This section explains how both customers and IBM employees can find out about ITSO redbooks, CD-ROMs, workshops, and residencies. A form for ordering books and CD-ROMs is also provided. This information was current at the time of publication, but is continually subject to change. The latest information may be found at http:[...]

How Customers Can Get ITSO Redbooks Customers may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about redbooks, workshops, and residencies in the following ways: • Online Orders — send orders to: • Telephone Orders • Mail Orders — send orders to: • Fax — send orders to: • 1-800-IBM-4FAX (United[...]

IBM Redbook Order Form Please send me the following: Title Order Number Quantity First name Last name Company Address City Postal code Country Telephone n umber Telefax number V A T number • Invoice to customer number • Credit card number Credit card expiration date Card issued to Signature We accept American Express, Diners, Eurocard, Master C[...]

564 VSE to OS/390 Migration Workbook[...]

Glossary Numerics 2-digit-year format . A format that provides a year date as two digits only to represent a year within a specific century. The two high-order digits of the year are truncated; for example 1995 is represented as 95 . 4-digit-year format . A format that provides a year date as four digits: the two high-order digits represent the cen[...]

MO:DCA-P is the strategic AFP interchange data stream, and IPDS is the strategic AFP printer data stream. alphabetic character . Any one of the letters A through Z (uppercase and lowercase). Some licensed programs include as alphabet characters the special characters #, $, and @. alphanumeric . Pertaining to data that consist of letters, digits, an[...]

B background partition . In VSE, a space of virtual storage in which programs are executed under control of the system. By default, the partition has a processing priority lower than any of the existing foreground partitions. backout . See file and catalog backout. backup copy . A copy of information or data that is kept in case the original is cha[...]

CCYY format . A 4-digit-year format that uses two century digits (CC) to indicate the century and two year digits (YY) to indicate the year within the century. The CC representation is provided as either the actual century digits (for example, 18, 19, or 20) or as an encoded value (for example, as 00 to represent 19, 01 to represent 20 as in, 0095 [...]

CP command . In VM, a command by which a terminal user controls his virtual machine. The VM/370 control program commands are called CP commands. The CP commands that perform console simulation are called console functions. cross-domain resource . (1) Deprecated term for other-domain resource. (2) In VTAM programs, synonym for other-domain resource.[...]

Device Support Facilities (DSF) . An IBM-supplied system control program for performing operations on disk volumes so that they can be accessed by IBM and user programs. Note: Examples of these operations are initializing a disk volume and assigning an alternate track. device-independent . Pertaining to a program that can be executed successfully w[...]

features to permit a computing system to execute programs written for another system. emulator . A combination of programming techniques and special machine features that permits a computing system to execute programs written for a different system. See also integrated emulator, terminal emulator. entry-sequenced data set . In OS/390 programs with [...]

GRS . global resource serialization. A component of MVS/ESA SP used for sharing system resources and for converting DASD reserve volumes to data set enqueues. Guest Operating System (GOS) . A second operating system that runs on the primary operating system. An example the second operating system is VSE and/or OS/390 and/or TPF etc. running on VM/E[...]

purpose of modifying or extending the functions of the IBM software product. integer date . A count of days since a specified date. Various IBM software products have defined integer dates as follows: Language/Product Days Since C 1969-Dec-31 COBOL 1600-Dec-31 Language Environment 1582-Oct-14 MVS/CICS/DB2 1899-Dec-31 integrity . The protection of s[...]

Job Entry Subsystem . An MVS subsystem that receives jobs into the system, converts them to internal format, selects them for execution, processes their output, and purges them from the system. In an installation with more than one processor, each JES2 processor independently controls its job input, scheduling, and output processing. job step . You[...]

link-edit . To create a loadable computer program by means of a linkage editor. load module . An application or routine in a form suitable for execution. The application or routine has been compiled and link-edited; that is, address constants have been resolved. load module library . A partitioned data set used to store and retrieve load modules. S[...]

multivolume file . A file contained on more than one storage medium. N NetView DM . IBM NetView Distribution Manager. network definition . In VTAM, the process of defining the identities and characteristics of each node in the network and the arrangement of the nodes in that system. network management . The process of planning, organizing, and cont[...]

routines. They can run on different computers with little or no modification. PDS . partitioned data set. A data set in direct access storage that is divided into partitions, called members, each of which can contain a program, part of a program, or data. Contrast with sequential data set. PDSE . partitioned data set extended. A system-managed data[...]

Q qualified name . (1) A data name explicitly accompanied by a specification of the class to which it belongs in a specified classification system. (2) A name that has been made unique by the addition of one or more qualifiers. R RACF . Resource Access Control Facility. An IBM-licensed program that provides for access control by identifying and ver[...]

sequential data set . A data set whose records are organized on the basis of their successive physical positions, such as on magnetic tape. Contrast with direct data set. sequential file . A file in which records are processed in the order in which they are entered and stored in the file. Contrast with direct file, indexed file. sequential processi[...]

Storage Management Subsystem (SMS) . A component of MVS/DFP that is used to automate and centralize the management of storage by providing the storage administrator with control over data class, storage class, management class, storage group, and ACS routine definitions. structured programming . A method for constructing programs using only hierarc[...]

T task . (1) In a multiprogramming or multiprocessing environment, one or more sequences of instructions treated by a control program as an element of work to be accomplished by a computer. (2) In VSE, the basic unit of synchronous program execution. A task competes with other tasks for computer system resources such as processing time and I/O chan[...]

V verification test . A test of a system to prove that it meets all its specified requirements at a particular stage of its development. virtual address . The address of a location in virtual storage. A virtual address must be translated into a real address in order to process the data in processor storage. virtual address space . (1) In virtual st[...]

List of Abbreviations ABEND ABnormal E N D ACB Access Control Block ACF/NCP Advanced Communications Facility/Network Control Program ACF/SSP Advanced Communications Facility/??? ACIF AFP Conversion and Indexing Facility ACS Automatic Class Selection ADSTAR ADvanced STorage And Retrieval AFF AFFinity AFP Advanced Function Presentation AFPDS Advanced[...]

CGI Common Gateway Interface CHKPT CHecKPoinT CI Control Interval CICS Customer Information Control System CICS/DOS/VS Customer Information Control System/Disk Operating System/Virtual Storage CICS/VS Customer Information Control System/Virtual Storage CLIST Command LIST CMIP Common Management Information Protocol CMOS Complementary Metal Oxide Sem[...]

DSCB Data Set Control Block DSECT Dummy Control SECTion DSN Data Set Name DSNAME Data Set NAME DSNX Distributed Systems Node eXecutive DSS Data Set Services DTF Define The File DTL Define The Lock EBCDIC Extended Binary Coded Decimal Interchange Code ECB Event Control Block ECSA Extended Common Service Area EMIF ESCON Multiple Image Facility ENDREQ[...]

HPR High Performance Routing HSM Hierarchical Storage Manager HTML HyperText Markup Language HTTP HyperText Transfer Protocol I/O Input/Output I/S Information Systems I/T Information Technology IBM International Business Machines ICA Integrated Communications Adapter ICCF Interactive Computing and Control Facility ICF Interactive Command Facility I[...]

LPAR Logically PARtitioned mode LRECL Logical RECord Length LRU Least Recently Used, Line Replaceable Unit LSPR Large Systems Performance Reference LSR Local Shared Resources LTM Local Transport Mechanism LU Logical Unit LUP Logical User Profile MAPS SNA Network Interconnecting Package MAS Multi-Access Spool MB MegaByte MCS Multiple Console Support[...]

PPFA Page Printer Formatting Aid PPT Processing Program Table PR/SM Processor Resource/Systems Manager PROC PROCedure PROP PRogrammable OPerator PS Personal System PSB Program Specification Block PSF Print Service Facility PSF/6000 Print Service Facility/6000 PTF Program Temporary Fix PW PassWord QISAM Queued Indexed Sequential Access Method QMF Qu[...]

SPG Service Planning Guide SPI System Programming Interface SPIE Specify Program Interruption Exit SPOOL Simultaneous Peripheral Operation On-Line SPUFI SQL Processor Using File Input SQL Structured Query Language SQL/DS Structured Query Language/Data System SQLCA SQL Communication Area SRL Systems Reference Library SRM Systems Resources Manager SS[...]

VTAM Virtual Telecommunications Access Method VTOC Volume Table of Contents VVDS VSAM Volume Data Set VVR VSAM Volume Record WS Work Station WSC Washington Systems Center WTM Write Tape Mark WTO Write To Operator WTOR Write To Operator with Reply WWW World Wide Web XCF Cross-system Coupling Facility XCTL Transfer ConTroL XEDIT eXtended EDITor XMT T[...]

Index Special Characters * $$ DATA 89 * $$ LST 8 9 &SYSNAME 11 5 %INCLUDE 3 35 Numerics 2-digit-year format definition 56 5 20th century definition 565 21st century definition 565 24x7 installations 485 4-digit-year format definition 56 5 A abbreviations 5 8 3 ABEND forcing 344 ABEND macro 280 abnormal termination exits 364, 365, 367 ACB additi[...]

APSRMARK (MVS) 24 0 APTRMARK (VSE) 240 APTZPARM macro 2 41 ASCII subsystem 1 8 8 Assembler CALLDLI 17 3 conversion comments 26 7 conversion tools 49 2 general conversion comments 26 7 initiation 2 6 9 migrating applications 35 9 migration 3 5 9 products 2 6 7 programming interfaces 24 1 TCP/IP applications using sockets API 196 termination 2 6 9 us[...]

Assembler Products (continued) data management macros (continued) multiple search / feedback 325 NOTE macro 299, 309 OPEN macro 297, 304 overview of programming elements 32 7 PIOCS 327 POINTS macro 300, 308 POINTW / POINTR macros 299, 308 processing a DAM File under MVS 324 processing a DAM File under VSE 324 PRTOV macro 296 READ macro 307, 313 rec[...]

batch (continued) TCP/IP 19 5 unit testing 51 2 B CP customization 41 5 BDAM 9 8 benefits customer migration 53 2 bibliographies COBOL 251 diagnostic reference 47 8 Language Environment 35 3 MQSeries 2 0 6 PSF/MVS 244 PSF/VSE 244 REXX 372 bibliography 5 5 7 BLKSIZE definition 293 BLL cells 252 book synopsis 3 broadcast data set 15 7 BSC remotes def[...]

CICS (continued) MRO 1 3 6 MVS management modules 14 2 PL/I 346 problem determination considerations 15 3 programs 2 5 2 run-time options 36 6 shutdown statistics 13 7 system control blocks 138 data sets requirements 14 5 initialization parameters 14 0 program interface 14 7 programming commands 14 7 testing considerations 15 3 transaction attribut[...]

comparing (continued) P S F commands 2 4 2 VSE & MVS JCL 86, 91 compatibility 344, 346 compiler option considerations for VS COBOL II 261 compiler options 260, 335 compiler options unavailable with COBOL for OS/390 and VM 260 compiling converted COBOL programs 26 5 complexity of implementation 51 component terminology for MVS 21 COMPRESS 121 Co[...]

conversion phases (continued) unit testing (continued) timing between on-line & batch testing 512 conversion process assumptions 4 8 6 introduction 4 8 2 prerequisites 4 8 4 recommendations 24x7 installations 485 manuals 4 8 4 migrate SNA network 48 5 project management 48 4 secure OS/390 skills 484 tools & automation 48 4 two phase approac[...]

data access 18 2 driven output segmentation 75 entry 7 6 integrity 1 2 5 management macros 29 2 management standards 40 7 manipulation 1 5 9 replication 1 8 2 sharing 1 2 5 TCP/IP related 195 transfer and NJE 405 Data Base Descriptor (DBD) 170 Data Control Block (DCB) 98 DATA DIVISION - FILE DESCRIPTION (FD) 256 data set CICS system requirements 14[...]

device (continued) control 4 4 8 information 3 2 9 migration 3 6 status display 44 8 supported by OS/390 402 DFDSS 23 DFHMSCAN utility 152 DFHSM 23 DFSDSdss 101 DFSMS FIT 102 DFSMS implementation 10 2 DFSMS naming conventions 54 3 DFSMS/MVS diagnosis 476 DFSMSdfp analyzing catalogs for errors and synchronization 4 7 6 catalog recovery 47 6 checking[...]

DOS/VS COBOL (continued) REPORT WRITER statements 253 reserved word considerations 26 3 DOS/VS COBOL & COBOL for OS/390 and VM language differences Common COBOL Coding Problems 253 DATA DIVISION - FILE DESCRIPTION (FD) 256 ENVIRONMENT DIVISION 255 file handling considerations file attribute mismatches 25 8 file status codes 257 ISAM 2 5 8 PROCE[...]

EXLST macro 2 91 expanded JC L 7 6 expiration date 54 8 extended MCS consoles 445 extended precision 33 4 extent exit 33 0 EXTENT statement 83 external side definition 57 1 F Fast Copy 124, 397 FBA DASD 108, 120 FCB incompatibilities 2 0 9 naming differences 21 7 prefixes 2 17 specification 2 18 FCEPGOUT macro 290 FDUMP compiler option 263 fee-base[...]

HLL programming interfaces 24 2 host operations 45 2 I I/O error checking 294 IBM COBOL & CICS CCCA 522 COBOL compilers - comparison 250 Global Services 51 9 OPTI-AUDIT for VSE 520 ICCF 155 /CMS/TSO 21 8 & TSO 155 command procedures 16 3 library conversion 16 3 LOGON procedures 157 macros 1 6 7 procedures 1 6 7 program execution 16 1 securi[...]

introducing PSF/MVS (continued) functional comparison (continued) PSF/MVS exclusives 235 migration effort 23 5 introduction to console operation 44 3 to DL/I and IMS/VS 169 to sizing 13 to test environments 41 9 to VSAM differences 110 introductory documentation 39 inventory validation 49 2 IOREG 293 IPCS analyzing dumps 47 3 analyzing traces 47 4 [...]

JCL differences (VSE and MVS) (continued) VSE Job Control statements ASSGN statement 83 CAT= on DLBL 83 conditional JCL 84 DLBL and EXTENT 83 EXEC statement 82 JOB statement 82 MTC statement 83 RESET statement 83 TLBL statement 82 JCL high level similarities JCL statement & job layout conditional JCL 73 continuation cards 72 EXEC (job step) 72 [...]

JES2/POWER functional comparison (continued) output service (continued) printers supported 21 6 separator page differences 21 7 tape spooling 21 6 UCS naming conventions 21 8 RAS characteristics remote job entry functional RJE differences 219 remote workstation definitions 21 9 RJE exits 220 RJE operations 220 JES3 21, 151 job 7 0 accounting 2 2 3 [...]

loading a DAM File (Fixed-Length Records without keys) 32 3 loading a DAM File (Undefined or Variable-Length Records) 32 3 LOCK & UNLOCK macros 281 log manager 14 5 logical library structure 38 9 logical partitioning 42 2 LOGON procedures 157 LOGREC 475 LPAR systems 421 LTM subparameter 10 5 M macro level programs 137, 148 Macro Resource Defini[...]

migrating from LE/VSE-conforming languages 353 C for VSE/ESA 353 COBOL for VSE/ESA 354 PL/I for VSE/ESA 354 migrating from non-LE/VSE run-time environments 3 5 4 C/370 355 DOS PL/I 356 DOS/VS COBOL 356 migrating Assembler applications 35 9 migrating interlanguage communications applications 3 5 8 options mapping 35 4 VS COBOL II 355 VS FORTRAN 358 [...]

MVS (continued) device addresses 80 DFP 21 DISPLAY command 4 4 7 execution overrides 1 4 9 exits 4 15 IEFBR14 78 initialization routine 2 69 JCL - a summary 88 JCL - sample 93 JCL versus VSE JCL 73 JES2 additional job scheduling functions 214 Job Control statements 84 linkage macros 27 1 Migration System 48 6 multitasking macros 28 3 naming standar[...]

OPTI-AUDIT highlights 5 2 1 OPTI-AUDIT product details 521 option setting recommendations 36 3 optional features for release 4 416 options mapping 3 5 4 specific to DOS 343 specific to DOS compiler 335 specific to MVS 344 specific to MVS compiler 336 order and install the OS/390 software 405 ordinal day of year definition 576 orientation for utilit[...]

OS/390 documentation resources introduction references 39 key documents & other references 40 Web URL 40 OS/390 hardcopy processing 393 OS/390 software - order and install entitled methods of installing OS/390 CBPDO 407 ServerPac 4 06 fee-based installation methods 40 5 installing OS/390 fee-based 405 other offerings 40 6 SoftwareXcel Installat[...]

PL/I (continued) storage management 34 5 subprograms 3 3 1 VSAM support 13 1 PL/I and CICS 346 calling DUMP 346 CICS transaction backout 347 compatibility 3 4 6 execution options 34 6 file support 34 6 return from ON-units 34 7 statements not supported 34 6 transaction ABEND codes 346 PL/I calling SORT interfaces offered 34 0 parameters to be passe[...]

POWER/JES2 detailed comparisons (continued) POWER/JES2 command equivalences control commands 23 3 file control 23 4 network management 23 3 NJE operator commands 233 queue management commands 23 2 sending commands & messages 23 4 task management commands 23 2 preparation phases 49 3 OS/390 standards & naming conventions 497 Phase 0: project[...]

project (continued) plan summary 5 6 planning 3 7 planning & orientation 49 4 schedule 5 4 staffing 43 tasks 47 PRTOV macro 296 PSB 171 PSETUP 208, 217 PSF command comparison 24 2 migrating resources 24 0 printer definitions 23 7 remote-resident resources 24 0 starting and stopping 24 2 startup procedures 23 7 supplied utilities 24 4 PSF/MVS ac[...]

resources (continued) operation 1 8 7 remote-resident 2 4 0 RESTART with CHKP 173 retrieving output 44 1 RETURN CODE 3 41 return codes 73 return codes in PL/I 344 return code values 34 4 setting return codes 34 4 RETURN macro 273 reusable data sets 123 Rewind option 17 3 REXX 163, 242, 369 and SAA 37 2 and TSO/E 369 and VSE/ESA 369 bibliography 3 7[...]

setting up AFP resources (continued) migrating print applications (continued) OS/390 dynamic allocation & output descriptor macros 2 4 2 PL/I 242 printing from TSO 241 REXX 242 VSE printer PARM macro 241 migrating resources from VSE to OS/390 defining resources 24 0 migration without the source 24 0 remote-resident resources 24 0 transferring p[...]

stand-alone systems 4 21 stand ard applications 19 5 stan dard labels 7 8, 1 0 3 standard user labels 10 5 standardized conversion deliverables 51 standards 4 0 7 standards, procedures, documentation documentation hardcopy library 41 2 printing softcopy books 41 2 redbooks 4 1 2 softcopy library 41 2 installation standards DASD and tape volume seri[...]

systems management (continued) summary 4 7 2 Systems Management Recording printing SMF records 39 5 T tailoring JES2 211 tailoring other components 41 6 tape differences 1 03 drives 4 0 4 file definition 297 labels 3 30 similarities 1 0 3 spooling 208, 216 storage considerations 97 tape similarities & differences bypass label processing facilit[...]

U UCS naming conventions 21 8 understanding device allocation 44 8 understanding operational differences 24 2 understanding the operator interfaces controlling consoles 44 4 extended MCS consoles using SDSF for system operation 446 using the TSO/E functions 445 managing display consoles console modes 44 4 display areas 44 5 PFKeys 44 5 understandin[...]

VSAM (continued) managed SAM files 12 2 managed space 15 moving catalog to different DASD type 11 9 MVS VSAM CHECK macro 292 NOALLOCATION data sets 123 OS/390 Backup/Restore 3 8 7 catalog management 11 4 cross-region SHR(4) 127 cross-system shareoptions 12 9 master catalog 11 4 user catalogs 11 5 VSE catalog compatibility 117 programming language s[...]

VSE (continued) virtual storage macros 28 9 VSAM backup/restore 38 7 VTAM 1 8 8 VSE & MVS JCL comparison 91 sample MVS JCL 93 sample VSE JCL 92 sample VSE plus carry-over 94 VSE/ESA conversion facilities 520 VSE/ESA environment 370 VSE/ESA ′ s JCL philosophy 70 VSE/Fast Copy 397 VSE/Fast Copy online 397 VSE/ICCF to MVS 163 VSE/ICCF to TSO/E 1[...]

ITSO Redbook Evaluation VSE to OS/390 Migration Workbook SG24-2043-00 Your feedback is very important to help us maintain the quality of ITSO redbooks. Please complete this questionnaire and return it using one of the following methods: • Use the online evaluation form found at http://www.redbooks.ibm.com • Fax this form to: USA International A[...]

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

/XRL/1 Artwork Definitions id File Page References WOLOGO 2043SU i WOLOGOS 2043SU i TILOGO 2043SU i TILOGOS 2043SU i Table Definitions id File Page References COBCMP 2043VARS i i, i, i, i, i, 250 HDR1 2043VARS i LPUBS1R 2043VARS i i, 353 LPUBS1H 2043VARS i 353 MAINTB 2043VARS i MVSFB 2043VARS i MVSFBK 2043VARS i ONE 2043VARS i PLNBOD1 2043VARS i i,[...]

/XRL/2 R2 REDB$EVA 621 621 R1 REDB$EVA 621 621, 621 Figures id File Page References VAE 2043CH01 61 6 VAE4 2043CH01 72 7 ESA 2043CH01 83 8 OS3 2043CH01 94 9 MGTEAM 2043CH03 45 5 45 JMPVMC 2043CH03 49 6 49 F011 2043CH05 107 7 105, 106 WSC9741 2043CH05 113 8 117 F042 2043CH05 116 9 F054 2043CH06 136 11 136 CICSDMS 2043CH06 139 12 138 CICSLSC 2043CH06[...]

/XRL/3 274 29 273 F1010 2043CH13 279 30 278 F1011 2043CH13 295 31 294 F1012 2043CH13 295 32 294 F1038 2043CH13 296 33 294 F1013 2043CH13 297 34 296 F1014 2043CH13 302 35 301 F1015 2043CH13 303 36 301 F1016 2043CH13 304 37 303 F1017 2043CH13 310 38 309 F1018 2043CH13 311 39 309 F1019 2043CH13 312 40 311 F1020 2043CH13 313 41 312 F1021 2043CH13 317 4[...]

/XRL/4 JMPP 2043CH32 493 58 493 Headings id File Page References REDBCOM REDB$COM xxii Comments Welcome PLNG 2043IMBD 1 Part 1, Planning the Migration - An Introduction 3, 3, 3 TREAS 2043CH01 4 1.2, Traditional Reasons for Migrating 3 FREAS 2043CH01 10 1.3, Functional Reasons for Migrating to OS/390 3 INTSIZ 2043CH02 13 2.1, Introduction to Sizing [...]

/XRL/5 69 Chapter 4, Job Control Language (JCL) Differences and Considerations 209, 375, 482 JCLFIL 2043CH04 69 4.1, The Philosophy of JCL in System/390 69, 73 JCLHI 2043CH04 72 4.2, High Level Similarities 69 CONJCL1 2043CH04 73 4.2.1.9, Conditional JCL JCLDIFF 2043CH04 73 4.3, JCL Differences Between VSE and MVS 69 JCLRED 2043CH04 76 4.3.2, JCL E[...]

/XRL/6 16 9 Chapter 8, Databases 18, 18, 366 DLIUTIL 2043CH08 173 8.1.6, Utilities 176 TELECOM 2043CH09 18 5 Chapter 9, Telecommunications Subsystems 17, 17 AVTAM 2043CH09 18 5 9.1, ACF/VTAM 185 H2043A1 2043CH09 186 9.1.1.1, VTAM Data Sets 186 H2043A2 2043CH09 192 9.2, ACF/NCP 185, 190 TBTAM 2043CH09 193 9.3, BTAM 185 TCPIP 2043CH09 193 9.4, Migrat[...]

/XRL/7 AFPPSF 2043CH11 23 5 Chapter 11, Advanced Function Printing and Print Services Facility/MVS 17, 17, 215 PSFINCN 2043CH11 236 11.2, Installing and Configuring PSF/MVS 236 PSFRES 2043CH11 240 11.3, Setting up AFP Resources 236 PSFAPPL 2043CH11 241 11.3.4, Migrating Print Applications 236 AFPPPM 2043CH11 24 1 VSE Printer PARM Macro PSFOPS 2043C[...]

/XRL/8 17, 17, 258, 259 CONDIF 2043CH17 352 17.1.2, Conceptual Differences between LE/VSE and OS/390 Language Environment 361 LVMC 2043CH17 352 17.2, VSE to OS/390 Migration Considerations LEVCON 2043CH17 352 17.2.1, LE/VSE-conforming Languages NONLEMG 2043CH17 354 17.4, Migrating from Non-LE/VSE Run-time Environments C370HD 2043CH17 355 17.4.2, C/[...]

/XRL/9 407 25.4, Set Up Standards, Procedures, and Documentation 100, 481 PUTRSU 2043CH25 414 25.5.1.2, Applying Preventive Service 411 SETERM 2043CH25 414 25.5.1.3, Providing Terminal Access to the OS/390 System 404 SETNJE 2043CH25 415 25.5.1.5, Providing NJE Connection to the OS/390 System 405 TESTENV 2043CH26 419 Chapter 26, Test Environments 48[...]

/XRL/10 482, 482, 483 IMPF 2043CH32 515 32.6, Implementation Phases 482, 483 CNVSRVS 2043CH33 519 33.1, Conversion Services 519 CNVTOOL 2043CH33 520 33.2, Conversion Tools 483, 519 MIGEXMP 2043IMBD 52 7 Part 8, Migration Experience 3, 4 MIGEXP1 2043CH34 52 9 Chapter 34, Customer Migration Example 483 APPXS 2043IMBD 53 3 Part 9, Appendixes 4 AX2 204[...]

/XRL/11 i (1) CICS 133, 133, 134, 135, 135, 136, 136, 136, 137, 137, 138, 138, 140, 140, 142, 143, 145, 147, 147, 149, 150, 151, 152, 153, 153, 153, 154, 154, 201, 201, 201, 252, 252, 252, 346, 366, 366, 367, 522, 522 C120001 2043VARS i (1 ) COBOL 131, 131, 131, 242, 249, 249, 249, 250, 250, 250, 250, 251, 252, 252, 252, 252, 253, 253, 253, 255, 25[...]

/XRL/12 72, 73 C040004 2043VARS i (1) JECL 89, 89, 89, 90 C100003 2043VARS i (1) JES2/POWER functional comparison 212, 213, 215, 218, 219, 220, 221, 223, 224, 225 C170001 2043VARS i (1 ) Language Environment (LE) 196, 351, 351, 352, 352, 352, 353, 353, 353, 354, 359, 359, 365, 366 C150003 2043VARS i (1 ) linkages between languages 338, 338 C280006 [...]

/XRL/13 235, 235, 236, 243, 243, 243, 244, 244 C110004 2043VARS i (1 ) PSF/MVS operational differences 242, 242 C110006 2043VARS i (1 ) PSF/MVS references 244, 244, 244, 244, 244, 245 C120009 2043VARS i (1 ) reserved words 263, 265 C150008 2043VARS i (1 ) return codes in PL/I 344, 344 C140001 2043VARS i (1) RPG II migration to OS/390 329, 329, 330,[...]

/XRL/14 ECH0003 2043VARS i (1 ) Assembler 131, 173, 196, 241, 267, 267, 267, 269, 269, 359, 359, 359, 364, 492 ECH0004 2043VARS i (1 ) VSAM 15, 81, 110, 110, 110, 112, 114, 118, 118, 118, 118, 119, 119, 119, 119, 119, 121, 122, 122, 122, 123, 123, 123, 124, 125, 129, 130, 130, 131, 131, 290, 292, 292, 292, 292, 292, 292, 292, 387, 387, 455, 477, 47[...]

/XRL/15 3, 3, 4, 4, 10, 10, 13, 18, 27, 28, 29, 35, 35, 35, 36, 39, 42, 43, 44, 134, 163, 182, 193, 205, 235, 241, 250, 251, 329, 352, 353, 354, 358, 359, 371, 401, 420, 485, 529, 529, 531, 531, 532 ECH0024 2043VARS i (1 ) SORT 131, 341, 341, 342, 377, 379, 379 ECH0025 2043VARS i (1 ) DASD 16, 108, 108, 108, 108, 108, 109, 120, 129, 129, 130, 304, [...]

/XRL/16 GENIND 2043VARS i (1 ) general 135, 136, 311, 351 HIGHIND 2043VARS i (1 ) high level 72, 242, 364, 544 IBMIND 2043VARS i (1) I B M 250, 519, 520, 522 ICCFIND 2043VARS i (1) ICCF 155, 157, 157, 161, 163, 163, 167, 167, 218, 437 INSTIND 2043VARS i (1 ) installation 200, 211, 243, 402, 405, 407, 410 INTRIND 2043VARS i (1 ) introduction 13, 110[...]

/XRL/17 i ( 1 ) program 33, 171, 192, 257, 503, 517, 526 PSFIND 2043VARS i (1) P SF 237, 237, 240, 240, 242, 242, 244 RECIND 2043VARS i (1 ) record 315, 315, 316, 316, 317 REMIND 2043VARS i (1 ) remote 219, 219, 229, 240, 452, 452, 453, 453, 454 RESIND 2043VARS i (1 ) resources 37, 78, 78, 187, 187, 190, 240 REXXIND 2043VARS i (1) REXX 369, 369, 37[...]

/XRL/18 i (1) changes between VSE and OS/390 24, 24, 25, 25, 25, 25 C020005 2043VARS i (1 ) approaches to migration 27, 27, 27, 28, 29, 29, 29, 30, 30 C020006 2043VARS i (1 ) education 31, 31, 31, 31, 31 C020007 2043VARS i (1 ) scope of work challenges 32, 33, 33, 35, 37, 37 C020009 2043VARS i (1 ) OS/390 documentation resources 39, 40, 40 C030001 [...]

/XRL/19 D040007 2043CH04 76 (1) JCL differences (VSE and MVS) ( 2) operator intervention 76, 76, 77, 77 D040008 2043CH04 78 (1) JCL differences (VSE and MVS) (2 ) resource allocation 78 D040009 2043CH04 78 (1) JCL differences (VSE and MVS) (2 ) hidden JCL 78, 79, 79, 79 D040012 2043CH04 81 (1) JCL differences (VSE and MVS) (2 ) JCL partition depend[...]

/XRL/20 D080011 2043CH08 18 1 (1 ) SQL/DS to DB2 (2 ) other comparison areas 181, 182, 182, 182, 182 D090001 2043CH09 1 8 6 (1 ) ACF/VTAM (2 ) product installation 186 D090002 2043CH09 1 8 7 (1 ) ACF/VTAM (2 ) resource definition and operation 190, 190 D090003 2043CH09 1 9 0 (1 ) ACF/VTAM (2 ) customization and programming 190, 191 D090011 2043CH09[...]

/XRL/21 D100016 2043CH10 23 0 (1 ) POWER/JES2 detailed comparisons (2 ) exit comparisons 231, 231 D100017 2043CH10 23 1 (1 ) POWER/JES2 detailed comparisons (2 ) POWER/JES2 command equivalences 232, 232, 233, 233, 233, 234, 234 D110001 2043CH11 2 35 (1 ) introducing PSF/MVS (2 ) functional comparison 235, 235, 235 D110003 2043CH11 2 36 (1) installi[...]

/XRL/22 D150009 2043CH15 3 36 (1 ) PL/I compiler options (2 ) options specific to MVS compiler 336, 336, 336, 336, 337, 337, 337, 337 D150010 2043CH15 3 37 (1 ) PL/I compiler options (2 ) execution options 337, 337, 337, 338 D150014 2043CH15 3 39 (1) ENVIRONMENT attributes (2 ) unsupported in MVS 339, 339, 339, 339, 339, 339, 339, 339, 339, 340 D15[...]

/XRL/23 4 5 2 (1 ) managing remote operations (2 ) JES2 RJE operations 452, 452, 453, 453, 453 D280018 2043CH28 4 5 3 (1 ) managing remote operations (2 ) NJE operations 454, 454 D310005 2043CH31 4 7 6 ( 1) DFSMS/MVS diagnosis (2 ) DFSMSdfp 476, 476, 477 D320003 2043CH32 4 8 4 (1 ) conversion process ( 2 ) recommendations 484, 484, 484, 484, 485, 4[...]

/XRL/24 5 2 9 (1 ) customer migration example ( 2 ) environment 529, 529, 530, 530 D340002 2043CH34 5 3 1 (1 ) customer migration example ( 2) duration 531, 531 List Items id File Page References TSK1 2043CH02 26 1 26 TSK2 2043CH02 26 2 26 TSK3 2043CH02 26 3 26 TSK4 2043CH02 26 4 26 TSK5 2043CH02 27 5 26 TSK6 2043CH02 27 6 26 TSK7 2043CH02 27 7 26 [...]

/XRL/25 86 7 OSJCL 2043CH04 88 8 POWJECL 2043CH04 89 9 J2JE CL 2043CH04 90 10 89 JESIN 2043CH10 212 11 JSCHED 2043CH10 213 12 OUTSERV 2043CH10 215 13 FC B 2043CH10 217 14 TSOFUNC 2043CH10 219 15 TABC161 2043CH10 224 16 PMACS 2043CH10 226 17 211 PLINE 2043CH10 228 18 219, 221 PRMTB 2043CH10 228 19 220 PRMTS 2043CH10 229 20 220 PNODE 2043CH10 230 21 [...]

/XRL/26 358 OPTRC1 2043CH17 363 42 363 OPTRC4 2043CH17 363 43 363 CICOPT 2043CH17 367 44 367 TABDLY 2043CH25 403 45 432 VENPS 2043AX02 539 46 Schedules id File Page References JMPFSUM 2043CH03 56 56 JMPFDET 2043CH03 60 58 Processing Options Runtime values: Document fileid .............................................................................[...]

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