IBM OS/390 Comparison of VSE and MVS JCL a Summary, 1 of 2. VSE Job Control Statements Summary

Page 110

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 Job Control Statements Summary

VSE

Function

MVS Equivalent

Statement

 

 

 

 

 

ASSGN

Used at execution time to assign a

// DD UNIT=

 

specific device address to the

 

 

symbolic unit name used.

 

 

 

 

CLOSE

Closes either a system or a

No equivalent in OS/390.

 

programmer logical unit assigned to

Units closed automatically

 

tape, disk, or diskette.

at end-of-step, or by the

 

 

application program.

 

 

 

DATE

Contains a date that is put in the

No equivalent in OS/390.

 

communications region.

 

 

 

 

DLBL

Contains file label information for

// DD DSName=

 

disk or diskette label checking and

 

 

creation.

 

 

 

 

EXEC

Indicates the end of job control

// EXEC PGM= (Must

 

statements for a job step and that

precede DD statements for

 

the job step is to be executed.

the step.)

 

 

 

EXEC PROC

Calls a cataloged procedure and

// EXEC PROC= (²P R O C = ²

 

defines values for symbolic

is optional)

 

parameters.

 

 

 

 

EXTENT

Defines each area, or extent, of a

// DD VOLUME= SPACE=

 

disk file or diskette volume.

D A T A C L A S =

 

 

 

GOTO

Causes JCL to skip all following

No direct equivalent in

 

statements (except JOB, /&, /+) up

OS/390. Use CONDitional

 

to the specified label statement.

step processing or

 

 

IF/THEN/ELSE/ENDIF

 

 

 

ID

Used to specify user identification

// JOB U S E R =

 

and password.

PASSWORD=

 

 

 

IF

Causes skipping or execution of the

// IF

 

following statement dependent on

 

 

the specified condition.

 

 

 

 

JCLEXIT

Activates or deactivates one or

Not applicable in OS/390.

 

more JCL exit routines.

 

 

 

 

JOB

Indicates the beginning of control

// JOB

 

information for a job.

 

 

 

 

LIBDEF

Defines library chains.

// STEPLIB DD,

 

 

// STEPCAT DD, or

 

 

// JCLLIB

 

 

 

LIBDROP

Drops library chain definitions.

No equivalent in OS/390.

 

 

 

LIBLIST

Lists library chain definitions.

No equivalent in OS/390

 

 

 

LIBSERV

Controls 3494 tape system.

No equivalent in OS/390

 

 

 

LISTIO

Used to get a listing of I/O

No equivalent in OS/390

 

assignments on SYSLOG or SYSLST.

 

 

 

 

MTC

Controls operations on magnetic

// DD LABEL

 

tapes.

 

 

 

 

86VSE to OS/390 Migration Workbook

Page 109 Page 111
Image 110
Page 109 Page 111
Contents VSE to OS/390 Migration Workbook Page VSE to OS/390 Migration Workbook OctoberFirst Edition October Take NoteContents Key Documents and Other References Job Control Language JCL Differences and ConsiderationsDisk and Tape Storage Considerations Operating System Implementations162 Advanced Function Printing and Print Services Facility/MVS Defining MQSeries Object and OperatingVSE/ESA Part 3. Converting VSE Languages to OS/390 LanguagesData Division File Description FD Egcs VSE to Dbcs OS Version 2 Comments 349 VSE/Fast Copy and OS/390 DFSMSdss Part 5. Setting Up the Migration EnvironmentPart 4. Converting VSE Utilities to OS/390 Utilities Prepare the Migration EnvironmentOrienting Iccf Users to TSO/ISPF Orientation to OS/390 Console OperationUnderstanding Message Formats and Replies Systems Management Philosophy and Methodology495 Appendix B. Mapping ISV Products and Functions List of Abbreviations 583 Appendix E. Related Publications565 591Figures XviiLoading a Random Preformatted DAM File under VSE Tables XixXx VSE to OS/390 Migration Workbook Redbook Builders and Key Contributors PrefaceTeam That Wrote This Redbook Http//w3.itso.ibm.com Authors and Significant ContributorsComments Welcome Part 1. Planning the Migration An Introduction VSE to OS/390 Migration Workbook What do I need to read? Why Customers MigrateSynopsis of This Book System Programmers Read the followingTraditional Reasons for Migrating Business ConsolidationVirtual Storage Mergers/AcquisitionsCapacity Constraints Cics SupervisorProd UnusedCics TOR VSE Vtam Static Dynamic Partitions SVA 31-Bit 16MB VSEACF C1 Y1 SVA 24- BitTask Quantity ImageWay Processor Support MVS NucleusSystems Management Functional Reasons for Migrating to OS/390Applications Availability Connectivity Systems AvailabilityStaff Availability Defining the Migration Project Objectives Sizing the EffortIntroduction to Sizing Source Program Inventory Areas of VSE and OS/390 DifferencesSource Programs Batch and Online Program ConversionJob Control Language FilesIocp IOCP, HCD Comparison of Basic VSE Functions & Components to OS/390Operations Erep Mshp SMP/ECobol PL/I LE/VSE LE/MVSA S M RPGOS/390 Components/Products/Subsystems Comparison of VSE Functions & Components to OS/3901.1 OS/390 Product Content OS/390 Operating EnvironmentUnix System Services Distributed Computing ServicesNetwork Computing Services LAN ServicesMVS Subsystem and Component Terminology ∙ Systems Resources Manager SRM ∙ Interactive Problem Control System Ipcs∙ Data Facility Storage Management Subsystem ∙ Systems Management Facility SMFSupporting Products Philosophical Changes Subsystem Level Comparison/AffinityWhat Changes Between VSE and OS/390? SecurityJCL Processing AutomationConsole Operator Interface Management DisciplinesRoles Activities ActivitiesWho′ s Normal Activities are Affected? Approaches to Migration Disclaimer Kernel/Progressive ApproachSingle Switchover Mass Application Migration Approach In-House Staff 3 VM/ESA Guest Support in Your VSE to OS/390 MigrationStaffing Strategies CAP-GEMINI Conversion ToolsOutside Consultants Application Programming Educational Requirements IntroductionSystem Programming Scope of Work and Challenges Application InventoryProgram Conversion JCL ConversionVSE to OS/390 Migration Workbook File Migration VSE to OS/390 Migration Workbook Project Management Automated OperationsCost Considerations OS/390 Documentation Resources Introduction ReferencesKey Documents and Other References Web URLRecommendations Developing the PlanOverview References Project ManagementMigration Plan Guide and Outline Two Phase ApproachTake Advantage Of Conversion Tools and Automation Conversion MethodMigration Responsibilities Project StaffingLibrarian Migration Assignments Plan Components Approach TeamProject Manager Systems ProgrammersTasks Applications ProgrammersMilestone Events Education Progressive versus Mass Conversion Approach DifferencesShared Application Code Historical PerspectiveShared Application Files and Databases Operations Support StaffingComplexity of Implementation Standardized Conversion Deliverables and AutomationRisk Management Cobol Mass Migration as a Conversion MethodMass Migration Used as a Conversion Tool RPGPlan Examples Estimated Schedule for CNV Responsibilities Project ScheduleEstimated Project Schedule Month Number Month InitialABC Responsibilities Estimated Schedule for ABC ResponsibilitiesEstimated Schedule for SER Responsibilities SER ResponsibilitiesTask Name Projected Actual Start End Project Plan ExampleProject Plan Summary Task Name 1998 Jan Feb Mar Apr May Jun Jul Aug Sep OctProject Plan Details PCL Task Name Projected Actual Start End Task ID 1998 Jan Feb Apr Jun Jul Aug Sep OctTask ID Conversion Software Install Batch File Migration Procedures JCL VSE to OS/390 Migration Workbook Copyright IBM Corp VSE to OS/390 Migration Workbook Job Control Language JCL Differences and Considerations Philosophy of JCL in System/3901 VSE/ESA′s Job Control Language Philosophy 2 OS/390′s Job Control PhilosophyJob Control Language JCL Differences and Considerations High Level Similarities JCL Statement and Job LayoutJob Input SpoolingJCL Differences Between VSE and MVS Multiple Instream Data Set Input VSE Example$$ LST CLASS=J,DEST=DANJ,DISP=H Data Driven Segmentation of OutputJCL Parameter Handling $$ EOJJCL Expansion Operator Flexibility and InterventionAssgn SYS005,CUU Comment Lines in the JCLPause Statement Resource Allocation at Open Time Allocation of ResourcesHidden JCL Partition and System Standard Labels5.3 ²Carry-Over² Permanent Assignments and Power DefaultsHelp for the Hidden JCL Problem SYS010 DD SYSOUT= Device Address SpecificationsAssgn SYS010,FEF REPORT1 DD SYSOUT=Communication Region Date and Upsi CatalogsPartition Dependent Codes in JCL Job Statement VSE Job Control StatementsUpsi Exec StatementAssgn Statement Reset StatementMTC Statement Dlbl and ExtentOutput JCL Statement MVS Job Control StatementsDD Statement MVS Conditional JCLCond Parameter on the Exec Statement Function MVS Equivalent Statement Comparison of VSE and MVS JCL a Summary1 of 2. VSE Job Control Statements Summary 2 of 2. VSE Job Control Statements Summary JCL Statement Purpose Summary of MVS JCL StatementsMVS Job Control Statements Jecl Comparison of Power and JES2 Jecl a Summary2. Overview of Power Jecl Statements List Card * $$ LSTStatement Purpose Comments Summary of JES2 Jecl a Table1 of 2. JES2 Control Statements VSE and MVS JCL Comparison Example 2 of 2. JES2 Control StatementsSample VSE JCL Sysin DD * 01 Endicott Boeblingen Sample MVS JCLMyjob JOB ACCT#,′ Report by PLANT′ , CLASS=F,REGION=4M Extent DISK14,0,600,500 Sample VSE plus Carry-OverExtent DISKO1,0,100,500 Outfil BLKSIZE=4350 Sort EndedExec PROGRAM2,SIZE=300K VSE to OS/390 Migration Workbook Access Method Similarities and Differences Access Methods Disk and Tape Storage ConsiderationsOperating System Implementations DAM or Bdam2 OS/390 Considerations Miscellaneous FunctionsData Set Naming Considerations VSE Considerations Storage and Space Management VSE Considerations System Managed StorageDisk and Tape Storage Considerations Implementing Dfsms Tape Similarities and Differences Volume Interchangeability Standard LabelsVOL1 VOL1 HDR1 TM Data Records TM EOV1 TMVOL1 HDR1 TM Data Records TM EOF1 TM TM UHL1 UHL8No Labels Standard User LabelsUse should be controlled Nonstandard LabelsBypass Label Processing Facility in OS/390 VSE With Tapemark Before Data Records OS/390 Single Data Set-Single VolumeOS/390 Single Data Set-Multiple Volumes VSE Without Tapemark Before Data RecordsDasd Similarities and Differences Volume Interchangeability Dasd Vtoc ProcessingIndexed Vtoc Considerations OS/390 Vsam Differences Introduction 2 OS/390 CatalogsIntegrated Catalog Facility ICF Vsam Catalogs Vsam Catalog and Cvol Support Ends in YR2000 Part 1 of 2. Extract from WSC Flash3 OS/390 Catalog Management 3.1 OS/390 Master CatalogLOADxx Prompt Nucleus Device Suffix Feature 3.2 OS/390 User CatalogsPayroll DEPT4DEPT1 & Jones DEPT2 DEPT34 OS/390 VSE/VSAM Catalog Compatibility Do not use Jobcat or Stepcat statements in OS/390Accessing a VSE/VSAM Catalog from an OS/390 System Converting VSE/VSAM Catalogs to OS/390 ICF CatalogsMoving a Vsam Catalog to a Different Dasd Type − Delete IgnoreerrorVsam Functional Differences Areas of ConsiderationCatalog Structures Shared Volume OwnershipFBA Dasd Noimbed OptionXXL Ksds New in VSE/ESA 2.3, greater than 4GB Ksds AMS CommandsSynchk Parameter Compress New in VSE/ESA 2.2, Vsam Record CompressionVsam CISIZEs and Record Sizes VSE/VSAM-managed SAM FilesJCL Implicit Define Default ModelsNoallocation Data Sets Reusable Data SetsPartition Independent File Names VSE/VSAM BACKUP/RESTORE and VSE FastcopyIkqvdu Volume Cleanup Space Classes Data Sharing and IntegrityIkqvchk Catalog Check Cross-Region Sharing Single CPU Environment OS/390 Vsam Integrity Provided by Cross-Region ShareoptionsOS/390 Vsam Cross-Region SHR4 Intra-Region Data Set Name Sharing Single Region Data Set SharingSingle ACB Open Multiple String Processing OS/390 Vsam Cross-System Shareoptions Cross-System and Dasd SharingOS/390 Definitions for Dasd Sharing Support Dasd Sharing Considerations Alternatives to Vsam Data Set SharingDfsort and Vsam Considerations Vsam Error and Reason Code CompatibilityProgramming Languages and Vsam Support VSE to OS/390 Migration Workbook 133 CicsOverview Cics Transaction Server Cics TS Key PrerequisitesGeneral Compatibility Comments Virtual Storage Considerations for MVSData Bases Cics General System ConsiderationsAppl TOR AOR1 AOR2Btam devices and controllers Journaling to tape serviceMacro-level programs Cics internal security and signon tableAccess to Cics system control blocks Message domain Monitoring domain Enqueue domainKernel domain Domain Cics DomainsCics Macro Resource Definition Table Changes Cics VSE to OS/390 Migration Workbook System initialization modifications SIMODs are obsolete CSD and RDO Considerations7.1 CSD 7.2 RDO CONNECTION/SECURITYNAMEMROCics System Data Sets Requirements TYPETERM/RECOVNOTIFYShows MVS data sets used by Cics Exits System Programming CommandsCics System Program Interface and Exits Collect StatisticsAll exits Command Exit pointsExec Cics Abend Exec Cics ReturnCics Transaction Security Cics UpsiApplication Programming Spool Interface restrictions SAA AD/Cycle COBOL/370 SAA AD/Cycle C/370 SAA AD/Cycle PL/I Testing and Problem Determination Considerations CICS/VSE and TS Coexistence ConsiderationsVendor Applications Cics with DL/IUser Profiles Iccf and TSOPreparing to Use the System 155Permit JCL Adduser Aaaa PASSWORDsecret SpecialPermit Parmlib Classtsoauth Idaaaa Accessread Permit OperSecurity Logon ProceduresMessage Facilities Using the System SummaryEntering and Manipulating Data Accessing the SystemDescriptive Qualifier Data Set Contents Edit Payrollprtchk NEW Cobol Executing Programs at a Terminal ReadySubmitting Jobs for Batch Execution Converting Iccf Libraries Using Command ProceduresMigrating from VSE/ICCF to MVS and TSO/E Sample Iccf Procedure Sysin DD Data TOP Stack 13 Quit Save Iebupdte Edit Iebupdte Next OptionsLoad Dtsprocs DELIccf Procedures and Macros VSE to OS/390 Migration Workbook 169 DatabasesDL/I and IMS/VS DB Differences Introduction Primary Index of Hidam DB MVS System RequirementsData Base Descriptor DBD Secondary Index for HD DBBatch Programming Program Specification Block PSBInteractive Macro Facility IMF Command-Level Coding Hlpi 5.1 RPGPCB after GE Status Statement CompatibilityField Level Sensitivity NI Status CodesUtilities OperationsBackout Utility/Disk Logging 7.4 DL/I Parameter StatementAlternate DL/I and IMS/ESA Access Database PortabilityUnloading and Reloading the Database Unload DB IMS GEN Changes Utilities Operations TuningDL/I DBD YesEnd Users 9 DL/I Multiple Partition SupportAdditional Information Application Developers SQL/DS Dbsu UNLOAD/RELOAD Database Administrators DBAsSystem Administrators SQL/DS Dbsu LoadYear Security AdministratorsOther Comparison Areas Drda Considerations Data Replication and Data AccessSummary of Migration Task Transaction ManagementDatabases VSE to OS/390 Migration Workbook ACF/VTAM Telecommunications Subsystems185 Product Installation Vtam Data SetsPGM=ISTINM01,REGION=6000K,TIME=1440,DPRTY=15,13 Resource Definition and OperationNET Proc PERF=13 Exec PERFORM=&PERFVSE to OS/390 Migration Workbook Telecommunications Subsystems Operation Customization and ProgrammingResource Definition Vtam TablesNetwork Configuration ProgrammingACF/NCP Program GenerationUsage Btam Product InstallationBacklevel Hardware Support Migrating TCP/IPNetwork Definitions 4 TCP/IP Batch Jobs 2 TCP/IP Configuration3 TCP/IP Related User Data User Written TCP/IP Applications5.3 TCP/IP Applications using the BSD/C Sockets 5.1 TCP/IP Applications using the Sockets API for Assembler5.2 TCP/IP Applications using the Preprocessor API 5.4 TCP/IP Applications using the LE/VSE C Socket APIOS/390 BibliographyMQSeries MQSeries in Your Operating System Environment PrerequisitesTelecommunications Subsystems Installation and Customization PL/ICics Considerations Data Sets Networking Definitions Defining MQSeries Object and OperatingVSE to OS/390 Migration Workbook MQSeries-based Applications SC33-0807 Major Differences Power and JES210.1 JES2 Introduction Keep Disposition for Pre-Execution JobsTape Spooling Printer Forms Alignment via PsetupTime Event Scheduling for Jobs Separator Page DifferenceEnd-of-page Sensing Setting Up the Required ResourcesImplementing JES2 FCB IncompatibilitiesStarting JES2 10.2.1.2 JES2 Spool VolumesPower JES2 10.2.1.1 JES2 Checkpoint10.3 JES2-POWER Functional Comparison Tailoring JES2Multiple System Support Input ServiceJES2 Input Sources compared to Power Input FromJob Stream Disposition OS/390 SolutionJob Scheduling Additional Job Scheduling Functions with MVS/JES2 Serializing Job ExecutionTime Event Scheduling Output Service Output Service1 of 2. POWER/JES2 Output Service Comparison Output Segmentation 2 of 2. POWER/JES2 Output Service ComparisonPrinters Supported NEWPAGE=1FCB Naming Differences Separator Page DifferencesOutput Disposition FCB PrefixesUCS Naming Conventions FCB SpecificationInteractive User Interfaces ICCF/CMS/TSO Remote Workstation Definitions Remote Job EntryFunctional RJE Differences InteractiveRJE Exits Network Job EntryRJE Operations Application Interfaces Other Interfaces Job Information ServicesOutput Retrieval JES2 SMF Accounting Records Accounting ComparisonsJob Accounting NJE Accounting RAS CharacteristicsNJE Activity VSE/POWER Account MVS/JES2 SMF Record Accounting Records for NJE ActivitiesMapping Power Parameters to JES2 Init Parms 10.3.11 JES2 Testing TechniquesPOWER/JES2 Detailed Comparisons Equivalent JES2 Parms for Power Macro1 of 2. Power Macro to JES2 Parameter Mapping 2 of 2. Power Macro to JES2 Parameter Mapping Pline Mapping to JES2 Line Parameters for RJE and NJE1 of 2. Prmt Macro to JES2 Parameter Mapping Define BSC RemotesPline Macro to JES2 Parameter Mapping Prmt Macro to JES2 Parameter Mapping Define SNA Remote Workstations2 of 2. Prmt Macro to JES2 Parameter Mapping Define Compaction Tables Exit ComparisonsDefine NJE Nodes Pnode Macro to JES2 Parameter MappingSource Code Modifications POWER-JES2 Command EquivalencesPower Exit to JES2 Exits JES2 Patching FacilityTask Management Commands Command Short Code Form VerbNJE Operator Commands Network ManagementFile Control Commands Sending Commands and Messages2 of 2. Network Management Commands Sending Commands and MessagesFunctional Comparison between PSF/VSE and PSF/MVS Advanced Function Printing and Print Services Facility/MVSIntroducing PSF/MVS Migration EffortDefining Network Printers Installing and Configuring PSF/MVSDefining Channel-attached Printers to MVS Attachment Options11.2.2.2 TCP/IP Attached Printers PSF Startup ProceduresDefining Printers for PSF Printing FSS Procedure and Printdev Statements Comparison of Printdev Statement ParametersPrintdev Parameter Comparison Remote-Resident Resources Setting up AFP ResourcesMigrating Resources from VSE to OS/390 Defining ResourcesJCL and Jecl Differences Transferring Print Streams VSE and OS/390 CoexistenceMigrating Print Applications Printing from TSOStarting and Stopping PSF Command ComparisonUnderstanding Operational Differences High Level Language Programming InterfacesOther Differences Performance Installation Exits2 of 2. VSE OS/390 Command Comparison 11.6.2 PSF/MVS Publications AccountingReferences 11.6.1 PSF/VSE Publications RedbooksServices Internet LocationsVSE to OS/390 Migration Workbook Part 3. Converting VSE Languages to OS/390 Languages 247VSE to OS/390 Migration Workbook 249 CobolGeneral Comments on Cobol for OS/390 and VM DOS/VS Cobol Comparison of IBM Cobol CompilersVSE to OS/390 Migration Considerations Deck Migrating Object CodeUseful Publications OutddUseful Cobol Publications Converting from DOS/VS Cobol12.3.1 DOS/VS Cobol Cics Programs FIELD1 Values are 60 61 FIELD2 Values are 50 51 Common Cobol Coding ProblemsPRIMARY-FIELD PIC RECA-FIRST PIC RECA-SECND RECORD-AFiller Redefines RECORD-A Move 0 to RETURN-CODEIs ACCEPT-SYSIN Configuration Section SPECIAL-NAMES ParagraphSPECIAL-NAMES Sysin UPSI-0 Is CBL232B on Status is CBL232-BASE UPSI-1Linage Clause and END-OF-PAGE Phrase Procedure Division Input/OutputAssign Clause Close Statement for TapesFile Status Codes File Handling ConsiderationsProgram Termination Exit Program Goback Stop RUNFile Attribute Mismatches PROCEDURE-POINTER FunctionConverting from VS Cobol IsamSome Conversion Considerations for all VSE Cobol Compilers VS Cobol II Cics ProgramsConverting from Cobol for VSE/ESA VsamCompiler Options 12.8.1 RES/NORESCompiler Option Considerations for VS Cobol Wordnooo PgmnamecompatRmodeauto FDUMP/NOFDUMP Reserved WordsReserved Word Considerations for DOS/VS Cobol FlagsaaEMI Printing CbltitleCompiling and Running Your Converted Cobol Programs FUNCTIONPROCEDURE-POINTERReserved Word Considerations for VS Cobol II and Cobol for VSE to OS/390 Migration Workbook General Assembler Conversion Comments AssemblerAssembler Products 267System Interface and Macros MVS Register ConventionsRegister Conventions InitiationTermination Save Areas Application Program LogicLA 13,SAVEA LA 13,SAVEB Call Progb Call Progc Call Progb Call Progc Proga Start Progb Csect Progc Csect MVS11,SAVEA 11,SAVEB 11,SAVEC Savea DCMVS Call Larex Csect UsingVSE Call Call SUBRTN113,413 Get backward chain pointer 1213 Restore the registers1213,X′ FF′ Set return indicators Return Caller′ s save areaCommunication Region Job Name Upsi User Program Switch IndicatorsProblem Program Area Addresses User Program Communication BytesCommunications Region Simulation 15,1 Pass address Load the phaseProgb CallEP=PROGB VSE PhasenmEPLOC=PHASENM CdloadMVS BIN VSE Standard HM MS S MVS DECVSE Binary Time DEC,OUTAREA,DATETYPE=YYYYMMDD,LINKAGE=SYSTEMMVS Abend Dump ,STEP VSE JdumpDump Unlock DTL1 VSE Cancel ALL MVS AbendVSE Lock DTL1 MVS ENQ MF=E,DTL1VSE Chkpt Resar addressEnd address Poiner ′ S′Multitasking Macros ATTACH/DETACH MacrosCb locaion address EntrypointNumber of evens,ECB = address ECBLIST=address WAIT/POST MacrosEcb1,ecb2 VSE Wait Lisname Step Systems 13.2.2.3 RCB/ENQ/DEQ MacrosSystem System SystemsInterval Timer Interrupts Interrupt Handling RoutinesTecb Setime VSE Ttimer Cancel MVS Ttimer Cancel ,TUOperator Communication Interrupts ExitVirtual Storage Macros Getvis and Freevis MacrosVsam Macros ∙ M a C R F = Exlst Macro and Excpad RoutinesRPL Macro Additional MVS Parameters Showcb Macro Vsam Error and Reason Code CompatibilityData Management Macros MVS Vsam Check MacroIoreg List and Execute Macro FormsDefinition of Blksize 13.2.6.4 I/O Error Checking Liocs Card File DefinitionCtlchr = YES Mode = E O Devd = ..,MODE=E OBufno = ASAPrtov Macro Liocs Printer File DefinitionCntrl Macro Card File Programs in VSE and MVSPrintov = YES Liocs Tape File DefinitionControl = YES Macrf = PC Ctlchr = YES Sepasmb = YESClose Macro Reread Leave Rewind DispBSR, number of blocks VSE MVS Bsam onlyNo equivalen. The opion specified in he Disp FSR, number of blocksTrunc Macro Points MacroRelse Macro Feov Macro GET / PUT MacrosEropt = ACC SKP ABE SkipOptcd = Q MACRF=RP,WPClose TAPE,LEAVE Liocs Device-independent File DefinitionOpen Tape VSE PUT Close Tape Erropi = Ignore Eropi = ACC Skip SKP ABE Liocs Sequential File Definition on Direct Access DevicesLiocs Console File Definition Recfm = FABsam Inout Disp Updat Leave Outin Outinx Qsam InputOutput Leave Updat Disp Extend Input Reread Leave Free DispEret Macro Write Read MacroWrite Macro Check MacroFilename Address Feovd Macro Eropt = ACC Errext = YES Feovd = YES Hold = YESWORKA= YES Optcd = WSequential Dasd File Program in VSE and MVS Liocs Direct Access File DefinitionGeneral Considerations Readid = YES After = YESErrext = YES Readkey = YESError VSE MVS VSE Error Bytes and MVS Exception Code BitsWAITF, Open and Close Macros Record Addressing Track and Record AddressingTrack Addressing Record Addressing by IDRecord Reference by ID Record Addressing by KEYReference Methods Record Reference by KEY Reference MethodOPTCD=R,BUFL=58 Direct Access File ProcessingDCB DSORG=DA,MACRF=RISC,WIC ReferenceDamfile DCB MACRF=WICS,DSORG=DA,OPTCD=R Open DAMFILE,OUTPUTDecbadd Open DAMFILE,TAPE WRITER0DCB Specified in the DD statementOpen DAMFILE,UPDAT,TAPE,INPUT Loading a Sequential DAM File under MVSDECBR0 CLI Open R0FILE,OUTPUT,TAPE WRITER0DECBR0,SZ,R0FILE STC Open DAMFILE,OUTPUT CLIDISP=OLD DCB=BLKSIZE=50,RECFM=F GO.R0DD DD DSN=UDAM CountThree DCB=DSORG=DA DISP=,KEEP GO.DAMDD DD DSN=UDAMLoading a DAM File Fixed-Length Records without keys Loading a DAM File Undefined or Variable-Length RecordsAFTER=YES,ERREXT=YES,RELTRK=YES Open Damfile Read DAMFILE,KEYDamfile Addition Write DAMFILE,AFTER Processing a DAM File under VSEMultiple Search / Feedback Loading a Random Preformatted DAM File under VSELiocs Indexed Sequential Definition Type or ReferenceCCB Macro PiocsOverview of Programming Elements Comparison of Physical Iocs Elements Dtfph MacroDevice Information RPGMigration from VSE to OS/390 Print FilesExtent Exit File Access MethodsTape Labels Processing OptionsCalling PL/I Subprograms Direct access method files are processed with BdamCalling Cobol Subprograms YearVSE to OS/390 Migration Workbook PL/I 333Dynamic Loading of Dependent Programs Extended PrecisionMultitasking File OrganizationCompiler Options Options Specific to the DOS Compiler Parameters Passed to a Main Program15.1.7 %INCLUDE CatalogOptions Specific to the MVS Compiler Execution Options Linkages not Supported Exec and Process CardsLinkages Between Languages Linkages Supported Environment AttributesNot Supported in MVS SIS Option Sequential Insert Strategy Supported but to be Avoided²TOTAL² Option Calling Sort from PL/I Interfaces OfferedStorage Sort FieldsRecord Return CodeCall Plickpt pl,p2,p3,p4 DOS and MVS Checkpoint-Restart in PL/I PlickptPlirest If ONCODE= xxx then doOptions Specific to DOS PlicancDump in PL/I Optimizer Output File ² File Plidump could not be Opened Ddname MISSING²Compatibility Return Codes in PL/I Setting Return CodesOptions Specific to MVS Return Code ValuesConversion Automatic RestartOverlay Structures Overlay in MVSCALLing Dump 15.12 PL/I and Cics File SupportStatements not Supported 15.12.6 PL/I-CICS/VS Transaction Abend CodesPL/I VSE to OS/390 Migration Workbook Fortran Conversion Considerations FortranVS Fortran in OS/390 349VSE to OS/390 Migration Workbook Few Words about Cobol and PL/I Language Environment LEGeneral Comments on Language Environment 35117.2.1 LE/VSE-conforming Languages Useful Publications Migrating from LE/VSE-Conforming LanguagesFor VSE/ESA Migrating from Non-LE/VSE Run-time Environments Cobol for VSE/ESA17.3.3 PL/I for VSE/ESA Options MappingReport and Isasize Options, C/370 and DOS PL/I 17.4.2 C/370VS Cobol 370 Migration ConsiderationsDOS/VS Cobol Migration Considerations DOS PL/IVS Cobol II Migration Considerations Migration Comments Consideration Default setting for the Depthcondlmt option, both forDOS PL/I Migration Considerations DepthcondlmtTo Migrate You Need To Migrating Interlanguage Communications Applications1 of 2. ILC Migration Considerations DOS PL/IRun-time Options Migrating Assembler ApplicationsMigrating from LE/VSE 2 of 2. ILC Migration ConsiderationsShh Ihh Udddd SyslstRun-time Options and LE/VSE Cblqda Flow Interrupt Simvrd VctrsaveRun-time Options and LE/VSE 1.4 and Later Releases ArgparseLanguage Option Recommendation Recommended Settings for OptionsLanguage Environment High-Level Language Exits User Exits and Abnormal Termination ExitsAssembler User Exits Ceecxita CicsCallable Services and Math Services Abnormal Termination ExitsCobol and Cics 17.5.4 LE/VSE 1.4 LocalesCics CeetdliUser Exits and Abnormal Termination Exits VSE to OS/390 Migration Workbook Rexx and VSE/ESA Procedure Language RexxRexx and VM/ESA Rexx and TSO/E18.4.1 VSE/ESA Environment PowerEnvironments 18.4.2 VM/ESA EnvironmentRexx Exec Sample for the OS/2, TSO and CMS Environments Migration Issues18.4.3 TSO/E Environment RexxRexx and SAA Rexx BibliographyPart 4. Converting VSE Utilities to OS/390 Utilities 373VSE to OS/390 Migration Workbook 375 SortJCL Statements VSE to OS/390 Migration Workbook Control Statements VSE to OS/390 Migration Workbook Additional DFSORT/VSE Migration Considerations Icetool 381 DittoCompatibility with Previous Releases of Ditto MVS/ESA VSE/ESA VM/ESAFunction Description Replacement Ditto Functions that are No Longer SupportedDitto Functions that are Not Recommended Batch Keywords that are No Longer Supported Functions Keyword Description ReplacementDitto Function Code Synonyms Function Synonyms DescriptionBatch Keywords that are Not Recommended DITTO/ESA SecurityVSE to OS/390 Migration Workbook 21.1.1 OS/390 Vsam Backup/Restore Vsam Backup/RestoreVsam Backup/Restore 21.1.2 VSE/VSAM Backup/RestoreVSE to OS/390 Migration Workbook 389 LibrarianOverall Library Support 22.1.1 OS/390 Ispf Overview ∙ Interactive usage22.1.2 OS/390 Library Management VSE to OS/390 Migration Workbook VSE Listlog Utility Program LISTLOG/PRINTLOG Printing Log StreamsVSE Printlog Utility 23.3 OS/390 Hardcopy ProcessingPrinting Operlog SyslogPrinting Syslog Printing SMF Records 23.5 JES2 System Data Sets Job Log and System MessagesSystems Management Recording VSE to OS/390 Migration Workbook 397 VSE/Fast Copy and OS/390 DFSMSdss24.1 VSE/Fast Copy Online and Stand-Alone ∙ Compress ∙ DUMP/RESTOREDFSMSdss OS/390 Component ∙ ReleasePart 5. Setting Up the Migration Environment 399VSE to OS/390 Migration Workbook Prepare the Migration Environment 401Devices Supported by OS/390 Install and Configure Required HardwareProcessor Requirements Dasd RequirementsOther Hardware Requirements 403Shared Dasd Terminal AccessInter-Systems Connectivity Tape DrivesSoftwareXcel Installation Express SIE Order and Install the OS/390 SoftwareFee-based Methods of Installing OS/390 Data Transfer and NJEOther Offerings Entitled Methods of Installing OS/390SoftwareXcel SystemPac/MVS ServerPacCbpdo Set Up Standards, Procedures, and DocumentationInstallation Standards Data Management StandardsRelated Redbooks Dasd and Tape Volume SerialsMVS Naming Standards Data Sets409 Systems Management ProceduresJCL Standards Other MVS NamesImplementing System Security Enforcing Installation StandardsCreating an Emergency Backup System Backing Up Your SystemManaging Change Setting Up Critical Operations ProceduresManaging Problems 411Your Softcopy Library DocumentationYour Hardcopy Library Printing Softcopy Books413 Customize Your New OS/390 SystemVerifying the New OS/390 System Applying Preventive Service Providing Terminal Access to the OS/390 SystemProviding NJE Connection to the OS/390 System NetView FTP AccessMVS BCP Customization 25.5.2.1 SYS1.PARMLIB ParametersTailoring Other Components Optional Features for ReleaseOther OS/390 Elements Base Elements for ReleaseIndependent Software Vendor Products 417VSE to OS/390 Migration Workbook Terminology Differences in Testing ²Philosophy²Test Environments 419Application Development & Test System Production Maintenance Backup Sand-boxTest Systems in the Life of the Migration Application Program, JCL, and Data Conversion26.3 VM, LPAR, or Standalone Systems OS/390 Production Stand-By MaintenanceOS/390 VSE Backup Production Maintenance Logical Partitioning Software Partitioning Our Recommendation New Users of VM Advantages of Guest Support in VM/ESA System SimulationPerformance Benefits Reduced Hardware and Migration CostOperations Management Recovery ManagementAccess to VM/ESA CMS Applications Interactive Computing, Application Development and SupportModels 3 and 6 Fast Write Transparency Use of CMSDB2 Guest Sharing Multiple 3270 Session SupportBuilding the Initial OS/390 Test System Parallel ActivitiesSynchronizing VSE Applications with OS/390 Versions 26.3.3.5 OS/390 Guest ConsiderationsMaintaining Your OS/390 Libraries and SMP/E Zones 26.5.1 OS/390 Maintenance Environment26.5.2 OS/390 Test Logical Partition Shared Dasd vs. Cloned Dasd Shared Dasd between OS/390 Test Systems vs. Cloned DasdShared Dasd between VSE and OS/390 vs. Cloned Dasd VSE to OS/390 Migration Workbook Part 6. Running Your OS/390 System 435VSE to OS/390 Migration Workbook 437 Orienting Iccf Users to TSO/ISPF27.1 TSO/ISPF and Sdsf Editing Data Sets Using Ispf Utilities Submitting JobsCreating and Executing Ispf Applications Managing ProjectsRetrieving Output Using Sdsf for OperatorsTracking Jobs VSE to OS/390 Migration Workbook Understanding the Operator Interfaces Orientation to OS/390 Console OperationOperating Hardware Consoles 443Console Modes Controlling ConsolesManaging Display Consoles DEL=R,SEG=28,CON=N,RNUM=14,RTME=001,MFORM=T,JDisplay Areas Using the TSO/E FunctionsExtended MCS Consoles PFKeysUsing Sdsf for System Operation Understanding Message Formats and RepliesDisplaying System Status Controlling the OS/390 SystemStarting the System Displaying the Status of Devices Stopping the SystemControlling Devices Understanding Device AllocationControlling TSO Users, Jobs and Started Tasks 28.4.3 JES2 DevicesSdsf Device Panels Displaying Work on Your SystemSdsf Panels MVS Commands28.5.1.2 JES2 Commands RMF and Other MonitorsControlling Started Tasks Controlling Time Sharing UsersControlling Batch Jobs Host Operations Managing Remote Operations28.6.1 JES2 RJE Operations Remote Workstation OperationsNJE Operations Using Sdsf Panels for RJECommand Authority for Remote Operators Remotes Without Consoles$D Nxx.′$D NODEyy′ Using Sdsf Panels for NJE$D PATHnodename $D MNn,′Please drain your session′455 Orientation for UtilitiesIEBxxx or IEHxxx DFSMSdss Storage Administration Reference, SC26-4929 DFSMSdssSystems Management Philosophy and Methodology 457VSE to OS/390 Migration Workbook Systems Management Scope What Needs to be Managed? Role of Automation Change Management OverviewProblem Management Overview MethodologyTasks Performance Management Overview Methodology Operations Management Overview Methodology Automating Operational Procedures Security Management Overview Configuration Management Overview Methodology Asset Management Overview Accounting Management OverviewSummary Dumps Diagnosing System ProblemsProblem Determination Tools IpcsAnalyzing Traces Using IpcsTraces Performance Tools 31.4 JES2 DiagnosisSlip DFSMS/MVS Diagnosis Analyzing Catalogs for Errors and SynchronizationCatalog Recovery DFSMSdfpChecking a Vsam Ksds for Structural Errors DFSMShsmDiagnostic Reference Publications DFSMSrmmPart 7. Converting your Applications 479VSE to OS/390 Migration Workbook Conversion Process 481Conversion Process Introduction ∙ Refer to MVS MS Production Standards, LB11-8080Conversion Process Secure OS/390 Skills PrerequisitesManuals 32.1.3.6 24x7 Installations Migrate the SNA Network EarlyAssumptions Mass Conversion Overview / Benefits Automated Conversion Repetitive ConversionAutomation Limits Mass Conversion SwitchoverMass Conversion Tools DMT DOS/OS/390 Translator Automated Conversion ProcessCortex MS INT File IntegrationPrep Preparation Switch SwitchoverEZ-PCL Easy PCL ENV EnvironmentJCL Conversion Tools Inventory ValidationTranslate the Languages/Programs File TransferMass Conversion Phase Overview Preparation Phases∙ Implement System Managed Storage Dfsms Phase 0 Project Management and Technical LeadershipProject Planning and Orientation Phase 1 Application Inventory Collection Analysis and Resolution of ExceptionsDetermination Supply32.4.3 OS/390 Standards and Naming Conventions VSE to OS/390 Migration Workbook Phase 2 Conversion Specifications Analyze the VSE Source Material Determine the Method to Get from Source to Target Phase 3 Customization or Development of Conversion ToolsDesign the MVS Target Output VSE Positioning Manual OS/390 ConversionConversion Phases Program Conversion ConsiderationsCommon VSE Coding Practices Causing Conversion Problems Phase 4 Initial Trial Conversion Objectives of testing Phases of testingResponsibilities Testing PrioritiesPersonnel Involvement in Testing RecommendationsDasd Requirements MVS Tools TestingTest Plan Subsystem Storage ProtectConversion Process 32.5.4.4 OS/390 Automated Operations Tools Initialization Testing Unit TestingData Migration in Unit Testing Online Unit TestingBatch Unit Testing Timing between Online and Batch TestingBatch System TestingOnline Data Migration in Parallel Testing Parallel/Production Simulation TestingData Migration in System Testing Job Simulation Implementation PhasesDate Concerns during Parallel Testing Final JCL Conversion Phase 6 Actual Conversion and SwitchoverConverting the Development Material Data/File Migration SwitchoverFinal Program Conversion Phase 7 Initial OS/390 Operations Additional Switchover TasksAutomated Migration Services AMS Conversion Services and ToolsConversion Services IBM Global Services 519Conversion Tools 33.2.1 VSE/ESA Facilities IBM OPTI-AUDIT for VSEProduct Highlights Product DetailsIBM Cobol and Cics Command Level Conversion Aid Ccca Product Positioning Technical DescriptionSisro CORTEX-Migration System CORTEX-MS CA-Convertor Source Recovery CompanyComputer Associates CA-DUORename/SRC Recovery/SRCCobol Recovery Example Reconcile/SRCPart 8. Migration Experience 527VSE to OS/390 Migration Workbook Environment Customer Migration ExampleBackground HardwareInventory ResourcesDuration Phase OnePhase Two Benefits Part 9. Appendixes 533VSE to OS/390 Migration Workbook Appendix A. Education Information 535OEM Product Education When are Courses Scheduled and When are they Needed?Custom Classes Where will the Training Take Place? Who will Provide the Training?VSE to OS/390 Migration Workbook VSE ISV System Management Products and OS/390 Compared Appendix B. Mapping ISV Products and FunctionsIBM Software Migration Project Office Smpo 539Idms Appendix B. Mapping ISV Products and Functions VSE to OS/390 Migration Workbook 543 Appendix C. Dfsms Naming ConventionsData Set Naming Guidelines Components of a Data Set Name High-Level Qualifier HLQAppendix C. Dfsms Naming Conventions File Contents Relative ImportanceThings Not to Include in the Data Set Name User NameData Set Level Department NumberOutput Device Type Application LocationManagement Criteria Expiration DateCommon Applications Naming Conventions Access MethodJob Name TSO Naming ConventionsHlq.DSNDBx.dbname.tblspacename.I0001.A00n Vsam Data Set Naming Conventions3 DB2 Naming Conventions DSNDBx isGeneration Data Sets C.GnnnnV00VSE to OS/390 Migration Workbook Appendix D. Special Notices 553AFP ACF/VTAMAdstar AIXFollowing terms are trademarks of other companies VM/ESA VM/XA VSE/ESA VtamVSE to OS/390 Migration Workbook Other Redbooks Appendix E. Related PublicationsInternational Technical Support Organization Publications OS/390 Product PublicationsBook Title Publication Number Planning Books2 OS/390 Online Product Library SK2T-6700Redbooks on CD-ROMs Other PublicationsOther Sources Books on the Internet Redbooks 1.2 OS/390 Books IBM Printing SystemsVSE to OS/390 Migration Workbook 561 How to Get Itso RedbooksHow IBM Employees Can Get Itso Redbooks ∙ Mail Orders Ð send orders to How Customers Can Get Itso Redbooks∙ Telephone Orders ∙ Fax Ð send orders toIBM Redbook Order Form Please send me the followingVSE to OS/390 Migration Workbook Glossary Numerics 565VSE 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 Interactive Computing and Control Facility ICCF. An Language/Product Days Since Dec-31Language Environment Oct-14 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 Resource Access Control Facility RACF. An Rolling window. Synonymous with sliding windowO 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 List of Abbreviations 583Callable Services Library Command ListRecovery Control VolumeEnvironmental error Record Data Set ServicesExtended Common Service External Symbol DictionaryInteractive Problem Control Interactive Command FacilityService Facility Indexed Sequential AccessPower END SeriesPrint Service Facility/6000 Program Specification BlockPrint Service Facility Queued Sequential AccessSystem Services Program Service Planning GuideSQL Processor Using File SYStem ADMinistratorVsam Volume Record Volume Table of ContentsVsam Volume Data Set Facility EXtended Recovery FacilityACF/VTAM Index Special Characters591 Apsrmark MVS TtimerCancel Aptrmark VSEIndex PSF/MVS Batch TCP/IP 195 unit testingDiagnostic reference 478 Language Environment 353 MQSeries Plicanc Plickpt PlirestCics CobolConversion CA-Convertor Dadsm Dasd Courses locations 537 schedules 536 when neededCORTEX-MS VSE to OS/390 Migration Workbook Device Ditto Data Division File Description FD E15 Exit ProcedureEntrypoint AssociateFilesec FBA DasdGonumber FortranIdcams Iebcopy Iebgener Isasize IpcsIsam Ismf IspfJES2 Link LE/VSELimsconv LiocsCortex MS Migration 356VS Fortran TCP/IPOperlog MVS device addresses 80 DFPNJE Printing Operlog 394 Opsys routine 349 OPTI-AUDIT 79MVS BCP OS/390 NCPVtamlst 190 XCF Piocs PL/I PL/I 394 SMF records 395 Softcopy books 412 SyslogRacf ProjectRES/NORES RDO371 VM/ESA ResourcesTSO/E 370 Risk management Risky VSE coding practices 504Fields RexxSort IcetoolVSE to OS/390 Migration Workbook Index Vsam BACKUP/RESTOREVS Cobol II BtamOS/VS Cobol Delete IgnoreerrorVSE/VSAM BACKUP/RESTORE & VSE CompressVSE Year2000 VtamlstPlease answer the following questions Itso Redbook Evaluation621 VSE to OS/390 Migration Workbook SG24-2043-00 XRL/1 XRL/2 XRL/3 JmacpXRL/4 XRL/5 XRL/6 XRL/7 XRL/8 XRL/9 XRL/10 XRL/11 DittindOperlog XRL/12Oploind ACB XRL/13Smfpind DL/I PowerXRL/14 NJEXRL/15 XRL/16 XRL/17 XRL/18 Ctrind XRL/19Vosind CsysindXRL/20 XRL/21 XRL/22 MVS BCPXRL/23 Cortex MSXRL/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.
Top Page Image Contents