IBM OS/390 manual Approaches to Migration Disclaimer, Kernel/Progressive Approach

Page 51

5.Security

6.Performance

7.Capacity Planning

8.Testing

9.Backup/Recovery

10.Disaster Planning

11.Project Plan Development

2.5Approaches 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, but they include:

Mass migration provides a project duration that is definable. This allows for a more accurate migration project cost estimation and sizing.

In today¢s integrated I/T environments it is more difficult to define discrete kernels. For example, many applications currently have integrated facilities that support the integrated nature of many business functions. This can be found in applications such as Enterprise Resource Planning (ERP). The sales forecasting function, for example, shares information with certain accounting functions. This makes it difficult to separate or define discrete kernels to migrate.

2.5.2 OS/390 Conversion and Production Implementation Strategies

There are two different strategies (or approaches) you can use in migrating applications to OS/390. They are: (1.) the kernel/progressive approach, and (2.) the single switchover - mass application migration approach. The decision as to which approach to take will have a definite impact on the project, particularly on the manner in which resources are deployed Additionally, the approach decision will, in most cases, have the greatest impact on sizing the project. The following discussion presents these two approaches.

2.5.2.1 Kernel/Progressive Approach

Here, an installation defines discrete application sets called kernels 2. The conversion team uses progressive conversions of each defined kernel, placing a converted kernel into OS/390 production on a ²when ready,² serial basis. After a kernel is cutover3 to OS/390 production, the next defined kernel is worked on, converted, and implemented on OS/390. This process goes on until all applications (kernels) are cutover to the OS/390 environment. Some points to make about the ²kernel approach²:

2A kernel is usually defined as all the programs and files that are needed to support a business application; for example, the payroll system.

3 ²Cutover² is a term generally associated with the kernel approach. It is a word used to describe the completed conversion of a kernel to OS/390; that is, the time when the kernel is placed in OS/390 production.

Chapter 2. Sizing the Effort

27

Image 51
Contents VSE to OS/390 Migration Workbook Page October VSE to OS/390 Migration WorkbookTake Note First Edition OctoberContents Job Control Language JCL Differences and Considerations Key Documents and Other ReferencesOperating System Implementations Disk and Tape Storage Considerations162 Defining MQSeries Object and Operating Advanced Function Printing and Print Services Facility/MVSPart 3. Converting VSE Languages to OS/390 Languages Data Division File Description FDVSE/ESA Egcs VSE to Dbcs OS Version 2 Comments 349 Prepare the Migration Environment Part 5. Setting Up the Migration EnvironmentPart 4. Converting VSE Utilities to OS/390 Utilities VSE/Fast Copy and OS/390 DFSMSdssOrientation to OS/390 Console Operation Orienting Iccf Users to TSO/ISPFSystems Management Philosophy and Methodology Understanding Message Formats and Replies495 Appendix B. Mapping ISV Products and Functions 591 Appendix E. Related Publications565 List of Abbreviations 583Xvii FiguresLoading a Random Preformatted DAM File under VSE Xix TablesXx VSE to OS/390 Migration Workbook Preface Team That Wrote This RedbookRedbook Builders and Key Contributors Authors and Significant Contributors Comments WelcomeHttp//w3.itso.ibm.com Part 1. Planning the Migration An Introduction VSE to OS/390 Migration Workbook System Programmers Read the following Why Customers MigrateSynopsis of This Book What do I need to read?Business Consolidation Traditional Reasons for MigratingMergers/Acquisitions Capacity ConstraintsVirtual Storage Supervisor CicsUnused Cics TORProd C1 Y1 SVA 24- Bit Static Dynamic Partitions SVA 31-Bit 16MB VSEACF VSE VtamMVS Nucleus ImageWay Processor Support Task QuantityFunctional Reasons for Migrating to OS/390 Applications AvailabilitySystems Management Systems Availability ConnectivityStaff Availability Sizing the Effort Introduction to SizingDefining the Migration Project Objectives Batch and Online Program Conversion Areas of VSE and OS/390 DifferencesSource Programs Source Program InventoryFiles Job Control LanguageErep Mshp SMP/E Comparison of Basic VSE Functions & Components to OS/390Operations Iocp IOCP, HCDRPG LE/VSE LE/MVSA S M Cobol PL/IComparison of VSE Functions & Components to OS/390 OS/390 Components/Products/SubsystemsOS/390 Operating Environment 1.1 OS/390 Product ContentLAN Services Distributed Computing ServicesNetwork Computing Services Unix System ServicesMVS Subsystem and Component Terminology ∙ Systems Management Facility SMF ∙ Interactive Problem Control System Ipcs∙ Data Facility Storage Management Subsystem ∙ Systems Resources Manager SRMSupporting Products Security Subsystem Level Comparison/AffinityWhat Changes Between VSE and OS/390? Philosophical ChangesManagement Disciplines AutomationConsole Operator Interface JCL ProcessingActivities Who′ s Normal Activities are Affected?Roles Activities Kernel/Progressive Approach Approaches to Migration DisclaimerSingle Switchover Mass Application Migration Approach 3 VM/ESA Guest Support in Your VSE to OS/390 Migration Staffing StrategiesIn-House Staff Conversion Tools Outside ConsultantsCAP-GEMINI Educational Requirements Introduction System ProgrammingApplication Programming Application Inventory Scope of Work and ChallengesJCL Conversion Program ConversionVSE to OS/390 Migration Workbook File Migration VSE to OS/390 Migration Workbook Automated Operations Project ManagementCost Considerations Introduction References OS/390 Documentation ResourcesWeb URL Key Documents and Other ReferencesProject Management Developing the PlanOverview References RecommendationsConversion Method Two Phase ApproachTake Advantage Of Conversion Tools and Automation Migration Plan Guide and OutlineProject Staffing LibrarianMigration Responsibilities Migration Assignments Team Plan Components ApproachSystems Programmers Project ManagerApplications Programmers TasksMilestone Events Progressive versus Mass Conversion Approach Differences EducationOperations Support Staffing Historical PerspectiveShared Application Files and Databases Shared Application CodeStandardized Conversion Deliverables and Automation Risk ManagementComplexity of Implementation RPG Mass Migration as a Conversion MethodMass Migration Used as a Conversion Tool CobolPlan Examples Month Number Month Initial Project ScheduleEstimated Project Schedule Estimated Schedule for CNV ResponsibilitiesSER Responsibilities Estimated Schedule for ABC ResponsibilitiesEstimated Schedule for SER Responsibilities ABC ResponsibilitiesProject Plan Example Project Plan SummaryTask Name Projected Actual Start End 1998 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Task NameProject Plan Details PCL Task Name Projected Actual Start End 1998 Jan Feb Apr Jun Jul Aug Sep Oct Task IDTask ID Conversion Software Install Batch File Migration Procedures JCL VSE to OS/390 Migration Workbook Copyright IBM Corp VSE to OS/390 Migration Workbook Philosophy of JCL in System/390 Job Control Language JCL Differences and Considerations2 OS/390′s Job Control Philosophy 1 VSE/ESA′s Job Control Language PhilosophyJob Control Language JCL Differences and Considerations JCL Statement and Job Layout High Level SimilaritiesSpooling JCL Differences Between VSE and MVSJob Input VSE Example Multiple Instream Data Set Input$$ EOJ Data Driven Segmentation of OutputJCL Parameter Handling $$ LST CLASS=J,DEST=DANJ,DISP=HOperator Flexibility and Intervention JCL ExpansionComment Lines in the JCL Pause StatementAssgn SYS005,CUU Partition and System Standard Labels Allocation of ResourcesHidden JCL Resource Allocation at Open TimePermanent Assignments and Power Defaults Help for the Hidden JCL Problem5.3 ²Carry-Over² REPORT1 DD SYSOUT= Device Address SpecificationsAssgn SYS010,FEF SYS010 DD SYSOUT=Catalogs Partition Dependent Codes in JCLCommunication Region Date and Upsi Exec Statement VSE Job Control StatementsUpsi Job StatementDlbl and Extent Reset StatementMTC Statement Assgn StatementMVS Conditional JCL MVS Job Control StatementsDD Statement Output JCL StatementCond Parameter on the Exec Statement Comparison of VSE and MVS JCL a Summary 1 of 2. VSE Job Control Statements SummaryFunction MVS Equivalent Statement 2 of 2. VSE Job Control Statements Summary Summary of MVS JCL Statements MVS Job Control StatementsJCL Statement Purpose List Card * $$ LST Comparison of Power and JES2 Jecl a Summary2. Overview of Power Jecl Statements JeclSummary of JES2 Jecl a Table 1 of 2. JES2 Control StatementsStatement Purpose Comments 2 of 2. JES2 Control Statements VSE and MVS JCL Comparison ExampleSample VSE JCL Sample MVS JCL Myjob JOB ACCT#,′ Report by PLANT′ , CLASS=F,REGION=4MSysin DD * 01 Endicott Boeblingen Outfil BLKSIZE=4350 Sort Ended Sample VSE plus Carry-OverExtent DISKO1,0,100,500 Extent DISK14,0,600,500Exec PROGRAM2,SIZE=300K VSE to OS/390 Migration Workbook Disk and Tape Storage Considerations Access Method Similarities and Differences Access MethodsDAM or Bdam Operating System ImplementationsMiscellaneous Functions Data Set Naming Considerations VSE Considerations2 OS/390 Considerations System Managed Storage Storage and Space Management VSE ConsiderationsDisk and Tape Storage Considerations Implementing Dfsms Standard Labels Tape Similarities and Differences Volume InterchangeabilityUHL1 UHL8 VOL1 HDR1 TM Data Records TM EOV1 TMVOL1 HDR1 TM Data Records TM EOF1 TM TM VOL1Standard User Labels No LabelsNonstandard Labels Bypass Label Processing Facility in OS/390Use should be controlled VSE Without Tapemark Before Data Records OS/390 Single Data Set-Single VolumeOS/390 Single Data Set-Multiple Volumes VSE With Tapemark Before Data RecordsDasd Vtoc Processing Dasd Similarities and Differences Volume InterchangeabilityIndexed Vtoc Considerations OS/390 2 OS/390 Catalogs Vsam Differences IntroductionIntegrated Catalog Facility ICF Vsam Catalogs Part 1 of 2. Extract from WSC Flash Vsam Catalog and Cvol Support Ends in YR20003.1 OS/390 Master Catalog 3 OS/390 Catalog Management3.2 OS/390 User Catalogs LOADxx Prompt Nucleus Device Suffix FeatureDEPT2 DEPT3 DEPT4DEPT1 & Jones PayrollDo not use Jobcat or Stepcat statements in OS/390 4 OS/390 VSE/VSAM Catalog CompatibilityConverting VSE/VSAM Catalogs to OS/390 ICF Catalogs Accessing a VSE/VSAM Catalog from an OS/390 SystemAreas of Consideration − Delete IgnoreerrorVsam Functional Differences Moving a Vsam Catalog to a Different Dasd TypeNoimbed Option Shared Volume OwnershipFBA Dasd Catalog StructuresCompress New in VSE/ESA 2.2, Vsam Record Compression AMS CommandsSynchk Parameter XXL Ksds New in VSE/ESA 2.3, greater than 4GB KsdsVSE/VSAM-managed SAM Files Vsam CISIZEs and Record SizesReusable Data Sets Default ModelsNoallocation Data Sets JCL Implicit DefineVSE/VSAM BACKUP/RESTORE and VSE Fastcopy Ikqvdu Volume CleanupPartition Independent File Names Data Sharing and Integrity Ikqvchk Catalog CheckSpace Classes OS/390 Vsam Integrity Provided by Cross-Region Shareoptions Cross-Region Sharing Single CPU EnvironmentOS/390 Vsam Cross-Region SHR4 Single Region Data Set Sharing Single ACB Open Multiple String ProcessingIntra-Region Data Set Name Sharing Cross-System and Dasd Sharing OS/390 Definitions for Dasd Sharing SupportOS/390 Vsam Cross-System Shareoptions Alternatives to Vsam Data Set Sharing Dasd Sharing ConsiderationsVsam Error and Reason Code Compatibility Programming Languages and Vsam SupportDfsort and Vsam Considerations VSE to OS/390 Migration Workbook Cics Overview Cics Transaction Server133 Key Prerequisites Cics TSVirtual Storage Considerations for MVS General Compatibility CommentsTOR AOR1 AOR2 Cics General System ConsiderationsAppl Data BasesCics internal security and signon table Journaling to tape serviceMacro-level programs Btam devices and controllersAccess to Cics system control blocks Cics Domains Enqueue domainKernel domain Domain Message domain Monitoring domainCics Macro Resource Definition Table Changes Cics VSE to OS/390 Migration Workbook CSD and RDO Considerations 7.1 CSDSystem initialization modifications SIMODs are obsolete CONNECTION/SECURITYNAMEMRO 7.2 RDOTYPETERM/RECOVNOTIFY Cics System Data Sets RequirementsShows MVS data sets used by Cics Collect Statistics System Programming CommandsCics System Program Interface and Exits ExitsExec Cics Return Command Exit pointsExec Cics Abend All exitsCics Upsi Cics Transaction SecurityApplication Programming Spool Interface restrictions SAA AD/Cycle COBOL/370 SAA AD/Cycle C/370 SAA AD/Cycle PL/I CICS/VSE and TS Coexistence Considerations Testing and Problem Determination ConsiderationsCics with DL/I Vendor Applications155 Iccf and TSOPreparing to Use the System User ProfilesPermit Oper Adduser Aaaa PASSWORDsecret SpecialPermit Parmlib Classtsoauth Idaaaa Accessread Permit JCLLogon Procedures Message FacilitiesSecurity Summary Using the SystemAccessing the System Descriptive Qualifier Data Set ContentsEntering and Manipulating Data Edit Payrollprtchk NEW Cobol Ready Executing Programs at a TerminalSubmitting Jobs for Batch Execution Using Command Procedures Migrating from VSE/ICCF to MVS and TSO/EConverting Iccf Libraries Sample Iccf Procedure Sysin DD Data TOP Stack 13 Quit DEL OptionsLoad Dtsprocs Save Iebupdte Edit Iebupdte NextIccf Procedures and Macros VSE to OS/390 Migration Workbook Databases DL/I and IMS/VS DB Differences Introduction169 Secondary Index for HD DB MVS System RequirementsData Base Descriptor DBD Primary Index of Hidam DB5.1 RPG Program Specification Block PSBInteractive Macro Facility IMF Command-Level Coding Hlpi Batch ProgrammingNI Status Codes Statement CompatibilityField Level Sensitivity PCB after GE StatusOperations Utilities7.4 DL/I Parameter Statement Backout Utility/Disk LoggingDatabase Portability Alternate DL/I and IMS/ESA AccessUnloading and Reloading the Database Yes Changes Utilities Operations TuningDL/I DBD Unload DB IMS GEN9 DL/I Multiple Partition Support Additional InformationEnd Users Application Developers SQL/DS Dbsu Load Database Administrators DBAsSystem Administrators SQL/DS Dbsu UNLOAD/RELOADSecurity Administrators Other Comparison AreasYear Transaction Management Data Replication and Data AccessSummary of Migration Task Drda ConsiderationsDatabases VSE to OS/390 Migration Workbook Telecommunications Subsystems 185ACF/VTAM Vtam Data Sets Product InstallationPERFORM=&PERF Resource Definition and OperationNET Proc PERF=13 Exec PGM=ISTINM01,REGION=6000K,TIME=1440,DPRTY=15,13VSE to OS/390 Migration Workbook Telecommunications Subsystems Vtam Tables Customization and ProgrammingResource Definition OperationProgramming Network ConfigurationProgram Generation ACF/NCPMigrating TCP/IP Btam Product InstallationBacklevel Hardware Support UsageNetwork Definitions User Written TCP/IP Applications 2 TCP/IP Configuration3 TCP/IP Related User Data 4 TCP/IP Batch Jobs5.4 TCP/IP Applications using the LE/VSE C Socket API 5.1 TCP/IP Applications using the Sockets API for Assembler5.2 TCP/IP Applications using the Preprocessor API 5.3 TCP/IP Applications using the BSD/C SocketsBibliography MQSeriesOS/390 Prerequisites MQSeries in Your Operating System EnvironmentTelecommunications Subsystems PL/I Installation and CustomizationCics Considerations Data Sets Defining MQSeries Object and Operating Networking DefinitionsVSE to OS/390 Migration Workbook MQSeries-based Applications SC33-0807 Keep Disposition for Pre-Execution Jobs Power and JES210.1 JES2 Introduction Major DifferencesSeparator Page Difference Printer Forms Alignment via PsetupTime Event Scheduling for Jobs Tape SpoolingFCB Incompatibilities Setting Up the Required ResourcesImplementing JES2 End-of-page Sensing10.2.1.1 JES2 Checkpoint 10.2.1.2 JES2 Spool VolumesPower JES2 Starting JES2Tailoring JES2 10.3 JES2-POWER Functional ComparisonInput From Input ServiceJES2 Input Sources compared to Power Multiple System SupportOS/390 Solution Job SchedulingJob Stream Disposition Serializing Job Execution Time Event SchedulingAdditional Job Scheduling Functions with MVS/JES2 Output Service 1 of 2. POWER/JES2 Output Service ComparisonOutput Service NEWPAGE=1 2 of 2. POWER/JES2 Output Service ComparisonPrinters Supported Output SegmentationFCB Prefixes Separator Page DifferencesOutput Disposition FCB Naming DifferencesFCB Specification Interactive User Interfaces ICCF/CMS/TSOUCS Naming Conventions Interactive Remote Job EntryFunctional RJE Differences Remote Workstation DefinitionsNetwork Job Entry RJE OperationsRJE Exits Application Interfaces Job Information Services Output RetrievalOther Interfaces Accounting Comparisons Job AccountingJES2 SMF Accounting Records Accounting Records for NJE Activities RAS CharacteristicsNJE Activity VSE/POWER Account MVS/JES2 SMF Record NJE AccountingEquivalent JES2 Parms for Power Macro 10.3.11 JES2 Testing TechniquesPOWER/JES2 Detailed Comparisons Mapping Power Parameters to JES2 Init Parms1 of 2. Power Macro to JES2 Parameter Mapping Pline Mapping to JES2 Line Parameters for RJE and NJE 2 of 2. Power Macro to JES2 Parameter MappingDefine BSC Remotes Pline Macro to JES2 Parameter Mapping1 of 2. Prmt Macro to JES2 Parameter Mapping Define SNA Remote Workstations 2 of 2. Prmt Macro to JES2 Parameter MappingPrmt Macro to JES2 Parameter Mapping Pnode Macro to JES2 Parameter Mapping Exit ComparisonsDefine NJE Nodes Define Compaction TablesJES2 Patching Facility POWER-JES2 Command EquivalencesPower Exit to JES2 Exits Source Code ModificationsCommand Short Code Form Verb Task Management CommandsNetwork Management NJE Operator CommandsSending Commands and Messages Sending Commands and Messages2 of 2. Network Management Commands File Control CommandsMigration Effort Advanced Function Printing and Print Services Facility/MVSIntroducing PSF/MVS Functional Comparison between PSF/VSE and PSF/MVSAttachment Options Installing and Configuring PSF/MVSDefining Channel-attached Printers to MVS Defining Network PrintersPSF Startup Procedures Defining Printers for PSF Printing11.2.2.2 TCP/IP Attached Printers Comparison of Printdev Statement Parameters FSS Procedure and Printdev StatementsPrintdev Parameter Comparison Defining Resources Setting up AFP ResourcesMigrating Resources from VSE to OS/390 Remote-Resident ResourcesPrinting from TSO Transferring Print Streams VSE and OS/390 CoexistenceMigrating Print Applications JCL and Jecl DifferencesHigh Level Language Programming Interfaces Command ComparisonUnderstanding Operational Differences Starting and Stopping PSFInstallation Exits 2 of 2. VSE OS/390 Command ComparisonOther Differences Performance Redbooks AccountingReferences 11.6.1 PSF/VSE Publications 11.6.2 PSF/MVS PublicationsInternet Locations ServicesVSE to OS/390 Migration Workbook 247 Part 3. Converting VSE Languages to OS/390 LanguagesVSE to OS/390 Migration Workbook Cobol General Comments on Cobol for OS/390 and VM249 Comparison of IBM Cobol Compilers VSE to OS/390 Migration ConsiderationsDOS/VS Cobol Outdd Migrating Object CodeUseful Publications DeckConverting from DOS/VS Cobol 12.3.1 DOS/VS Cobol Cics ProgramsUseful Cobol Publications Common Cobol Coding Problems PRIMARY-FIELD PICFIELD1 Values are 60 61 FIELD2 Values are 50 51 Move 0 to RETURN-CODE RECORD-AFiller Redefines RECORD-A RECA-FIRST PIC RECA-SECNDUPSI-0 Is CBL232B on Status is CBL232-BASE UPSI-1 Configuration Section SPECIAL-NAMES ParagraphSPECIAL-NAMES Sysin Is ACCEPT-SYSINClose Statement for Tapes Procedure Division Input/OutputAssign Clause Linage Clause and END-OF-PAGE PhraseExit Program Goback Stop RUN File Handling ConsiderationsProgram Termination File Status CodesIsam PROCEDURE-POINTER FunctionConverting from VS Cobol File Attribute MismatchesVsam VS Cobol II Cics ProgramsConverting from Cobol for VSE/ESA Some Conversion Considerations for all VSE Cobol Compilers12.8.1 RES/NORES Compiler OptionsCompiler Option Considerations for VS Cobol Pgmnamecompat RmodeautoWordnooo Flagsaa Reserved WordsReserved Word Considerations for DOS/VS Cobol FDUMP/NOFDUMPCbltitle EMI PrintingFUNCTIONPROCEDURE-POINTER Reserved Word Considerations for VS Cobol II and Cobol forCompiling and Running Your Converted Cobol Programs VSE to OS/390 Migration Workbook 267 AssemblerAssembler Products General Assembler Conversion CommentsMVS Register Conventions System Interface and MacrosInitiation TerminationRegister Conventions Application Program Logic LA 13,SAVEA LA 13,SAVEB Call Progb Call ProgcSave Areas Savea DC Proga Start Progb Csect Progc Csect MVS11,SAVEA 11,SAVEB 11,SAVEC Call Progb Call ProgcCall SUBRTN1 Larex Csect UsingVSE Call MVS CallCaller′ s save area 1213 Restore the registers1213,X′ FF′ Set return indicators Return 13,413 Get backward chain pointerCommunication Region User Program Communication Bytes Upsi User Program Switch IndicatorsProblem Program Area Addresses Job NameCommunications Region Simulation Call Load the phaseProgb 15,1 Pass addressCdload VSE PhasenmEPLOC=PHASENM EP=PROGBTime DEC,OUTAREA,DATETYPE=YYYYMMDD,LINKAGE=SYSTEM VSE Standard HM MS S MVS DECVSE Binary MVS BINVSE Jdump DumpMVS Abend Dump ,STEP MVS ENQ MF=E,DTL1 VSE Cancel ALL MVS AbendVSE Lock DTL1 Unlock DTL1′ S′ Resar addressEnd address Poiner VSE ChkptATTACH/DETACH Macros Multitasking MacrosEntrypoint Cb locaion addressWAIT/POST Macros Ecb1,ecb2 VSE Wait LisnameNumber of evens,ECB = address ECBLIST=address System Systems 13.2.2.3 RCB/ENQ/DEQ MacrosSystem Step SystemsInterrupt Handling Routines Interval Timer InterruptsExit VSE Ttimer Cancel MVS Ttimer Cancel ,TUOperator Communication Interrupts Tecb SetimeGetvis and Freevis Macros Virtual Storage MacrosVsam Macros Exlst Macro and Excpad Routines RPL Macro Additional MVS Parameters∙ M a C R F = MVS Vsam Check Macro Vsam Error and Reason Code CompatibilityData Management Macros Showcb MacroList and Execute Macro Forms Definition of BlksizeIoreg Liocs Card File Definition 13.2.6.4 I/O Error CheckingASA Mode = E O Devd = ..,MODE=E OBufno = Ctlchr = YESCard File Programs in VSE and MVS Liocs Printer File DefinitionCntrl Macro Prtov MacroSepasmb = YES Liocs Tape File DefinitionControl = YES Macrf = PC Ctlchr = YES Printov = YESReread Leave Rewind Disp Close MacroFSR, number of blocks VSE MVS Bsam onlyNo equivalen. The opion specified in he Disp BSR, number of blocksPoints Macro Relse MacroTrunc Macro GET / PUT Macros Feov MacroMACRF=RP,WP SkipOptcd = Q Eropt = ACC SKP ABELiocs Device-independent File Definition Open Tape VSE PUT Close TapeClose TAPE,LEAVE Recfm = FA Liocs Sequential File Definition on Direct Access DevicesLiocs Console File Definition Erropi = Ignore Eropi = ACC Skip SKP ABEReread Leave Free Disp Qsam InputOutput Leave Updat Disp Extend Input Bsam Inout Disp Updat Leave Outin OutinxEret Macro Check Macro Read MacroWrite Macro WriteFilename Address Feovd Macro Optcd = W Errext = YES Feovd = YES Hold = YESWORKA= YES Eropt = ACCLiocs Direct Access File Definition General ConsiderationsSequential Dasd File Program in VSE and MVS Readkey = YES After = YESErrext = YES Readid = YESVSE Error Bytes and MVS Exception Code Bits Error VSE MVSWAITF, Open and Close Macros Record Addressing by ID Track and Record AddressingTrack Addressing Record AddressingRecord Addressing by KEY Reference MethodsRecord Reference by ID Reference Method Record Reference by KEYReference Direct Access File ProcessingDCB DSORG=DA,MACRF=RISC,WIC OPTCD=R,BUFL=58Open DAMFILE,TAPE WRITER0 Open DAMFILE,OUTPUTDecbadd Damfile DCB MACRF=WICS,DSORG=DA,OPTCD=RLoading a Sequential DAM File under MVS Specified in the DD statementOpen DAMFILE,UPDAT,TAPE,INPUT DCBOpen DAMFILE,OUTPUT CLI Open R0FILE,OUTPUT,TAPE WRITER0DECBR0,SZ,R0FILE STC DECBR0 CLIDCB=DSORG=DA DISP=,KEEP GO.DAMDD DD DSN=UDAM CountThree DISP=OLD DCB=BLKSIZE=50,RECFM=F GO.R0DD DD DSN=UDAMLoading a DAM File Undefined or Variable-Length Records Loading a DAM File Fixed-Length Records without keysProcessing a DAM File under VSE Open Damfile Read DAMFILE,KEYDamfile Addition Write DAMFILE,AFTER AFTER=YES,ERREXT=YES,RELTRK=YESLoading a Random Preformatted DAM File under VSE Multiple Search / FeedbackType or Reference Liocs Indexed Sequential DefinitionPiocs Overview of Programming ElementsCCB Macro Dtfph Macro Comparison of Physical Iocs ElementsPrint Files RPGMigration from VSE to OS/390 Device InformationProcessing Options File Access MethodsTape Labels Extent ExitYear Direct access method files are processed with BdamCalling Cobol Subprograms Calling PL/I SubprogramsVSE to OS/390 Migration Workbook 333 PL/IFile Organization Extended PrecisionMultitasking Dynamic Loading of Dependent ProgramsCatalog Parameters Passed to a Main Program15.1.7 %INCLUDE Compiler Options Options Specific to the DOS CompilerOptions Specific to the MVS Compiler Execution Options Environment Attributes Exec and Process CardsLinkages Between Languages Linkages Supported Linkages not SupportedNot Supported in MVS Calling Sort from PL/I Interfaces Offered Supported but to be Avoided²TOTAL² Option SIS Option Sequential Insert StrategyReturn Code Sort FieldsRecord StorageIf ONCODE= xxx then do Checkpoint-Restart in PL/I PlickptPlirest Call Plickpt pl,p2,p3,p4 DOS and MVS² File Plidump could not be Opened Ddname MISSING² PlicancDump in PL/I Optimizer Output File Options Specific to DOSReturn Code Values Return Codes in PL/I Setting Return CodesOptions Specific to MVS CompatibilityOverlay in MVS Automatic RestartOverlay Structures Conversion15.12.6 PL/I-CICS/VS Transaction Abend Codes 15.12 PL/I and Cics File SupportStatements not Supported CALLing DumpPL/I VSE to OS/390 Migration Workbook 349 FortranVS Fortran in OS/390 Fortran Conversion ConsiderationsVSE to OS/390 Migration Workbook 351 Language Environment LEGeneral Comments on Language Environment Few Words about Cobol and PL/I17.2.1 LE/VSE-conforming Languages Migrating from LE/VSE-Conforming Languages For VSE/ESAUseful Publications Options Mapping Cobol for VSE/ESA17.3.3 PL/I for VSE/ESA Migrating from Non-LE/VSE Run-time Environments370 Migration Considerations 17.4.2 C/370VS Cobol Report and Isasize Options, C/370 and DOS PL/IDOS PL/I VS Cobol II Migration ConsiderationsDOS/VS Cobol Migration Considerations Depthcondlmt Default setting for the Depthcondlmt option, both forDOS PL/I Migration Considerations Migration Comments ConsiderationDOS PL/I Migrating Interlanguage Communications Applications1 of 2. ILC Migration Considerations To Migrate You Need To2 of 2. ILC Migration Considerations Migrating Assembler ApplicationsMigrating from LE/VSE Run-time OptionsSyslst Shh Ihh UddddCblqda Flow Interrupt Simvrd Vctrsave Run-time Options and LE/VSEArgparse Run-time Options and LE/VSE 1.4 and Later ReleasesRecommended Settings for Options Language EnvironmentLanguage Option Recommendation Ceecxita Cics User Exits and Abnormal Termination ExitsAssembler User Exits High-Level Language ExitsAbnormal Termination Exits Callable Services and Math ServicesCeetdli 17.5.4 LE/VSE 1.4 LocalesCics Cobol and CicsUser Exits and Abnormal Termination Exits VSE to OS/390 Migration Workbook Rexx and TSO/E Procedure Language RexxRexx and VM/ESA Rexx and VSE/ESA18.4.2 VM/ESA Environment PowerEnvironments 18.4.1 VSE/ESA EnvironmentRexx Migration Issues18.4.3 TSO/E Environment Rexx Exec Sample for the OS/2, TSO and CMS EnvironmentsRexx Bibliography Rexx and SAA373 Part 4. Converting VSE Utilities to OS/390 UtilitiesVSE to OS/390 Migration Workbook Sort JCL Statements375 VSE to OS/390 Migration Workbook Control Statements VSE to OS/390 Migration Workbook Additional DFSORT/VSE Migration Considerations Icetool MVS/ESA VSE/ESA VM/ESA DittoCompatibility with Previous Releases of Ditto 381Ditto Functions that are No Longer Supported Function Description ReplacementDitto Functions that are Not Recommended Function Synonyms Description Functions Keyword Description ReplacementDitto Function Code Synonyms Batch Keywords that are No Longer SupportedDITTO/ESA Security Batch Keywords that are Not RecommendedVSE to OS/390 Migration Workbook 21.1.2 VSE/VSAM Backup/Restore Vsam Backup/RestoreVsam Backup/Restore 21.1.1 OS/390 Vsam Backup/RestoreVSE to OS/390 Migration Workbook Librarian Overall Library Support389 ∙ Interactive usage 22.1.1 OS/390 Ispf Overview22.1.2 OS/390 Library Management VSE to OS/390 Migration Workbook 23.3 OS/390 Hardcopy Processing LISTLOG/PRINTLOG Printing Log StreamsVSE Printlog Utility VSE Listlog Utility ProgramSyslog Printing SyslogPrinting Operlog 23.5 JES2 System Data Sets Job Log and System Messages Systems Management RecordingPrinting SMF Records VSE to OS/390 Migration Workbook VSE/Fast Copy and OS/390 DFSMSdss 24.1 VSE/Fast Copy Online and Stand-Alone397 ∙ Release ∙ DUMP/RESTOREDFSMSdss OS/390 Component ∙ Compress399 Part 5. Setting Up the Migration EnvironmentVSE to OS/390 Migration Workbook 401 Prepare the Migration EnvironmentDasd Requirements Install and Configure Required HardwareProcessor Requirements Devices Supported by OS/390403 Other Hardware RequirementsTape Drives Terminal AccessInter-Systems Connectivity Shared DasdData Transfer and NJE Order and Install the OS/390 SoftwareFee-based Methods of Installing OS/390 SoftwareXcel Installation Express SIEServerPac Entitled Methods of Installing OS/390SoftwareXcel SystemPac/MVS Other OfferingsData Management Standards Set Up Standards, Procedures, and DocumentationInstallation Standards CbpdoData Sets Dasd and Tape Volume SerialsMVS Naming Standards Related RedbooksOther MVS Names Systems Management ProceduresJCL Standards 409Backing Up Your System Enforcing Installation StandardsCreating an Emergency Backup System Implementing System Security411 Setting Up Critical Operations ProceduresManaging Problems Managing ChangePrinting Softcopy Books DocumentationYour Hardcopy Library Your Softcopy LibraryCustomize Your New OS/390 System Verifying the New OS/390 System413 Providing Terminal Access to the OS/390 System Applying Preventive Service25.5.2.1 SYS1.PARMLIB Parameters NetView FTP AccessMVS BCP Customization Providing NJE Connection to the OS/390 SystemBase Elements for Release Optional Features for ReleaseOther OS/390 Elements Tailoring Other Components417 Independent Software Vendor ProductsVSE to OS/390 Migration Workbook 419 Differences in Testing ²Philosophy²Test Environments TerminologyApplication Program, JCL, and Data Conversion Production Maintenance Backup Sand-boxTest Systems in the Life of the Migration Application Development & Test SystemOS/390 Production Stand-By Maintenance OS/390 VSE Backup Production Maintenance26.3 VM, LPAR, or Standalone Systems Logical Partitioning Software Partitioning Our Recommendation New Users of VM System Simulation Advantages of Guest Support in VM/ESAReduced Hardware and Migration Cost Performance BenefitsInteractive Computing, Application Development and Support Recovery ManagementAccess to VM/ESA CMS Applications Operations ManagementMultiple 3270 Session Support Use of CMSDB2 Guest Sharing Models 3 and 6 Fast Write Transparency26.3.3.5 OS/390 Guest Considerations Parallel ActivitiesSynchronizing VSE Applications with OS/390 Versions Building the Initial OS/390 Test System26.5.1 OS/390 Maintenance Environment 26.5.2 OS/390 Test Logical PartitionMaintaining Your OS/390 Libraries and SMP/E Zones Shared Dasd between OS/390 Test Systems vs. Cloned Dasd Shared Dasd vs. Cloned DasdShared Dasd between VSE and OS/390 vs. Cloned Dasd VSE to OS/390 Migration Workbook 435 Part 6. Running Your OS/390 SystemVSE to OS/390 Migration Workbook Orienting Iccf Users to TSO/ISPF 27.1 TSO/ISPF and Sdsf437 Editing Data Sets Submitting Jobs Using Ispf UtilitiesManaging Projects Creating and Executing Ispf ApplicationsUsing Sdsf for Operators Tracking JobsRetrieving Output VSE to OS/390 Migration Workbook 443 Orientation to OS/390 Console OperationOperating Hardware Consoles Understanding the Operator InterfacesDEL=R,SEG=28,CON=N,RNUM=14,RTME=001,MFORM=T,J Controlling ConsolesManaging Display Consoles Console ModesPFKeys Using the TSO/E FunctionsExtended MCS Consoles Display AreasUnderstanding Message Formats and Replies Using Sdsf for System OperationControlling the OS/390 System Starting the SystemDisplaying System Status Understanding Device Allocation Stopping the SystemControlling Devices Displaying the Status of DevicesDisplaying Work on Your System 28.4.3 JES2 DevicesSdsf Device Panels Controlling TSO Users, Jobs and Started TasksRMF and Other Monitors MVS Commands28.5.1.2 JES2 Commands Sdsf PanelsControlling Time Sharing Users Controlling Batch JobsControlling Started Tasks Remote Workstation Operations Managing Remote Operations28.6.1 JES2 RJE Operations Host OperationsRemotes Without Consoles Using Sdsf Panels for RJECommand Authority for Remote Operators NJE Operations$D MNn,′Please drain your session′ Using Sdsf Panels for NJE$D PATHnodename $D Nxx.′$D NODEyy′Orientation for Utilities IEBxxx or IEHxxx455 DFSMSdss DFSMSdss Storage Administration Reference, SC26-4929457 Systems Management Philosophy and MethodologyVSE to OS/390 Migration Workbook Systems Management Scope What Needs to be Managed? Change Management Overview Role of AutomationMethodology Problem Management OverviewTasks Performance Management Overview Methodology Operations Management Overview Methodology Automating Operational Procedures Security Management Overview Configuration Management Overview Methodology Accounting Management Overview Asset Management OverviewSummary Ipcs Diagnosing System ProblemsProblem Determination Tools DumpsUsing Ipcs TracesAnalyzing Traces 31.4 JES2 Diagnosis SlipPerformance Tools DFSMSdfp Analyzing Catalogs for Errors and SynchronizationCatalog Recovery DFSMS/MVS DiagnosisDFSMShsm Checking a Vsam Ksds for Structural ErrorsDFSMSrmm Diagnostic Reference Publications479 Part 7. Converting your ApplicationsVSE to OS/390 Migration Workbook 481 Conversion Process∙ Refer to MVS MS Production Standards, LB11-8080 Conversion Process IntroductionConversion Process Prerequisites ManualsSecure OS/390 Skills Migrate the SNA Network Early 32.1.3.6 24x7 InstallationsAssumptions Mass Conversion Overview / Benefits Repetitive Conversion Automated ConversionMass Conversion Switchover Mass Conversion ToolsAutomation Limits INT File Integration Automated Conversion ProcessCortex MS DMT DOS/OS/390 TranslatorENV Environment Switch SwitchoverEZ-PCL Easy PCL Prep PreparationFile Transfer Inventory ValidationTranslate the Languages/Programs JCL Conversion ToolsPreparation Phases Mass Conversion Phase OverviewPhase 0 Project Management and Technical Leadership Project Planning and Orientation∙ Implement System Managed Storage Dfsms Phase 1 Application Inventory Supply Analysis and Resolution of ExceptionsDetermination Collection32.4.3 OS/390 Standards and Naming Conventions VSE to OS/390 Migration Workbook Phase 2 Conversion Specifications Analyze the VSE Source Material Phase 3 Customization or Development of Conversion Tools Design the MVS Target OutputDetermine the Method to Get from Source to Target Manual OS/390 Conversion VSE PositioningProgram Conversion Considerations Conversion PhasesCommon VSE Coding Practices Causing Conversion Problems Phase 4 Initial Trial Conversion Phases of testing Objectives of testingRecommendations Testing PrioritiesPersonnel Involvement in Testing ResponsibilitiesSubsystem Storage Protect MVS Tools TestingTest Plan Dasd RequirementsConversion Process 32.5.4.4 OS/390 Automated Operations Tools Unit Testing Initialization TestingTiming between Online and Batch Testing Online Unit TestingBatch Unit Testing Data Migration in Unit TestingSystem Testing OnlineBatch Parallel/Production Simulation Testing Data Migration in System TestingData Migration in Parallel Testing Implementation Phases Date Concerns during Parallel TestingJob Simulation Phase 6 Actual Conversion and Switchover Converting the Development MaterialFinal JCL Conversion Switchover Final Program ConversionData/File Migration Additional Switchover Tasks Phase 7 Initial OS/390 Operations519 Conversion Services and ToolsConversion Services IBM Global Services Automated Migration Services AMSIBM OPTI-AUDIT for VSE Conversion Tools 33.2.1 VSE/ESA FacilitiesProduct Details Product HighlightsIBM Cobol and Cics Command Level Conversion Aid Ccca Technical Description Product PositioningSisro CORTEX-Migration System CORTEX-MS CA-DUO Source Recovery CompanyComputer Associates CA-ConvertorReconcile/SRC Recovery/SRCCobol Recovery Example Rename/SRC527 Part 8. Migration ExperienceVSE to OS/390 Migration Workbook Hardware Customer Migration ExampleBackground EnvironmentResources InventoryPhase One Phase TwoDuration Benefits 533 Part 9. AppendixesVSE to OS/390 Migration Workbook 535 Appendix A. Education InformationWhen are Courses Scheduled and When are they Needed? Custom ClassesOEM Product Education Who will Provide the Training? Where will the Training Take Place?VSE to OS/390 Migration Workbook 539 Appendix B. Mapping ISV Products and FunctionsIBM Software Migration Project Office Smpo VSE ISV System Management Products and OS/390 ComparedIdms Appendix B. Mapping ISV Products and Functions VSE to OS/390 Migration Workbook Appendix C. Dfsms Naming Conventions Data Set Naming Guidelines543 High-Level Qualifier HLQ Components of a Data Set NameAppendix C. Dfsms Naming Conventions Relative Importance File ContentsDepartment Number User NameData Set Level Things Not to Include in the Data Set NameExpiration Date Application LocationManagement Criteria Output Device TypeTSO Naming Conventions Access MethodJob Name Common Applications Naming ConventionsDSNDBx is Vsam Data Set Naming Conventions3 DB2 Naming Conventions Hlq.DSNDBx.dbname.tblspacename.I0001.A00nC.GnnnnV00 Generation Data SetsVSE to OS/390 Migration Workbook 553 Appendix D. Special NoticesAIX ACF/VTAMAdstar AFPVM/ESA VM/XA VSE/ESA Vtam Following terms are trademarks of other companiesVSE to OS/390 Migration Workbook OS/390 Product Publications Appendix E. Related PublicationsInternational Technical Support Organization Publications Other RedbooksSK2T-6700 Planning Books2 OS/390 Online Product Library Book Title Publication NumberRedbooks 1.2 OS/390 Books IBM Printing Systems Other PublicationsOther Sources Books on the Internet Redbooks on CD-ROMsVSE to OS/390 Migration Workbook How to Get Itso Redbooks How IBM Employees Can Get Itso Redbooks561 ∙ Fax Ð send orders to How Customers Can Get Itso Redbooks∙ Telephone Orders ∙ Mail Orders Ð send orders toPlease send me the following IBM Redbook Order FormVSE to OS/390 Migration Workbook 565 Glossary NumericsVSE to OS/390 Migration Workbook O s s a r y Customer Information Control System CICS. An O s s a r y VSE to OS/390 Migration Workbook File Information Management System/Virtual Storage Language/Product Days Since Dec-31 Language Environment Oct-14Interactive Computing and Control Facility ICCF. An VSE to OS/390 Migration Workbook O s s a r y Ordinal Day of Year. See Julian Date O s s a r y Rolling window. Synonymous with sliding window Resource Access Control Facility RACF. AnO s s a r y System management facilities SMF. See SMF O s s a r y Year2000 support. The ability to provide Year2000 readiness 583 List of AbbreviationsControl Volume Command ListRecovery Callable Services LibraryExternal Symbol Dictionary Data Set ServicesExtended Common Service Environmental error RecordIndexed Sequential Access Interactive Command FacilityService Facility Interactive Problem ControlSeries Power ENDQueued Sequential Access Program Specification BlockPrint Service Facility Print Service Facility/6000SYStem ADMinistrator Service Planning GuideSQL Processor Using File System Services ProgramEXtended Recovery Facility Volume Table of ContentsVsam Volume Data Set Facility Vsam Volume RecordIndex Special Characters 591ACF/VTAM Aptrmark VSE TtimerCancel Apsrmark MVSIndex Plicanc Plickpt Plirest Batch TCP/IP 195 unit testingDiagnostic reference 478 Language Environment 353 MQSeries PSF/MVSCobol CicsConversion CA-Convertor Courses locations 537 schedules 536 when needed CORTEX-MSDadsm Dasd VSE to OS/390 Migration Workbook Device Ditto Associate E15 Exit ProcedureEntrypoint Data Division File Description FDFortran FBA DasdGonumber FilesecIdcams Iebcopy Iebgener Ismf Ispf IpcsIsam IsasizeJES2 Liocs LE/VSELimsconv LinkCortex MS TCP/IP 356VS Fortran MigrationPrinting Operlog 394 Opsys routine 349 OPTI-AUDIT 79 MVS device addresses 80 DFPNJE OperlogOS/390 NCP Vtamlst 190 XCFMVS BCP Piocs PL/I PL/I Syslog 394 SMF records 395 Softcopy books 412RDO ProjectRES/NORES Racf370 Risk management Risky VSE coding practices 504 ResourcesTSO/E 371 VM/ESAIcetool RexxSort FieldsVSE to OS/390 Migration Workbook Index Btam BACKUP/RESTOREVS Cobol II VsamCompress Delete IgnoreerrorVSE/VSAM BACKUP/RESTORE & VSE OS/VS CobolVtamlst VSE Year2000Itso Redbook Evaluation 621Please answer the following questions VSE to OS/390 Migration Workbook SG24-2043-00 XRL/1 XRL/2 Jmacp XRL/3XRL/4 XRL/5 XRL/6 XRL/7 XRL/8 XRL/9 XRL/10 Dittind XRL/11XRL/12 OploindOperlog XRL/13 SmfpindACB NJE PowerXRL/14 DL/IXRL/15 XRL/16 XRL/17 XRL/18 Csysind XRL/19Vosind CtrindXRL/20 XRL/21 MVS BCP XRL/22Cortex MS XRL/23XRL/24 XRL/25 XRL/26 XRL/27
Related manuals
Manual 76 pages 7.95 Kb

OS/390 specifications

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

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

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

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

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

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

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