How can I locate VISION:Builder or VISION:Two
search cancel

How can I locate VISION:Builder or VISION:Two


Article ID: 31099


Updated On:


Vision:Builder Vision:Two



How can I tell if VISION:Builder or VISION:Two is used at my site?



There are times when VISION:Builder or VISION:Two (formally known as MARK IV and Answer/2) customers are not sure if the products are still being actively utilized within their Enterprise Server environment.  The following information can be used to locate and/or determine if VISION:Builder or VISION:Two is part of their environment. 

The first place to look is in the Job Control Language (JCL) libraries and members that contain the jobs that are running at the customer’s location.  This includes the Cataloged JCL Procedures Libraries. 

The primary indicators to scan for in the JCL to identify Builder jobs are as follows:

  •          In z/OS environments, the DD statement names “M4LIB” and “M4INPUT” will indicate that the job step is a VISION:Builder or VISION:Two run.  The DD names of “M4LIB” and “M4INPUT” must be present in every processing step that runs VISION:Builder or VISION:Two.
  •          In VSE environments, look for a DLBL control statement that uses the DTF name of M4LIB.  In some cases the DLBL statement will be included in the Partition Standard and/or System Standard Label Areas.
  •          The standard program name on the EXEC statements within the JCL is “MARKIV”.
  •          For IMS / DLI data base job steps, the program name will be coded as a PARM on the EXEC statement or coded as a parameter in the data base control statements input to the application runs.  The names MARKDLI, MARKDLIX, and MARKDLS are used to execute VISION:Builder or VISION:Two.
  •          For DB2 relational data base job steps, the executed program name depends on which attach facility is used.  The Call Attach would execute MARKIV.  The IMS Attach would use the program name of MARKDLI in the control statement input at the DDITV02 DD statement.  The TSO Attach would use the program name MARKIV in the RUN control statement input at the SYSTSIN DD statement.  In the VSE environment, Multiple User Mode would execute MARKIV and Single User Mode would execute MARKSQI or MARKSQS.

Once the JCL is identified, the System Load (or Program) Libraries can be located.

  •          In z/OS environments, the JOBLIB, STEPLIB or Link List DD statements will contain references to Load Libraries.  The product software will be stored in a Load Library.
  •          In VSE environments, there will be LIBDEF statements using the PHASE and SEARCH entries to reference the VSE Sublibraries that will contain the product software.  Remember, in VSE, these LIBDEF statements may exist in the Partition Standard and/or System Standard Label Areas.

In the Load Libraries or Sublibraries, there are some member names that will identify the VISION:Builder or VISION:Two software.  Of course, the module named MARKIV is the definite indicator.  There are also many other modules which have names that start with “MARK”.

There is also a module named M4PARAMS that is used by customers to tailor their VISION:Builder or VISION:Two system to specific location requirements.  There is a release number identifier in the M4PARAMS module.  By browsing the M4PARAMS module and looking at the last record, position 33, the software release number can be read.  For example, 15.0, 14.0. 13.7, 10.1.

Finally, at some locations, the Systems Group may be able to scan the SMF Records or the equivalent to determine if the program name “MARKIV” was executed.  The associated information about the job or user could help identify where the product is located.

With the various methods described above, you should be able to locate and identify the extent to which the VISION:Builder or VISION:Two product is utilized in your Enterprise Server environment. 


Component: V:BLDR