IBM OS/390 manual Filename Address

Page 332

Notes:

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

2.If the I/O operation did not complete successfully, the error analysis routine (SYNAD) is given control if you have provided one.

3.The following conditions are also handled:

When the system is reading, volume switching is automatic. The end-of-data-set (EODAD) routine is given control if an input request is made after all the records have been retrieved.

When the system is writing, additional space on the device is obtained when the current space is filled and more WRITE macros have been issued.

POINTW / POINTR Macros

VSE

POINTW

filename

,

address

 

POINTR

(1)

 

(0)

 

 

 

 

 

MVS

POINT

dcbaddress

,

blockaddress

 

 

(2-12)

 

(2-12)

 

 

(1)

 

(0)

 

 

 

 

 

Notes:

1.Blockaddress is the address of a fullword on a fullword boundary containing the required record identification in the same form as it is obtained from the NOTE macro.

2.If you use WRITE SQ after POINTR in VSE, set the 0 of TTR0 to 1 in MVS for the same result.

POINTS Macro

VSE

POINTS

filename

 

 

 

 

(1)

 

 

 

 

 

 

 

MVS

POINT

dcbaddress

,

blockaddress

 

 

(2-12)

 

(2-12)

 

 

(1)

 

(0)

 

 

 

 

 

Notes:

1.The POINTS macro in VSE causes repositioning of the file to the lower limit of its first extent.

2.The POINT macro in MVS positions the data set to the block indicated in the blockaddress field, which contains TTRz where:

TT is the relative track number.

R is the block number on that track.

z is zero or one, if it is one, the block following the TTR block is referenced.

You can specify the first block of a direct access device data set by either hexadecimal 00000001 or 00000100.

3. The MVS POINT macro is valid only for BSAM and BPAM.

308VSE to OS/390 Migration Workbook

Image 332
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 Part 5. Setting Up the Migration Environment Part 4. Converting VSE Utilities to OS/390 UtilitiesVSE/Fast Copy and OS/390 DFSMSdss 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 Appendix E. Related Publications 565List of Abbreviations 583 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 Why Customers Migrate Synopsis of This BookWhat do I need to read? System Programmers Read the followingTraditional Reasons for Migrating Business ConsolidationVirtual Storage Mergers/AcquisitionsCapacity Constraints Cics SupervisorProd UnusedCics TOR Static Dynamic Partitions SVA 31-Bit 16MB VSE ACFVSE Vtam C1 Y1 SVA 24- BitImage Way Processor SupportTask Quantity 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 Areas of VSE and OS/390 Differences Source ProgramsSource Program Inventory Batch and Online Program ConversionJob Control Language FilesComparison of Basic VSE Functions & Components to OS/390 OperationsIocp IOCP, HCD Erep Mshp SMP/ELE/VSE LE/MVS A S MCobol PL/I RPGOS/390 Components/Products/Subsystems Comparison of VSE Functions & Components to OS/3901.1 OS/390 Product Content OS/390 Operating EnvironmentDistributed Computing Services Network Computing ServicesUnix System Services LAN ServicesMVS Subsystem and Component Terminology ∙ Interactive Problem Control System Ipcs ∙ Data Facility Storage Management Subsystem∙ Systems Resources Manager SRM ∙ Systems Management Facility SMFSupporting Products Subsystem Level Comparison/Affinity What Changes Between VSE and OS/390?Philosophical Changes SecurityAutomation Console Operator InterfaceJCL Processing 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 URLDeveloping the Plan Overview ReferencesRecommendations Project ManagementTwo Phase Approach Take Advantage Of Conversion Tools and AutomationMigration Plan Guide and Outline Conversion MethodMigration Responsibilities Project StaffingLibrarian Migration Assignments Plan Components Approach TeamProject Manager Systems ProgrammersTasks Applications ProgrammersMilestone Events Education Progressive versus Mass Conversion Approach DifferencesHistorical Perspective Shared Application Files and DatabasesShared Application Code Operations Support StaffingComplexity of Implementation Standardized Conversion Deliverables and AutomationRisk Management Mass Migration as a Conversion Method Mass Migration Used as a Conversion ToolCobol RPGPlan Examples Project Schedule Estimated Project ScheduleEstimated Schedule for CNV Responsibilities Month Number Month InitialEstimated Schedule for ABC Responsibilities Estimated Schedule for SER ResponsibilitiesABC 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 ExampleData Driven Segmentation of Output JCL Parameter Handling$$ LST CLASS=J,DEST=DANJ,DISP=H $$ EOJJCL Expansion Operator Flexibility and InterventionAssgn SYS005,CUU Comment Lines in the JCLPause Statement Allocation of Resources Hidden JCLResource Allocation at Open Time Partition and System Standard Labels5.3 ²Carry-Over² Permanent Assignments and Power DefaultsHelp for the Hidden JCL Problem Device Address Specifications Assgn SYS010,FEFSYS010 DD SYSOUT= REPORT1 DD SYSOUT=Communication Region Date and Upsi CatalogsPartition Dependent Codes in JCL VSE Job Control Statements UpsiJob Statement Exec StatementReset Statement MTC StatementAssgn Statement Dlbl and ExtentMVS Job Control Statements DD StatementOutput JCL 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 Comparison of Power and JES2 Jecl a Summary 2. Overview of Power Jecl StatementsJecl 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 Sample VSE plus Carry-Over Extent DISKO1,0,100,500Extent DISK14,0,600,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 HDR1 TM Data Records TM EOV1 TM VOL1 HDR1 TM Data Records TM EOF1 TM TMVOL1 UHL1 UHL8No Labels Standard User LabelsUse should be controlled Nonstandard LabelsBypass Label Processing Facility in OS/390 OS/390 Single Data Set-Single Volume OS/390 Single Data Set-Multiple VolumesVSE With Tapemark Before Data Records 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 CatalogsDEPT4 DEPT1 & JonesPayroll 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 Catalogs− Delete Ignoreerror Vsam Functional DifferencesMoving a Vsam Catalog to a Different Dasd Type Areas of ConsiderationShared Volume Ownership FBA DasdCatalog Structures Noimbed OptionAMS Commands Synchk ParameterXXL Ksds New in VSE/ESA 2.3, greater than 4GB Ksds Compress New in VSE/ESA 2.2, Vsam Record CompressionVsam CISIZEs and Record Sizes VSE/VSAM-managed SAM FilesDefault Models Noallocation Data SetsJCL Implicit Define 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 MVSCics General System Considerations ApplData Bases TOR AOR1 AOR2Journaling to tape service Macro-level programsBtam devices and controllers Cics internal security and signon tableAccess to Cics system control blocks Enqueue domain Kernel domain DomainMessage domain Monitoring 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 System Programming Commands Cics System Program Interface and ExitsExits Collect StatisticsCommand Exit points Exec Cics AbendAll exits 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/IIccf and TSO Preparing to Use the SystemUser Profiles 155Adduser Aaaa PASSWORDsecret Special Permit Parmlib Classtsoauth Idaaaa AccessreadPermit JCL 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 Options Load DtsprocsSave Iebupdte Edit Iebupdte Next DELIccf Procedures and Macros VSE to OS/390 Migration Workbook 169 DatabasesDL/I and IMS/VS DB Differences Introduction MVS System Requirements Data Base Descriptor DBDPrimary Index of Hidam DB Secondary Index for HD DBProgram Specification Block PSB Interactive Macro Facility IMF Command-Level Coding HlpiBatch Programming 5.1 RPGStatement Compatibility Field Level SensitivityPCB after GE Status 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 Changes Utilities Operations Tuning DL/I DBDUnload DB IMS GEN YesEnd Users 9 DL/I Multiple Partition SupportAdditional Information Application Developers Database Administrators DBAs System AdministratorsSQL/DS Dbsu UNLOAD/RELOAD SQL/DS Dbsu LoadYear Security AdministratorsOther Comparison Areas Data Replication and Data Access Summary of Migration TaskDrda Considerations Transaction ManagementDatabases VSE to OS/390 Migration Workbook ACF/VTAM Telecommunications Subsystems185 Product Installation Vtam Data SetsResource Definition and Operation NET Proc PERF=13 ExecPGM=ISTINM01,REGION=6000K,TIME=1440,DPRTY=15,13 PERFORM=&PERFVSE to OS/390 Migration Workbook Telecommunications Subsystems Customization and Programming Resource DefinitionOperation Vtam TablesNetwork Configuration ProgrammingACF/NCP Program GenerationBtam Product Installation Backlevel Hardware SupportUsage Migrating TCP/IPNetwork Definitions 2 TCP/IP Configuration 3 TCP/IP Related User Data4 TCP/IP Batch Jobs User Written TCP/IP Applications5.1 TCP/IP Applications using the Sockets API for Assembler 5.2 TCP/IP Applications using the Preprocessor API5.3 TCP/IP Applications using the BSD/C Sockets 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 Power and JES2 10.1 JES2 IntroductionMajor Differences Keep Disposition for Pre-Execution JobsPrinter Forms Alignment via Psetup Time Event Scheduling for JobsTape Spooling Separator Page DifferenceSetting Up the Required Resources Implementing JES2End-of-page Sensing FCB Incompatibilities10.2.1.2 JES2 Spool Volumes Power JES2Starting JES2 10.2.1.1 JES2 Checkpoint10.3 JES2-POWER Functional Comparison Tailoring JES2Input Service JES2 Input Sources compared to PowerMultiple System Support 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 2 of 2. POWER/JES2 Output Service Comparison Printers SupportedOutput Segmentation NEWPAGE=1Separator Page Differences Output DispositionFCB Naming Differences FCB PrefixesUCS Naming Conventions FCB SpecificationInteractive User Interfaces ICCF/CMS/TSO Remote Job Entry Functional RJE DifferencesRemote Workstation Definitions InteractiveRJE Exits Network Job EntryRJE Operations Application Interfaces Other Interfaces Job Information ServicesOutput Retrieval JES2 SMF Accounting Records Accounting ComparisonsJob Accounting RAS Characteristics NJE Activity VSE/POWER Account MVS/JES2 SMF RecordNJE Accounting Accounting Records for NJE Activities10.3.11 JES2 Testing Techniques POWER/JES2 Detailed ComparisonsMapping Power Parameters to JES2 Init Parms 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 Exit Comparisons Define NJE NodesDefine Compaction Tables Pnode Macro to JES2 Parameter MappingPOWER-JES2 Command Equivalences Power Exit to JES2 ExitsSource Code Modifications JES2 Patching FacilityTask Management Commands Command Short Code Form VerbNJE Operator Commands Network ManagementSending Commands and Messages 2 of 2. Network Management CommandsFile Control Commands Sending Commands and MessagesAdvanced Function Printing and Print Services Facility/MVS Introducing PSF/MVSFunctional Comparison between PSF/VSE and PSF/MVS Migration EffortInstalling and Configuring PSF/MVS Defining Channel-attached Printers to MVSDefining Network Printers 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 Setting up AFP Resources Migrating Resources from VSE to OS/390Remote-Resident Resources Defining ResourcesTransferring Print Streams VSE and OS/390 Coexistence Migrating Print ApplicationsJCL and Jecl Differences Printing from TSOCommand Comparison Understanding Operational DifferencesStarting and Stopping PSF High Level Language Programming InterfacesOther Differences Performance Installation Exits2 of 2. VSE OS/390 Command Comparison Accounting References 11.6.1 PSF/VSE Publications11.6.2 PSF/MVS 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 Migrating Object Code Useful PublicationsDeck 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 RECORD-A Filler Redefines RECORD-ARECA-FIRST PIC RECA-SECND Move 0 to RETURN-CODEConfiguration Section SPECIAL-NAMES Paragraph SPECIAL-NAMES SysinIs ACCEPT-SYSIN UPSI-0 Is CBL232B on Status is CBL232-BASE UPSI-1Procedure Division Input/Output Assign ClauseLinage Clause and END-OF-PAGE Phrase Close Statement for TapesFile Handling Considerations Program TerminationFile Status Codes Exit Program Goback Stop RUNPROCEDURE-POINTER Function Converting from VS CobolFile Attribute Mismatches IsamVS Cobol II Cics Programs Converting from Cobol for VSE/ESASome Conversion Considerations for all VSE Cobol Compilers VsamCompiler Options 12.8.1 RES/NORESCompiler Option Considerations for VS Cobol Wordnooo PgmnamecompatRmodeauto Reserved Words Reserved Word Considerations for DOS/VS CobolFDUMP/NOFDUMP 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 Assembler Assembler ProductsGeneral Assembler Conversion Comments 267System Interface and Macros MVS Register ConventionsRegister Conventions InitiationTermination Save Areas Application Program LogicLA 13,SAVEA LA 13,SAVEB Call Progb Call Progc Proga Start Progb Csect Progc Csect MVS 11,SAVEA 11,SAVEB 11,SAVECCall Progb Call Progc Savea DCLarex Csect Using VSE CallMVS Call Call SUBRTN11213 Restore the registers 1213,X′ FF′ Set return indicators Return13,413 Get backward chain pointer Caller′ s save areaCommunication Region Upsi User Program Switch Indicators Problem Program Area AddressesJob Name User Program Communication BytesCommunications Region Simulation Load the phase Progb15,1 Pass address CallVSE Phasenm EPLOC=PHASENMEP=PROGB CdloadVSE Standard HM MS S MVS DEC VSE BinaryMVS BIN Time DEC,OUTAREA,DATETYPE=YYYYMMDD,LINKAGE=SYSTEMMVS Abend Dump ,STEP VSE JdumpDump VSE Cancel ALL MVS Abend VSE Lock DTL1Unlock DTL1 MVS ENQ MF=E,DTL1Resar address End address PoinerVSE Chkpt ′ S′Multitasking Macros ATTACH/DETACH MacrosCb locaion address EntrypointNumber of evens,ECB = address ECBLIST=address WAIT/POST MacrosEcb1,ecb2 VSE Wait Lisname 13.2.2.3 RCB/ENQ/DEQ Macros SystemStep Systems System SystemsInterval Timer Interrupts Interrupt Handling RoutinesVSE Ttimer Cancel MVS Ttimer Cancel ,TU Operator Communication InterruptsTecb Setime ExitVirtual Storage Macros Getvis and Freevis MacrosVsam Macros ∙ M a C R F = Exlst Macro and Excpad RoutinesRPL Macro Additional MVS Parameters Vsam Error and Reason Code Compatibility Data Management MacrosShowcb Macro MVS Vsam Check MacroIoreg List and Execute Macro FormsDefinition of Blksize 13.2.6.4 I/O Error Checking Liocs Card File DefinitionMode = E O Devd = ..,MODE=E O Bufno =Ctlchr = YES ASALiocs Printer File Definition Cntrl MacroPrtov Macro Card File Programs in VSE and MVSLiocs Tape File Definition Control = YES Macrf = PC Ctlchr = YESPrintov = YES Sepasmb = YESClose Macro Reread Leave Rewind DispVSE MVS Bsam only No equivalen. The opion specified in he DispBSR, number of blocks FSR, number of blocksTrunc Macro Points MacroRelse Macro Feov Macro GET / PUT MacrosSkip Optcd = QEropt = ACC SKP ABE MACRF=RP,WPClose TAPE,LEAVE Liocs Device-independent File DefinitionOpen Tape VSE PUT Close Tape Liocs Sequential File Definition on Direct Access Devices Liocs Console File DefinitionErropi = Ignore Eropi = ACC Skip SKP ABE Recfm = FAQsam Input Output Leave Updat Disp Extend InputBsam Inout Disp Updat Leave Outin Outinx Reread Leave Free DispEret Macro Read Macro Write MacroWrite Check MacroFilename Address Feovd Macro Errext = YES Feovd = YES Hold = YES WORKA= YESEropt = ACC Optcd = WSequential Dasd File Program in VSE and MVS Liocs Direct Access File DefinitionGeneral Considerations After = YES Errext = YESReadid = YES Readkey = YESError VSE MVS VSE Error Bytes and MVS Exception Code BitsWAITF, Open and Close Macros Track and Record Addressing Track AddressingRecord Addressing Record Addressing by IDRecord Reference by ID Record Addressing by KEYReference Methods Record Reference by KEY Reference MethodDirect Access File Processing DCB DSORG=DA,MACRF=RISC,WICOPTCD=R,BUFL=58 ReferenceOpen DAMFILE,OUTPUT DecbaddDamfile DCB MACRF=WICS,DSORG=DA,OPTCD=R Open DAMFILE,TAPE WRITER0Specified in the DD statement Open DAMFILE,UPDAT,TAPE,INPUTDCB Loading a Sequential DAM File under MVSOpen R0FILE,OUTPUT,TAPE WRITER0 DECBR0,SZ,R0FILE STCDECBR0 CLI Open DAMFILE,OUTPUT CLICount ThreeDISP=OLD DCB=BLKSIZE=50,RECFM=F GO.R0DD DD DSN=UDAM 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 RecordsOpen Damfile Read DAMFILE,KEY Damfile Addition Write DAMFILE,AFTERAFTER=YES,ERREXT=YES,RELTRK=YES 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 MacroRPG Migration from VSE to OS/390Device Information Print FilesFile Access Methods Tape LabelsExtent Exit Processing OptionsDirect access method files are processed with Bdam Calling Cobol SubprogramsCalling PL/I Subprograms YearVSE to OS/390 Migration Workbook PL/I 333Extended Precision MultitaskingDynamic Loading of Dependent Programs File OrganizationParameters Passed to a Main Program 15.1.7 %INCLUDECompiler Options Options Specific to the DOS Compiler CatalogOptions Specific to the MVS Compiler Execution Options Exec and Process Cards Linkages Between Languages Linkages SupportedLinkages not Supported Environment AttributesNot Supported in MVS Supported but to be Avoided ²TOTAL² OptionSIS Option Sequential Insert Strategy Calling Sort from PL/I Interfaces OfferedSort Fields RecordStorage Return CodeCheckpoint-Restart in PL/I Plickpt PlirestCall Plickpt pl,p2,p3,p4 DOS and MVS If ONCODE= xxx then doPlicanc Dump in PL/I Optimizer Output FileOptions Specific to DOS ² File Plidump could not be Opened Ddname MISSING²Return Codes in PL/I Setting Return Codes Options Specific to MVSCompatibility Return Code ValuesAutomatic Restart Overlay StructuresConversion Overlay in MVS15.12 PL/I and Cics File Support Statements not SupportedCALLing Dump 15.12.6 PL/I-CICS/VS Transaction Abend CodesPL/I VSE to OS/390 Migration Workbook Fortran VS Fortran in OS/390Fortran Conversion Considerations 349VSE to OS/390 Migration Workbook Language Environment LE General Comments on Language EnvironmentFew Words about Cobol and PL/I 35117.2.1 LE/VSE-conforming Languages Useful Publications Migrating from LE/VSE-Conforming LanguagesFor VSE/ESA Cobol for VSE/ESA 17.3.3 PL/I for VSE/ESAMigrating from Non-LE/VSE Run-time Environments Options Mapping17.4.2 C/370 VS CobolReport and Isasize Options, C/370 and DOS PL/I 370 Migration ConsiderationsDOS/VS Cobol Migration Considerations DOS PL/IVS Cobol II Migration Considerations Default setting for the Depthcondlmt option, both for DOS PL/I Migration ConsiderationsMigration Comments Consideration DepthcondlmtMigrating Interlanguage Communications Applications 1 of 2. ILC Migration ConsiderationsTo Migrate You Need To DOS PL/IMigrating Assembler Applications Migrating from LE/VSERun-time Options 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 User Exits and Abnormal Termination Exits Assembler User ExitsHigh-Level Language Exits Ceecxita CicsCallable Services and Math Services Abnormal Termination Exits17.5.4 LE/VSE 1.4 Locales CicsCobol and Cics CeetdliUser Exits and Abnormal Termination Exits VSE to OS/390 Migration Workbook Procedure Language Rexx Rexx and VM/ESARexx and VSE/ESA Rexx and TSO/EPower Environments18.4.1 VSE/ESA Environment 18.4.2 VM/ESA EnvironmentMigration Issues 18.4.3 TSO/E EnvironmentRexx Exec Sample for the OS/2, TSO and CMS Environments 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 Ditto Compatibility with Previous Releases of Ditto381 MVS/ESA VSE/ESA VM/ESAFunction Description Replacement Ditto Functions that are No Longer SupportedDitto Functions that are Not Recommended Functions Keyword Description Replacement Ditto Function Code SynonymsBatch Keywords that are No Longer Supported Function Synonyms DescriptionBatch Keywords that are Not Recommended DITTO/ESA SecurityVSE to OS/390 Migration Workbook Vsam Backup/Restore Vsam Backup/Restore21.1.1 OS/390 Vsam 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 LISTLOG/PRINTLOG Printing Log Streams VSE Printlog UtilityVSE Listlog Utility Program 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 ∙ DUMP/RESTORE DFSMSdss OS/390 Component∙ Compress ∙ ReleasePart 5. Setting Up the Migration Environment 399VSE to OS/390 Migration Workbook Prepare the Migration Environment 401Install and Configure Required Hardware Processor RequirementsDevices Supported by OS/390 Dasd RequirementsOther Hardware Requirements 403Terminal Access Inter-Systems ConnectivityShared Dasd Tape DrivesOrder and Install the OS/390 Software Fee-based Methods of Installing OS/390SoftwareXcel Installation Express SIE Data Transfer and NJEEntitled Methods of Installing OS/390 SoftwareXcel SystemPac/MVSOther Offerings ServerPacSet Up Standards, Procedures, and Documentation Installation StandardsCbpdo Data Management StandardsDasd and Tape Volume Serials MVS Naming StandardsRelated Redbooks Data SetsSystems Management Procedures JCL Standards409 Other MVS NamesEnforcing Installation Standards Creating an Emergency Backup SystemImplementing System Security Backing Up Your SystemSetting Up Critical Operations Procedures Managing ProblemsManaging Change 411Documentation Your Hardcopy LibraryYour Softcopy 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 SystemNetView FTP Access MVS BCP CustomizationProviding NJE Connection to the OS/390 System 25.5.2.1 SYS1.PARMLIB ParametersOptional Features for Release Other OS/390 ElementsTailoring Other Components Base Elements for ReleaseIndependent Software Vendor Products 417VSE to OS/390 Migration Workbook Differences in Testing ²Philosophy² Test EnvironmentsTerminology 419Production Maintenance Backup Sand-box Test Systems in the Life of the MigrationApplication Development & Test System 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 CostRecovery Management Access to VM/ESA CMS ApplicationsOperations Management Interactive Computing, Application Development and SupportUse of CMS DB2 Guest SharingModels 3 and 6 Fast Write Transparency Multiple 3270 Session SupportParallel Activities Synchronizing VSE Applications with OS/390 VersionsBuilding the Initial OS/390 Test System 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 Orientation to OS/390 Console Operation Operating Hardware ConsolesUnderstanding the Operator Interfaces 443Controlling Consoles Managing Display ConsolesConsole Modes DEL=R,SEG=28,CON=N,RNUM=14,RTME=001,MFORM=T,JUsing the TSO/E Functions Extended MCS ConsolesDisplay Areas PFKeysUsing Sdsf for System Operation Understanding Message Formats and RepliesDisplaying System Status Controlling the OS/390 SystemStarting the System Stopping the System Controlling DevicesDisplaying the Status of Devices Understanding Device Allocation28.4.3 JES2 Devices Sdsf Device PanelsControlling TSO Users, Jobs and Started Tasks Displaying Work on Your SystemMVS Commands 28.5.1.2 JES2 CommandsSdsf Panels RMF and Other MonitorsControlling Started Tasks Controlling Time Sharing UsersControlling Batch Jobs Managing Remote Operations 28.6.1 JES2 RJE OperationsHost Operations Remote Workstation OperationsUsing Sdsf Panels for RJE Command Authority for Remote OperatorsNJE Operations Remotes Without ConsolesUsing Sdsf Panels for NJE $D PATHnodename$D Nxx.′$D NODEyy′ $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 Diagnosing System Problems Problem Determination ToolsDumps IpcsAnalyzing Traces Using IpcsTraces Performance Tools 31.4 JES2 DiagnosisSlip Analyzing Catalogs for Errors and Synchronization Catalog RecoveryDFSMS/MVS Diagnosis 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 Automated Conversion Process Cortex MSDMT DOS/OS/390 Translator INT File IntegrationSwitch Switchover EZ-PCL Easy PCLPrep Preparation ENV EnvironmentInventory Validation Translate the Languages/ProgramsJCL Conversion Tools 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 Analysis and Resolution of Exceptions DeterminationCollection 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 testingTesting Priorities Personnel Involvement in TestingResponsibilities RecommendationsMVS Tools Testing Test PlanDasd Requirements Subsystem Storage ProtectConversion Process 32.5.4.4 OS/390 Automated Operations Tools Initialization Testing Unit TestingOnline Unit Testing Batch Unit TestingData Migration in 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 TasksConversion Services and Tools Conversion Services IBM Global ServicesAutomated Migration Services AMS 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 Source Recovery Company Computer AssociatesCA-Convertor CA-DUORecovery/SRC Cobol Recovery ExampleRename/SRC Reconcile/SRCPart 8. Migration Experience 527VSE to OS/390 Migration Workbook Customer Migration Example BackgroundEnvironment 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 Appendix B. Mapping ISV Products and Functions IBM Software Migration Project Office SmpoVSE ISV System Management Products and OS/390 Compared 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 ImportanceUser Name Data Set LevelThings Not to Include in the Data Set Name Department NumberApplication Location Management CriteriaOutput Device Type Expiration DateAccess Method Job NameCommon Applications Naming Conventions TSO Naming ConventionsVsam Data Set Naming Conventions 3 DB2 Naming ConventionsHlq.DSNDBx.dbname.tblspacename.I0001.A00n DSNDBx isGeneration Data Sets C.GnnnnV00VSE to OS/390 Migration Workbook Appendix D. Special Notices 553ACF/VTAM AdstarAFP AIXFollowing terms are trademarks of other companies VM/ESA VM/XA VSE/ESA VtamVSE to OS/390 Migration Workbook Appendix E. Related Publications International Technical Support Organization PublicationsOther Redbooks OS/390 Product PublicationsPlanning Books 2 OS/390 Online Product LibraryBook Title Publication Number SK2T-6700Other Publications Other Sources Books on the InternetRedbooks on CD-ROMs 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 How Customers Can Get Itso Redbooks ∙ Telephone Orders∙ Mail Orders Ð send orders to ∙ 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 583Command List RecoveryCallable Services Library Control VolumeData Set Services Extended Common ServiceEnvironmental error Record External Symbol DictionaryInteractive Command Facility Service FacilityInteractive Problem Control Indexed Sequential AccessPower END SeriesProgram Specification Block Print Service FacilityPrint Service Facility/6000 Queued Sequential AccessService Planning Guide SQL Processor Using FileSystem Services Program SYStem ADMinistratorVolume Table of Contents Vsam Volume Data Set FacilityVsam Volume Record EXtended Recovery FacilityACF/VTAM Index Special Characters591 Ttimer CancelApsrmark MVS Aptrmark VSEIndex Batch TCP/IP 195 unit testing Diagnostic reference 478 Language Environment 353 MQSeriesPSF/MVS Plicanc Plickpt PlirestCics CobolConversion CA-Convertor Dadsm Dasd Courses locations 537 schedules 536 when neededCORTEX-MS VSE to OS/390 Migration Workbook Device Ditto E15 Exit Procedure EntrypointData Division File Description FD AssociateFBA Dasd GonumberFilesec FortranIdcams Iebcopy Iebgener Ipcs IsamIsasize Ismf IspfJES2 LE/VSE LimsconvLink LiocsCortex MS 356 VS FortranMigration TCP/IPMVS device addresses 80 DFP NJEOperlog 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 SyslogProject RES/NORESRacf RDOResources TSO/E371 VM/ESA 370 Risk management Risky VSE coding practices 504Rexx SortFields IcetoolVSE to OS/390 Migration Workbook Index BACKUP/RESTORE VS Cobol IIVsam BtamDelete Ignoreerror VSE/VSAM BACKUP/RESTORE & VSEOS/VS Cobol 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 Power XRL/14DL/I NJEXRL/15 XRL/16 XRL/17 XRL/18 XRL/19 VosindCtrind 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.