rh._.exports({"0":[[" ","Setting up your MVS Build Environment"]],"1":[[" ","Setting \n up your MVS Build Environment"," ","Setting up builds on z/OS mainframes \n can be a complicated and lengthy process. It is recommended that you follow \n the steps below to set up your z/OS build environment:"," ","Check \n\t that the following software is installed and configured:"," ","A Dimensions server on \n\t\t any supported platform. For details see the ","Installation Guide for Windows"," ","or \n\t\t the ","Installation Guide for UNIX","."," ","Dimensions for z/OS: check \n\t\t that you can run the Dimensions for z/OS ISPF client, or perform \n\t\t a remote checkout from the desktop client to the Dimensions node. \n\t\t For details see the ","Dimensions for z/OS Guide","."," ","On \n\t your z/OS mainframe do the following:"," ","Pre-allocate the build \n\t\t areas that Dimensions uses to ensure that data sets are allocated \n\t\t properly (DCB, sizes, etc.) for your application and project. \n\t\t As a general rule, the last qualifier in the data set name indicates \n\t\t its type, for example, COBOL, COPY, H, and C. Build areas are \n\t\t typically allocated for each stage. Optionally, you can allocate \n\t\t a managed Development build area."," ","NOTE  ","Any \n\t managed build areas that you set up should be allocated under a security \n\t protected ID that the average Dimensions user does not have write \n\t access to. This precaution is necessary to protect the integrity of \n\t the data contained in the build areas."," ","Create data sets for targets \n\t\t and intermediate targets, for example, .LOAD and .OBJ respectively."," ","(Optional) Set up a user \n\t\t build area for your development work. Allocate a collection of \n\t\t data sets with a common HLQ (’directory’), as required for your \n\t\t build."," ","(Optional) \n\t If you are adding items from a PC to a z/OS mainframe and want automatic \n\t allocation of data sets, check that the Dimensions configuration file \n\t on the z/OS mainframe, MDH.V1010.MDHPARM(MDHTDCFG), has the correct \n\t defaults to create data sets by LLQ (low level qualifier). For details \n\t see the ","Dimensions for z/OS Guide",". \n\t It is recommended that you perform step 2 above to ensure proper data \n\t set sizing for each item type."]],"id":"351"})