home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
viscobv7.zip
/
vac22os2
/
ibmcobol
/
macros
/
mvsinfo.dat
< prev
next >
Wrap
Text File
|
1998-03-13
|
41KB
|
634 lines
***********************************************************************
* *
* ---- MVSINFO.DAT File ---- *
* *
* This file, named MVSINFO.DAT, is used to obtain information that *
* is required by any of the following components: *
* *
* - IBM VisualAge COBOL *
* *
* -- Remote Edit/Compile/Debug *
* *
* - IBM VisualAge PL/I *
* *
* -- Remote Edit/Compile/Debug *
* *
* This file is located in the MACROS directory under the main *
* product directory. *
* *
* This file must be modified to reflect your own individual *
* requirements. *
* *
* Note that any line in this file that starts with an asterisk (*) *
* will be treated as a comment. Blank lines will also be ignored. *
* Data entered in this file may be in upper or lower case. The data *
* will be converted to upper case when it is processed. *
* *
***********************************************************************
***********************************************************************
* *
* System specification: *
* *
* The following line, which starts with "system", specifies the name *
* of your MVS system as known to TCP/IP. If you are using the SdU *
* file system then the value is ignored (but it must have some *
* value). *
* *
* This line is required. *
* *
***********************************************************************
system mymvs.mycompany.com
***********************************************************************
* *
* Workstation specification: *
* *
* The following line, which starts with "worksys", specifies the name *
* of your workstation system as known to TCP/IP. *
* *
* This line is required, but reserved for future use, therefore *
* you should leave this line asis. *
* *
***********************************************************************
worksys reserved.for.future.use
***********************************************************************
* *
* UserID specification: *
* *
* The following line, which starts with "userid", specifies your *
* TSO userID on the above MVS system. *
* *
* This line is required. *
* *
***********************************************************************
userid myuser
***********************************************************************
* *
* Password specification: *
* *
* The following line, which starts with "pwd", specifies the password *
* (in encrypted form) for your TSO userID. The current encryption *
* alogorithm is as follows: *
* *
* - the letters A through Y map to the next letter in the alphabet *
* (e.g. L maps to M) *
* - the letter Z maps to the number 0 *
* - the numbers 0 through 8 map to the next higher number (e.g *
* 7 maps to 8) *
* - the number 9 maps to the letter A *
* - all other characters stay asis *
* *
* An easy way to look at the encryption is to note that every *
* character below is mapped to the character to its right. *
* *
* ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789A *
* *
* In the sample below the actual user password my9pwd is *
* encrypted to nzaqxe. *
* *
* To provide for additional security, you can specify the password *
* as ++++++++ (eight plus signs) followed by a blank and the *
* number 1 (the number 1 is for support of possible future function). *
* This will cause you to get prompted for a password for each *
* TSO command that is issued (note that the editing a file causes a *
* a TSO command to be issued to get data set/member information). *
* *
* This line is required. *
* *
***********************************************************************
pwd nzaqxe
***********************************************************************
* *
* File system specification: *
* *
* The following line, which starts with "filesys", specifies which *
* file system (NFS or SdU) is being used to access MVS data. *
* *
* After the file system name (nfs or sdu) you can optionally *
* specify "accessmon" which will automatically start the File System *
* Access Monitor when you start access to the MVS drives. The Access *
* Monitor will issue a trivial data request to MVS every 15 minutes *
* to prevent the file system server on MVS from timing out. *
* *
* After "accessmon" you can optionally specify "testaccess" which *
* will cause the connection to MVS to be automatically tested when *
* you start access to the MVS drives. If you want to specify *
* "testaccess" but do not want the access monitor started then *
* specify "noaccessmon" in place of "accessmon". *
* *
* This line is required. *
* *
***********************************************************************
filesys nfs accessmon testaccess
***********************************************************************
* *
* Network File System (NFS) read timeout specification: *
* *
* The following line, which starts with "readtimeout", specifies the *
* Network File System (NFS) readtimeout (and also attrtimeout) value *
* for drives that are mounted via NFS. *
* *
* This line is optional. If missing, the readtimeout and attrtimeout *
* attributes will be defaulted by NFS. *
* *
***********************************************************************
readtimeout 10
***********************************************************************
* *
* Network File System (NFS) write timeout specification: *
* *
* The following line, which starts with "writetimeout", specifies the *
* Network File System (NFS) writetimeout values for drives that are *
* mounted via NFS. *
* *
* This line is optional. If missing, the writetimeout attribute will *
* be defaulted by NFS. *
* *
***********************************************************************
writetimeout 10
***********************************************************************
* *
* Network File System (NFS) attributes specification: *
* *
* The following line, which starts with "nfs", specifies Network *
* File System (NFS) processing attributes for the drives that are *
* mounted via NFS. The possible attribute values are defined by NFS. *
* Missing values will be assigned a default value by NFS. You should *
* not specify the high level qualifier, text, binary, end-of-line *
* (such as crlf), read timeout, attribute timeout, write timeout *
* or name mapping attributes. These additional NFS attributes are *
* determined either automatically based on the specification for *
* the MVS drives (lines in this file that start with "drive") or *
* determined by the readtimeout and writetimeout specification in *
* this file. *
* *
* This line is optional. If missing, all processing attribute values *
* other than high level qualifier, text, binary, crlf, readtimeout, *
* attrtimeout, writetimeout, and name mapping will be defaulted by *
* NFS. *
* *
***********************************************************************
nfs
***********************************************************************
* *
* Smart Data Utilties (SdU) attributes specification: *
* *
* The following line, which starts with "sdu", specifies Smart Data *
* Utilities (SdU) processing attributes for the drives that are *
* mounted via SdU. The possible attribute values are defined by SdU. *
* Missing values will be assigned a default value by SdU. *
* *
* This line is optional. If missing, all processing attribute values *
* other that high level qualifier will be defaulted by SdU. *
* *
***********************************************************************
sdu pc_ccsid(850)
***********************************************************************
* *
* Drives specification: *
* *
* The following line(s), which start with "drive", specify one or *
* more drives that reference your MVS data sets. One drive is *
* needed for each data set high level qualifier that you will *
* access from the workstation. Data sets that are only referenced *
* by submitted batch jobs do not require a drive. The drive letter *
* must not already be in use for other purposes (for example do not *
* use c:, which is usually the system boot drive). *
* *
* The format of the drive specification is: *
* *
* drive drive_letter: high_level_qualifier text|binary mapping *
* *
* where: *
* *
* text or binary indicate whether the data is text and therefore *
* requires translation between EBCDIC on the host and ASCII on the *
* workstation or whether the data is binary and will not be *
* translated. If the text or binary specification is omitted, text *
* is assumed. To access data for the same high level qualifier as *
* both text and binary requires two drives, one for each. *
* *
* Note that the high_level_qualifier can specified one or two MVS *
* data set name qualifier, as for example MYUSER (one MVS qualifier) *
* or MYUSER.MYPROJ (two MVS qualifiers). *
* *
* mapping indicates the type of name mapping between MVS member names *
* and workstation file names. The following mapping specifications *
* may be given: *
* *
* local - mapping is done locally based on the type specifications *
* (see below for details) in this file. *
* *
* filesys - mapping is done by the file system (NFS only) using the *
* default name mapping file. If there is no default name *
* mapping file then name mapping is not performed. *
* Note that not all releases of the MVS Network File *
* System (NFS) server support file system name mapping. *
* name mapping. Check with your system programmer to *
* determine whether your have the required NFS release. *
* *
* filesys dsname - mapping is done by the file system (NFS only) *
* using the specified user name mapping data set. *
* *
* If the name mapping specification is omitted then local is *
* assumed. *
* *
* To use the File System Access Monitor you need to specify a drive *
* (text or binary) for the high level qualifier of the SIGYCLST *
* data set. The sample below shows this as the v: drive. Note *
* that this drive must specify only a single MVS data set name *
* qualifier. *
* *
*drive v: igy text local *
*drive w: myuser text filesys myuser.nfs.mapping *
*drive y: myuser binary local *
*drive z: myuser text local *
* *
***********************************************************************
* DO NOT CHANGE THE NEXT LINE THAT SAYS drives placeholder
* drives placeholder
***********************************************************************
* *
* Local types mapping specification: *
* *
* The following line(s), which start with "type", specify the local *
* association of a data set low level qualifier with the *
* corresponding extension used for workstation files. The local *
* mappings are ignored if NFS mapping is being used for the drive. *
* *
* The following extensions have special meaning: *
* *
* CBL - COBOL source (input to the COBOL compiler) *
* CPY - COBOL copy file (used by the COBOL COPY statement) *
* PLI - PL/I source (input to the PL/I compiler) *
* OBJ - object code (input to the linkage editor) *
* EXE - load module (output of the linkage editor) *
* CMD - CLIST or REXX procedure *
* JCL - MVS job control language (JCL) used for batch job submission *
* LST - compilation or link edit listing *
* ADT - Compilation ADATA (SYSADATA) *
* PPR - Preprocessor output *
* OUT - MVS job SYSOUT output *
* *
* The specified extension will be used to determine the language *
* sensitive editing for the data set (there is language sensitive *
* editing for CBL, CPY, CMD and JCL). It will also be used to *
* determine whether certain actions are valid, as for example a *
* compile action is only valid for data sets with an extension of *
* CBL. Files with an extension of OBJ, EXE, LST, ADT, PPR, or OUT *
* are set to readonly when editing. *
* *
* These lines are required if you are using local name mapping and *
* you want to use either language sensitive editing or project *
* actions that are dependent on the type of data set. *
* *
* *
***********************************************************************
type cobol cbl
type cobcopy cpy
type pli pli
type obj obj
type load exe
type clist cmd
type sigyclst cmd
type cntl jcl
type listing lst
type outlist out
***********************************************************************
* *
* SIGYCLST specification: *
* *
* The following line, which starts with "sigyclst", specifies the *
* fully qualified name of the SIGYCLST data set on MVS. *
* *
* This line is required. *
* *
***********************************************************************
sigyclst igy.v2r1m0.sigyclst
***********************************************************************
* *
* SYSPROC specification: *
* *
* The following line, which starts with "sysproc", specifies the *
* name of the data sets that are to be allocated to SYSPROC when *
* executing command procedures on MVS/TSO. A specification of an *
* asterisk (*) for a data set is interpreted as being the above *
* mentioned SIGYCLST data set. To allow executing the IBM supplied *
* command procedures you must include the asterisk (*) as one of the *
* SYSPROC data sets. If you have your own SYSPROC data sets, then *
* where you place the * for the SIGYCLST data set will determine *
* its order within the SYSPROC concatenation. *
* *
* This line is required. *
* *
***********************************************************************
sysproc *
***********************************************************************
* *
* Temporary data set drive specification: *
* *
* The following line, which starts with "tempdata", specifies the *
* drive to be used for temporary data sets required by certain *
* operations, as for example the temporary sequential data set used *
* for protected saves. If the high level qualifier for the drive *
* specifies a single MVS data set qualifier then temporary data sets *
* will have as their high level qualifiers mvsqual.IWZ where mvsqual *
* is the single MVS data set qualifier specified. If the high level *
* qualifier for the drive specifies two MVS data set qualifiers then *
* temporary data sets will have as their high level qualifier the *
* specified two MVS data set qualifiers. The specified drive must *
* have a usage of text. *
* *
* This line is optional. If missing, temporary data sets will be *
* created on the first drive with a high level qualifier equal to *
* the userid and with a usage of text. The temporary data sets will *
* have as their high level qualifiers userid.IWZ. *
* *
***********************************************************************
*tempdata z:
***********************************************************************
* *
* Temporary drive specification: *
* *
* The following line, which starts with "tempdrive", specifies the *
* temporary drive be used for Redeveloper functions that copy *
* files from the MVS host to the workstation. *
* *
* This line is optional. If missing, a temporary drive will be *
* chosen as the first available drive letter from c: through z:. *
* *
***********************************************************************
*tempdrive g:
***********************************************************************
* *
* File system requests specification: *
* *
* The following lines, which start with "fsstartcmd", "fsstopcmd", *
* "mountcmd", and "umountcmd" specify user defined command for *
* starting the file system, stopping the file system, mounting a *
* drive and unmounting a drive functions respectively. *
* *
* The command specification consists of characters to appear as is *
* (unlike other data in the MVSINFO.DAT file, these characters are *
* not converted to uppercase for processing, this is to allow for *
* commands whose input parameters are case sensitive) and *
* substitution variables of the form &*varname. where varname *
* is one of the following: *
* *
* system - the system specification from this file *
* userid - the userid specification from this file *
* pwd - the pwd specification from this file *
* nfs - the nfs specification from this file *
* sdu - the sdu specification from this file *
* user1 - user data specification from this file (add a line that *
* starts with user1) *
* user2 - user data specification from this file (add a line that *
* starts with user2) *
* user3 - user data specification from this file (add a line that *
* starts with user3) *
* user4 - user data specification from this file (add a line that *
* starts with user4) *
* *
* For mount and unmount functions the following variables may also *
* be used: *
* *
* readtimeout - the readtimeout specification from this file *
* writetimeout - the writetimeout specification from this file *
* timeout - the readtimeout and writetimeout specifications in the *
* NFS format ,readtimeout(nn),attrtimeout(nn),writetimeout(nn) *
* drive - the drive letter followed by a colon (e.g. Z:) *
* trans - the drive translation in the NFS format (e.g. text,crlf or *
* binary) *
* nfsmap - the name mapping specification in NFS format *
* ,fileextmap or ,fileextmap,sidefile(dsname) *
* *
* To get all the NFS attributes that are normally generated you can *
* specify the following in your mount command: *
* *
* &*highqual.,&*trans.&*nfsmap.,nofastfilesize&*timeout.&*nfs. *
* *
* An example of a user mount command would be: *
* *
* usermnt.exe drive(&*drive.) user(&*userid.) qual(&*highqual.) *
* *
* which when executed might generate: *
* *
* usermnt.exe drive(Z:) user(MYUSER) QUAL(SYS1) *
* *
* If you want to invoke a REXX procedure to perform the functions *
* then specify the command in the following format: *
* *
* cmd.exe /c procname.cmd parameters (this is for OS/2) *
* rexx procname.cmd parameters (this is for Windows NT) *
* *
* where procname is the filename (less the extension) of the REXX *
* procedure and parameters are any optional parameters to be passed *
* to the REXX procedure. An example for Windows is: *
* *
* rexx mymount.cmd &*.drive. &*trans. &*nfsmap. *
* *
* These lines are optional. If missing, or if the cammand is *
* specified as an asterisk (*) then the system supplied default *
* command will be used for the given function. *
* *
***********************************************************************
fsstartcmd *
fsstopcmd *
mountcmd *
umountcmd *
***********************************************************************
* *
* Protected save specification: *
* *
* The following line, which starts with "protsave", specifies that *
* the editor is to use the protected save mechanism when saving a *
* partitioned data set member (either PDS or PDSE). Use of the *
* protected save mechanism causes the actual update of the member *
* to occur by using the IEBGENER MVS utility, thus using the same *
* data management as that of an ISPF editor save. In particular, *
* this means that if the save fails, as for example due to lack of *
* space (x37 abends), then the original contents of the member *
* before the save will be preserved. *
* *
* When using the protected save mechanim the contents of the file *
* are first saved to a temporary sequential data set on MVS. By *
* default this data set is allocated with a space allocation at *
* least 10,000 lines more than the current size of the member. *
* If you want the temporary data set to be larger you can specify *
* a multiplier value after the keyword "yes" (the value must be *
* an integer). For example, a multiplier value of 5 will allow *
* for a space allocation of at least 50,000 lines more than the *
* current size of the member. If the multiplier value is missing, *
* a value of 1 is assumed. *
* *
* If protected save is disabled ("protsave no" was explicitly *
* specified) then if a save fails for a partitioned data set member, *
* the member contents may be partial (the original contents are *
* lost). Therefore, even though the protected save mechanism *
* takes longer, it is highly recommended that it not be disabled. *
* *
* The protected save processing is not done when saving via *
* "Save as", as it is assumed that the original contents of the *
* "Save as" location are no longer required. *
* *
* This line is optional. If missing, the protected save processing *
* will be performed for partitioned data set members. It can only *
* be turned off by explicitly specifying "protsave no". *
* *
***********************************************************************
protsave yes 1
***********************************************************************
* *
* Close file specification: *
* *
* The following line, which starts with "closefile", specifies *
* whether your MVS Network File System (NFS) server has the support *
* for doing an immediate close of a file on MVS. This support allows *
* for closing a file without the need to wait for the appropriate *
* timeout value to expire, thus providing a fater means of freeing *
* a file for direct use on MVS. Note that support for doing an *
* immediate close of a file on MVS is available only on those *
* releases of the NFS server that support the file system name *
* mapping. Check with your system programmer to determine whether *
* you have the required NFS release. *
* *
* This line is optional. If missing, instead of doing a immediate *
* close of a file on MVS, a wait will be done for the appropriate *
* timeout value. *
* *
***********************************************************************
closefile no
***********************************************************************
* *
* High performance MVS commands specification: *
* *
* The following line, which starts with "mvscomm", specifies whether *
* the high performance MVS commands facility supplied with this *
* product should be used instead of the TCP/IP supplied REXEC and *
* RSH commands. This support is only available when using the NFS *
* file system. See the Getting Started publication for information *
* on required MVS setup. *
* *
* This line is optional. If missing, the normal TCP/IP supplied *
* REXEC or RSH commands will be used to issue TSO commands. *
* *
***********************************************************************
mvscomm no
***********************************************************************
* *
* REXEC/RSH header lines specification: *
* *
* The following line, which starts with "header", specifies whether *
* extra processing needs to be performed to remove system header *
* lines that may be placed at the start of REXEC/RSH output before *
* the actual output of the TSO command. Examples of such lines *
* may be accounting or security information. If your MVS system *
* produces such lines you need to specify "yes" as the parameter *
* following "header". Note that this extra processing may affect *
* performance. The implementation also causes the length of the *
* TSO commands to be increased. *
* *
* This line is optional. If missing, the extra processing will be *
* done to remove REXEC/RSH header lines. *
* *
***********************************************************************
*header no
***********************************************************************
* *
* Maximum command length supported specification: *
* *
* The following line, which starts with "maxcmd", specifies the *
* maximum length of a TSO command which is supported by the *
* combination of your client (REXEC or SdU client on OS/2 and *
* RSH client on Windows NT) and the REXEC server on MVS. *
* A limit less than 72 is not supported (it is highly unlikely *
* that the actual limit will be less than 80). If a TSO command *
* exceeds the limit then extra processing will be required. This *
* extra processing requires that you have a drive defined for text *
* usage with your TSO userID as the high level qualifier. As the *
* extra processing includes copying the TSO command to a sequential *
* data set on MVS, it is also required that you have connected to *
* the MVS drives. *
* *
* This line is optional. If missing, it will be assumed that your *
* client/server combination can support the same command length *
* limit as TSO itself. *
* *
***********************************************************************
*maxcmd 240
***********************************************************************
* *
* Test data file specification: *
* *
* The following line, which starts with "testfile", specifies the *
* fully qualified name of either a physical sequential file or a *
* PDS member that is to be accessed by the Test MVS connection *
* action. The data set should have fixed 80 byte records (RECFM or *
* F or FB). The data set (or member) contents may be anything. *
* The contents are displayed as part of the testing. *
* *
* This line is optional. If missing, the Test MVS connection action *
* will be limited to issuing the TSO TIME command and getting the *
* attributes for the MVS system data set SYS1.MACLIB member OPEN. *
* *
***********************************************************************
*testfile myuser.testfile.data(testdata)
***********************************************************************
* *
* Null stdin for RSH specification: *
* *
* Note: nullstdin yes is now assumed for Windows systems. It no *
* longer needs to be specified. *
* *
***********************************************************************
trace 3
***********************************************************************
* *
* ---- End of File ---- *
* *
***********************************************************************
