Browse Prior Art Database

Batch File Automation with Software Infinite State Machine

IP.com Disclosure Number: IPCOM000113623D
Original Publication Date: 1994-Sep-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 71K

Publishing Venue

IBM

Related People

Cheung, ST: AUTHOR [+2]

Abstract

This present article describes a method for automatically performing a series of process steps in software batch files with the ability to continue executing the process steps even after the computer based system is re-booted. The traditional method for automatically performing a series of process steps in software batch files is based upon replacing or renaming one or more batch files prior to having the system re-boot. In addition, the traditional approach utilize code redundancy wherein copies of the same code must be duplicated throughout several batch files. Two distinct disadvantages result through the use of code redundancy. First, more disk space is required to accommodate each copy of the code. Secondly, modifications to the code must be made in several files.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Batch File Automation with Software Infinite State Machine

      This present article describes a method for automatically
performing a series of process steps in software batch files with the
ability to continue executing the process steps even after the
computer based system is re-booted.  The traditional method for
automatically performing a series of process steps in software batch
files is based upon replacing or renaming one or more batch files
prior to having the system re-boot.  In addition, the traditional
approach utilize code redundancy wherein copies of the same code must
be duplicated throughout several batch files.  Two distinct
disadvantages result through the use of code redundancy.  First, more
disk space is required to accommodate each copy of the code.
Secondly, modifications to the code must be made in several files.
Moreover, the traditional approach many times makes use of GOTO
statements inside BATCH Files.  Because by the very nature of GOTO
statements, i.e., to redirect program flow, software practitioners
must plan the use of GOTO statements and structure their code
accordingly.  Unfortunately, there is a tendency for programs to
rapidly grow unstructured if numerous GOTO statements are placed
uncontrolled or unplanned within software code.  Many software
practitioners avoid GOTO statements unless structure can maintained.
Un-structured code is undesirable due to the difficulty in performing
code modifications, code enhancements and code maintenance.

      To overcome the disadvantages in traditional methods for
automatically performing...