Application Properties  Source Code Reference & Management Information http://www.simotime.com

Introduction
(Next) (Previous) (Table-of-Contents)

The suite of programs provides the capability of creating and managing a repository of information or "Application Properties Repository" for the source code used by a mainframe application or group of applications. This information can be quite useful when supporting applications or migrating applications and data between a Mainframe System and a Linux, UNIX or Windows (LUW) System using Micro Focus technologies. This suite of programs (referred to as APMAST01) runs on a personal computer with Microsoft Windows (Windows/XP or later) and Micro Focus (Net Express 5.1 or later).

The information obtained from the source code scanning functionality provided by the SImoLYZE Utility Program (a separate package) will be used to initially create and/or update a repository (a Micro Focus Key-Sequenced-Data-Set or Indexed File) that contains application properties and management information. This data base will be referred to as the "Application Properties Repository" (or APMASTER) . This suite of programs is provided as an add-on or plug-in for the SimoLYZE Utility Program. The suite includes programs that will read the APMASTER and create various reports, listings, scripts and other information as described in the following sections of this document.

The source code, data sets and documentation are provided in a single zipped file called APMAST01.ZIP. This zipped file may be downloaded from the SimoTime Web site. This example illustrates the following functions.

Purpose and Prerequisites
(Next) (Previous) (Table-of-Contents)

The purpose of this suite of programs is to assist in the defining of the scope of effort by providing information about the size and properties of the source members that are used in the building of a production application. When performing a task that requires an application change and/or redeployment a certian minimum level of information is required to determine the size and effort required. The following table list some of the items that provide this information.

The suite of programs uses Micro Focus COBOL and Windows Command files. The programs are unit tested with Micro Focus Net Express, version 5.1. The COBOL source code is included with the software package and may be compiled and executed on other versions of Micro Focus COBOL running on Linux, UNIX or Windows (LUW) platforms. The full program or system testing is done on a Windows/XP system using Micro Focus Studio, Enterprise Edition. Many of the programs are deployed on various LUW platforms using Micro Focus Server, Enterprise Edition.

Quick Start
(Next) (Previous) (Table-of-Contents)

This following sections describe the process for creating a repository for source member properties.

Quick Start, Download the Source Code to a Windows System
(Next) (Previous) (Table-of-Contents)

Source code is usually stored in Partitioned data sets or a Source Code Repository that is managed by a source code management system. The actual source code is usually a sequential file of 80-byte, fixed length records an EBCDIC format. The most common method used to transfer source code is the File Transfer Protocol (or FTP). The Mainframe Source Code is usually 80-byte, EBCDIC-encoded text strings and the FTP process in ASCII mode will convert the files to ASCII/Text files during the download process. The ASCII/Text format is the format of choice for source code on a Windows System. On rare occasions there may be embedded hexadecimal bytes embedded in the source code. These will require special handling. Refer to the  Data File Transfer  document for detailed information about the various file transfer alternatives available.

Quick Start, Create a Repository of Source Member Properties
(Next) (Previous) (Table-of-Contents)

Once the source code is downloaded into a directory on the Windows System the SImoLYZE program is used to scan the source members and determine the member type (i.e. COBOL, copy file, JCL, BMS, etc.) and the member information is stored in the Application Properties Repository (APMASTER.DAT). Refer to the  SimoLYZE Source Member Typing  document for a detailed description of member typing and building an application properties repository of information.

Quick Start, Create HTML Documentation
(Next) (Previous) (Table-of-Contents)

This job (APHTMLE1.CMD) will access the Application Properties Repository (APMASTER.DAT) and create an HTML Document.

Quick Start, Do a Scripted BMS Generation
(Next) (Previous) (Table-of-Contents)

The BMS Generation should alway be done prior to doing the COBOL compiles for the online CICS Programs. This is required because the BMS Generation process creates COBOL copy files that are used during the COBOL compile process. Doing the BMS Generation is a two (2) step process. The 1st step is to create the list of member names in an ASCII/Text file. To do this run the following command.

C:\SimoSam1\Adm1>PrepareListSam1BmsCics01

The 2nd step will use the list file just created and do the BMS Generation that creates the COBOL copy file and the Load Member for the BMS Maps (or screens). To do this run the following command.

C:\SimoSam1\Adm1>aaGenerateBMSascForSam1Online

For addition detail about the BMS Generation process refer to the Technical Details, Command Files, Prepare and Execute a Scripted BMS Generation section of this document.

Quick Start, Create COBOL Source Member Lists by Category
(Next) (Previous) (Table-of-Contents)

In this sample suite of programs there are four categories of COBOL Source Members.

C:\SimoSam1\Adm1>CreateListSam1BmsCics01

Quick Start, Do a Scripted Compile of COBOL Members
(Next) (Previous) (Table-of-Contents)

WIP...

This job (APLISTC4.CMD) will access the Application Properties Repository (APMASTER.DAT) and create four files (or listings) containing COBOL Source Code Member names. The listing files are created based on the properties of the COBOL source members. The four categories of programs are as follows.

The lists are then used within scripted processes to do the COBOL Compiles.

Record Structure for the Application Properties Repository
(Next) (Previous) (Table-of-Contents)

The following COBOL copy file (APMASTB1.CPY) shows the record structure for the Application Properties Repository or APMASTER.DAT. The record structure is Fixed Field Length (FFL) format.

      *****************************************************************
      *      Copy File for the Application Properties Repository      *
      *      This is a VSAM Keyed Sequence Data Structure (KSDS)      *
      *              or a Micro Focus Keyed-Index File.               *
      *****************************************************************
      *         Copyright (C) 1987-2010 SimoTime Enterprises          *
      *                     All Rights Reserved                       *
      *****************************************************************
      *              Provided by SimoTime Enterprises                 *
      *        Our e-mail address is: helpdesk@simotime.com           *
      *     Also, visit our Web Site at http://www.simotime.com       *
      *****************************************************************
       01  APMASTER-RECORD.
           05  APMASTER-KEY.
               10  APMASTER-KEY-16             PIC X(16).
               10  APMASTER-RECORD-ID          PIC 9(2).
           05  APMASTER-DATA.
               10  APMASTER-RECORD-STATUS      PIC X.
               10  APMASTER-LAST-ACTIVITY-DATE PIC X(8).
               10  APMASTER-LAST-ACTIVITY-TIME PIC X(8).
               10  APMASTER-MEMBER-DATE        PIC X(8).
               10  APMASTER-MEMBER-TIME        PIC X(8).
               10  APMASTER-LANGUAGE           PIC X(8).
               10  APMASTER-LANGUAGE-USER      PIC X(8).
               10  APMASTER-LANGUAGE-MFA       PIC X(8).
               10  APMASTER-TYPE               PIC X(8).
               10  APMASTER-TYPE-USER          PIC X(8).
               10  APMASTER-TYPE-MFA           PIC X(8).
               10  APMASTER-CICS               PIC X.
               10  APMASTER-CICS-USER          PIC X.
               10  APMASTER-CICS-MFA           PIC X.
               10  APMASTER-SQL                PIC X.
               10  APMASTER-SQL-USER           PIC X.
               10  APMASTER-SQL-MFA            PIC X.
               10  APMASTER-FLAGS.
                   15  APMASTER-FLAG-01        PIC X.
                   15  APMASTER-FLAG-02        PIC X.
                   15  APMASTER-FLAG-03        PIC X.
                   15  APMASTER-FLAG-04        PIC X.
                   15  APMASTER-FLAG-05        PIC X.
                   15  APMASTER-FLAG-06        PIC X.
                   15  APMASTER-FLAG-07        PIC X.
                   15  APMASTER-FLAG-08        PIC X.
               10  APMASTER-FLAGS-USER.
                   15  APMASTER-FLAG-U1        PIC X.
                   15  APMASTER-FLAG-U2        PIC X.
                   15  APMASTER-FLAG-U3        PIC X.
                   15  APMASTER-FLAG-U4        PIC X.
                   15  APMASTER-FLAG-U5        PIC X.
                   15  APMASTER-FLAG-U6        PIC X.
                   15  APMASTER-FLAG-U7        PIC X.
                   15  APMASTER-FLAG-U8        PIC X.
               10  APMASTER-RECORDS            PIC 9(8).
               10  APMASTER-BLANK-LINES        PIC 9(8).
               10  APMASTER-COMMENTS           PIC 9(8).
               10  APMASTER-LINES-OF-CODE      PIC 9(8).
               10  APMASTER-FILLER-00          PIC X(70).
               10  APMASTER-ACCUMULATORS.
                   15  APMASTER-ACCUMULATE-01  PIC 9(7).
                   15  APMASTER-ACCUMULATE-02  PIC 9(7).
                   15  APMASTER-ACCUMULATE-03  PIC 9(7).
                   15  APMASTER-ACCUMULATE-04  PIC 9(7).
                   15  APMASTER-ACCUMULATE-05  PIC 9(7).
                   15  APMASTER-ACCUMULATE-06  PIC 9(7).
                   15  APMASTER-ACCUMULATE-07  PIC 9(7).
               10  APMASTER-MVS-MEMBER-NAME    PIC X(16).
               10  APMASTER-PCNAME             PIC X(256).
               10  APMASTER-MAKEACTION         PIC X(224).
               10  APMASTER-HOSTNAME           PIC X(256).
      *    End of APMASTB1.CPY

Ancillary Tasks
(Next) (Previous) (Table-of-Contents)

This section provides technical detail about the supporting scripts and programs used or called by the primary jobs.

Ancillary Function, Setting the Environment
(Next) (Previous) (Table-of-Contents)

A command file (ezSetEnv.CMD located in the sub-directory named ProdLibA) is called from other command files to set commonly used environment variables. This provides a single point of definition. The following is a listing of the contents of the command file.

rem  * *******************************************************************
rem  * Set the commonly used environment variables. This is used to
rem  * provide a single point for managing the commonly used environment
rem  * variables.
rem  *
     set BaseLib1=c:\SimoSAM1
rem  *
rem  * The following two (2) statements are required when Hyperlinking from
rem  * an Excel Spreadsheet.
     c:
     cd %BaseLib1%\ProdLibA
rem  *
     set SYSOUT=%BaseLib1%\LOGS\SYSOUT_USER.TXT
     set SYSLOG=%BaseLib1%\LOGS\SYSLOG_USER.DAT
     set SimoNOTE=%BaseLib1%\LOGS\SIMONOTE_USER.TXT
     set DataLib1=%BaseLib1%\DataLibA
     call SimoNOTE "*"
if   "%1" == "" goto :NoHeader
     call SimoNOTE "**********************************************ezSetEnv/%1"
:NoHeader
rem  *
     set LRSTOKEN=%DataLib1%\Txt1\LRSTOKEN.TXT
     set CobCpy=%BaseLib1%\CobCpy1;c:\SimoLIBR
rem  *
rem  set MAINFRAME_FLOATING_POINT=true
rem  *
rem  * set MFTRACE_CONFIG=%BaseLib1%\LOGS\TRACE001\ctfrtsfs.cfg
rem  * set MFTRACE_LOGS=%BaseLib1%\LOGS\TRACE001
rem  *
rem  * The following SORTSPACE of 1 gigabyte is used when sorting very
rem  * large files. The value is the digit one (1) followed by nine (9)
rem  * zeroes. To allocate this amount of memory for sorting requires a
rem  * minimum of two (2) gigabytes of RAM.
rem  set SORTSPACE=1000000000
rem  *
rem  * For large file support and record locking control of File Handler
     set EXTFH=%BaseLib1%\SysLibA1\EXTFH4AE.CFG
rem  * Set environment for MFBSI (Micro Focus Batch Scheduling Interface)
     set ES_EMP_EXIT_1=mfbsiemx
     set MFBSI_DIR=%BaseLib1%\BSIA\%ezServerName%
     set MFBSIEOP_CMD=ENABLE
     set MFBSIEOP_CSV=ENABLE
     set MFBSIEOP_HTM=ENABLE
     set MFBSIEOP_XML=ENABLE
rem  *
rem  * The following is used to map the location of files that are to be
rem  * allocated using JCL with ES/MTO.
     set ES_ALLOC_OVERRIDE=%BaseLib1%\SysLibA1\CatMapA1.cfg
rem  *
rem  * Set the environment for Core Dump on System error, CBLCORE file
rem  set COBCONFIG_=%BaseLib1%\SysLibA1\Diagnose.CFG
     set COBCONFIG_=
rem  *
rem  * The following may need to be adjusted based on individual systems
rem  * and the various versions of the Operating System, Sub-Systems and
rem  * other software.
     if "%ezSetEnv%" == "Y" goto :NOPATH
     set iexplore=C:\Program Files\Internet Explorer
     set path="C:\Program Files\Micro Focus\Net Express 5.1\Base\";"C:\Program Files\Micro Focus\Net Express 5.1\Base\bin";%BaseLib1%\ProdLibA;%BaseLib1%\ProdLibA\UTIL;%PATH%;
rem  set path="C:\Program Files\Micro Focus\Server 5.0\Base\";"C:\Program Files\Micro Focus\Server 5.0\Base\bin";%PATH%;
:NOPATH
     set cobpath=%BaseLib1%\ProdLibA;%BaseLib1%\ProdLibA\UTIL;c:\SimoLIBR
     set JobStatus=0000
     set StepStatus=0000
     set ezSetEnv=Y
     call SimoNOTE "* BaseLib1 is %BaseLib1%"

Ancillary Function, Displaying and Logging Messages
(Next) (Previous) (Table-of-Contents)

The following (SimoNOTE.CMD) is a listing of the contents of the SimoNOTE.CMD command file.

@echo OFF
rem  * *******************************************************************
rem  *                   This program is provided by:                    *
rem  *                    SimoTime Enterprises, LLC                      *
rem  *           (C) Copyright 1987-2010 All Rights Reserved             *
rem  *             Web Site URL:   http://www.simotime.com               *
rem  *                   e-mail:   helpdesk@simotime.com                 *
rem  * *******************************************************************
rem  *
rem  * Text    - Display message on screen and write to a log file.
rem  * Author  - SimoTime Enterprises
rem  *
rem  * This script may be called from other scripts and expects a
rem  * single parameter enclosed in double quotes. The double quotes
rem  * will be removed. Before writing to the log file a date and time
rem  * stamp will be inserted in front of the message text.
rem  *
rem  * Note: The tilde (~) removes leading/trailing double-quotes.
rem  *
if "%SimoNOTE%" == "" set SimoNOTE=c:\SimoLIBR\LOGS\SimoTime.LOG
echo %date% %time% %~1>> %SimoNOTE%
echo %~1

Technical Details
(Next) (Previous) (Table-of-Contents)

This section provides a technical overview of the job scripts and programs used by the ...

Technical Details, Command Files
(Next) (Previous) (Table-of-Contents)

This section describes some of the Windows Command files used in the processes associated with managing the Application Properties Repository and doing scripted builds of the applications.

Technical Details, Command Files, Create HTML Document
(Next) (Previous) (Table-of-Contents)

WIP...

The following (APHTMLE1.CMD) is the source listing for the CMD file that creates the HTML Documentation.

Technical Details, Command Files, Prepare and Execute a BMS Generation
(Next) (Previous) (Table-of-Contents)

The scripted BMS Generation for multiple BMS Members uses a "List of Member Names" stored in an ASCII/Text file. Once the list is created a Windows Command File with a "FOR" loop will access the List of Member Names and execute the BMS Generation process for each BMS member.

Technical Details, Command Files, Create a List of BMS Members
(Next) (Previous) (Table-of-Contents)

Creating an ASCII/Text file with a list of BMS Member names can be done maually using a file editor such as Microsoft NotePad. The BMS Member name is the 8-byte (or less) member name without a file extension. Doing this manually may be a good choice for a small number of BMS Members.

However, when there is a large number of BMS Members an automated process may be a better alternative. If the SimoLYZE function was used to do member typing and create an Application Properties Repository a command script and a program are provided to create a BMS Member list. This sample script (CreateListSam1BmsCics01.CMD) will access the Application Properties Repository (APMASTER.DAT) and create a list of BMS member names. The following shows the Windows command script.

@echo OFF
rem  * ************************************************************************
rem  * This procedure calls the following Windows Command Files or Programs.
rem  * 1. Env1Base.CMD - this provides a single point for setting commonly
rem  *                   used environment variables.
rem  * 2. SimoNOTE.CMD - this provides a consistent process for displaying
rem  *                   messages to the screen and writing to a journal or
rem  *                   log file.
rem  * 3. APLISTC3     - this utility program will create a list file without
rem  *                   the extension on the file name.
rem  * ************************************************************************
     setlocal
     call ..\Env1Base
     set CmdName=CreateListSam1BmsCics01
rem  *
     call SimoNOTE "*******************************************************%CmdName%.CMD"
     call SimoNOTE "Starting JobName %CmdName%.CMD"
rem  *
rem  * Set the environment variables for the selection criteria.
rem  *
     set APMEMLANG=370
     set APMEMTYPE=BMS
     set APCICSSTAT=*
     set APSQLSTAT=*
rem  *
rem  * Set the environment variables for file name mapping,
rem  * execute the select and extract program.
rem  *
     set APMASTER=%BaseLib1%\DataLibA\Dyn1\SIMOTIME.UTIL.APMASTER.DAT
     set APLIST03=%BaseLib1%\DataLibA\Wrk1\SIMOTIME.UTIL.BMSNAMES.LST
     run APLISTC3
rem  *
     call SimoNOTE "Finished JobName %CmdName%.CMD"
     if not "%SimoGENS%" == "BATCH" pause
     endlocal

Technical Details, Command Files, Scripted BMS Generation
(Next) (Previous) (Table-of-Contents)

This sample job (aaGenerateBMSascForSam1Online.CMD) will read the list of BMS Source Member names and use a Windows "FOR" loop to Generate a BMS Load Member and a BMS Copy File for each BMS member. This script will call a second command file (ezBmsGeneration.CMD) to do the actual BMS Generation. The following is the content of the two command file.

@echo OFF
rem  * ************************************************************************
rem  * This procedure calls the following Windows Command Files.
rem  * 1. Env1Base.CMD - this provides a single point for setting commonly
rem  *                   used environment variables.
rem  * 2. SimoNOTE.CMD - this provides a consistent process for displaying
rem  *                   messages to the screen and writing to a journal or
rem  *                   log file.
rem  * 3. ezBmsGeneration.CMD
rem  *                 - this will do the actual generation of the
rem  *                   specified member.
rem  * ************************************************************************
     setlocal
     call ..\Env1Base
     set CmdName=aaGenerateBMSascForSam1Online
rem  *
     call SimoNOTE "****************************************%CmdName%.CMD"
     call SimoNOTE "Starting JobName %CmdName%.CMD"
rem  *
rem  * Read the file containing BMS Member names and pass the contents of each
rem  * record to the command file that does the actual generation. Each record
rem  * in the file contains an eight character member name. The following
rem  * parameters are passed to the called command file.
rem  * Parameter  Description
rem  * ---------  ------------------------------------------------------------
rem  *    1       Name of BMS source member
rem  *    2       Name of BMS source directory relative to BaseLib1
rem  *    3       Name of directory for BMS load member relative to BaseLib1
rem  *
     set AOK_Count=0
     set NOK_Count=0
     for /F %%i in (SIMOTIME.UTIL.BMSNAMES.LST) do CALL ezBmsGeneration %%i BMS StagLibA
rem  *
     call SimoNOTE "AOKcount Generate Count for AOK is %AOK_Count% "
     call SimoNOTE "NOKcount Generate Count for NOK is %NOK_Count% "
     call SimoNOTE "Finished JobName %CmdName%.CMD"
     if not "%SimoGENS%" == "BATCH" pause
     endlocal

This preceding job (or script) calls a second command file (ezBmsGeneration.CMD) to do the actual BMS Generation. The following is the content of the second command file.

@echo OFF
     set BMSgenerateStatus=0000
rem  *
rem  * It is the caller's responsibility to set BaseLib1 environment variable
rem  * to the base directory. This procedure uses various sub-directories
rem  * under the base directory.
rem  *
rem  * The following parameters are received from the calling command file.
rem  * Parameter  Description
rem  * ---------  ------------------------------------------------------------
rem  *    1       Name of BMS source member
rem  *    2       Name of BMS source directory relative to BaseLib1
rem  *    3       Name of directory for BMS load member relative to BaseLib1
rem  *    Note    The COBOL copy file will be written to the CobCpy6
rem  *            sub-directory under the BaseLib1 directory.
rem  *
     call SimoNOTE "* ------------------------------------------------------------*ezBmsGeneration01"
     call SimoNOTE "Starting JobStep ezBmsGeneration01, Status is %BMSgenerateStatus%, BMS Member is %1"
rem  *
rem  * ************************************************************************
rem  * Do the BMS generation to create the .MOD Screen load member and the
rem  * copy file to be used by a COBOL program.
rem  * The copy file will be written to the CobCpy6 sub-directory under the
rem  * base directory.
rem  *
     mfbmscl %BaseLib1%\%2\%1.BMS /SYSPARM=MAP /SYSPARM=DSECT /COBOL=%BaseLib1%\CobCpy6\ /BINARY=%BaseLib1%\%3\
     if not ERRORLEVEL = 0 set BMSgenerateStatus=0010
     if not "%BMSgenerateStatus%" == "0000" goto :Compile2GNTNOK
rem  *
     echo %BaseLib1%\%3\%1.MOD
     if exist %BaseLib1%\%3\%1.MOD goto :Compile2GNTAOK
     set BMSgenerateStatus=0020
     goto :Compile2GNTNOK
rem  *
rem  * ************************************************************************
:Compile2GNTAOK
     set /A AOK_Count=%AOK_Count% + 1
     call SimoNOTE "BMS LOAD, %BaseLib1%\%3\%1.MOD"
     call SimoNOTE "BMS COPY, %BaseLib1%\CobCpy6\\%1.CPY"
     call SimoNOTE "Complete JobStep ezBmsGeneration01, Status is %BMSgenerateStatus%, BMS Member is %1"
     goto :End
rem  *
rem  * ************************************************************************
:Compile2GNTNOK
     set JobStatus=%BMSgenerateStatus%
     set /A NOK_Count=%NOK_Count% + 1
     call SimoNOTE "ABENDING JobStep ezBmsGeneration01, Status is %BMSgenerateStatus%, BMS Member is %1"
     echo %1>%BaseLib1%\LOGS\%1.ERR
     goto :End
rem  *
rem  * ************************************************************************
:End

Technical Details, Command Files, Create Lists by Cobol Category
(Next) (Previous) (Table-of-Contents)

WIP...

Technical Details, Command Files, Scripted COBOL Compiles
(Next) (Previous) (Table-of-Contents)

WIP...

Technical Details, COBOL Programs
(Next) (Previous) (Table-of-Contents)

WIP...

Technical Details, COBOL Programs, Create HTML Document
(Next) (Previous) (Table-of-Contents)

WIP....

Technical Details, COBOL Programs, Create List of Member Name by Language and Type
(Next) (Previous) (Table-of-Contents)

WIP....

This program (APLISTC3.CBL) will read the Application Properties Repository (APMASTER.DAT) and create an ASCII/Text file (APLIST03) that is a list of source member names. The selection criteria for writing member names to the output file is determine by four (4) environment variables.

Technical Details, COBOL Programs, Create Lists by Cobol Category
(Next) (Previous) (Table-of-Contents)

WIP....

Summary
(Next) (Previous) (Table-of-Contents)

The purpose of this suite of programs is to provide an example of how to scan JCL members and extract file information based on the content of the DD statements and IDCAMS specifications and to save this information in a separate file.

Software Agreement and Disclaimer
(Next) (Previous) (Table-of-Contents)

Permission to use, copy, modify and distribute this software for any non-commercial purpose and without fee is hereby granted, provided the SimoTime copyright notice appear on all copies of the software. The SimoTime name or Logo may not be used in any advertising or publicity pertaining to the use of the software.

SimoTime Enterprises makes no warranty or representations about the suitability of the software for any purpose. It is provided "AS IS" without any express or implied warranty, including the implied warranties of merchantability, fitness for a particular purpose and non-infringement. SimoTime Enterprises shall not be liable for any direct, indirect, special or consequential damages resulting from the loss of use, data or projects, whether in an action of contract or tort, arising out of or in connection with the use or performance of this software.

Links to Similar Pages of Interest
(Next) (Previous) (Table-of-Contents)

You may download this example at http://www.simotime.com/sim4dzip.htm#zpackapmast01 or view the complete list of SimoTime Examples at http://www.simotime.com/sim4dzip.htm.

The  Source Code Member Typing  programs will create an Application Properties Repository.

To save information collected by the JCL Scanner in the File Properties Repository refer to the File Properties Repository Management  provided in separate document.

Check out  The CICS Connection  for more examples of mainframe CICS coding techniques and sample code.

This document provides a quick summary of the  File Status Key  for VSAM data sets and QSAM files.

Check out  The JCL Connection  for more mainframe JCL examples.

To review all the information available on this site start at  The SimoTime Home Page .

Glossary of Terms
(Next) (Previous) (Table-of-Contents)

Check out  The SimoTime Glossary  for a list of terms and definitions used in the documents provided by SimoTime.

Comments or Suggestions
(Next) (Previous) (Table-of-Contents)

If you have any questions, suggestions or comments please call or send an e-mail to: helpdesk@simotime.com

About SimoTime Enterprises
(Next) (Previous) (Table-of-Contents)

Founded in 1987, SimoTime Enterprises is a privately owned company. We specialize in the creation and deployment of business applications using new or existing technologies and services. We have a team of individuals that understand the broad range of technologies being used in today's environments. This includes the smallest thin client using the Internet and the very large mainframe systems. There is more to making the Internet work for your company's business than just having a nice looking WEB site. It is about combining the latest technologies and existing technologies with practical business experience. It's about the business of doing business and looking good in the process. Quite often, to reach larger markets or provide a higher level of service to existing customers it requires the newer Internet technologies to work in a complementary manner with existing corporate mainframe systems. Whether you want to use the Internet to expand into new market segments or as a delivery vehicle for existing business functions simply give us a call or check the web site at http://www.simotime.com