C. Glossary

This glossary defines the terminology used in this manual.

.env file

A file in which are set the path names to the ENV environment variables and that is loaded when the shell starts. You can use the KSH_ENV_READ environment setting parameter to specify whether this file is to be loaded.

argument

A generic term for an item that is specified following a command name. Multiple arguments are separated by a delimiter on the command line or in a job definition script.

arithmetic operation

Any of the calculations performed using arithmetic operators in a job definition script. In an arithmetic operation, the values assigned to variables are handled as numeric values.

base name

The portion of a file name excluding the .extension portion. For example, the base name of adshexec.exe, the program for executing batch jobs, is adshexec.

batch job

A job executed by batch processing.

batch operation server

A server on which JP1/Advanced Shell is installed that is used to execute batch jobs. JP1/AJS - Agent or JP1/AJS - Manager must be installed when JP1/AJS is used.

batch processing

The process of gathering collected data and transactions and processing them in bulk on a regular schedule, such as every day, week, or month.

breakpoint

Coding that forces execution to stop and that is inserted into a job definition script in order to pause the processing during development in order to check the operational status of the job definition script. The debugger interrupts the processing at a breakpoint so that the developer can check the values of variables and registers at the time of the interruption.

built-in command

A command that is included as part of the shell, and thus requires only the shell itself to be executed. Built-in commands can be used in job definition scripts, and they can be executed from the shell or from the command prompt. JP1/Advanced Shell supports regular built-in commands and special built-in commands.

child job

A job whose job definition script is executed as a descendant process of the root job. Child jobs are executed in accordance with one of the following parameter specifications or their default settings:

• CHILDJOB_EXT parameter

• CHILDJOB_PGM parameter

• CHILDJOB_SHEBANG parameter

child job execution log output file

The output file for the job execution log of a child job, which is created by the child job and output in the spool job directory of the root job.

command

Generic name for any instruction that can be used in JP1/Advanced Shell. Commands are executed from the shell or the command prompt, as well as from job definition scripts.

command grouping

Facility for executing multiple commands as a unit in JP1/Advanced Shell.

command line

The line displayed to the user for entering commands. In the Windows command prompt, input is entered after the > on the command line. In the UNIX shell, input is entered after the % on the command line.

command prompt

The window in a Windows environment that requests that a command be entered.

command separator

The functionality that allows developers to write more than one command on a single line of a job definition script in JP1/Advanced Shell.

conditional

A test that controls the processing branch that is to execute based on the results of a conditional expression in a control statement in a job definition script.

conditional expression

A formula used in a job definition script that expresses a calculation using numeric comparisons, string comparisons, file attributes, logical operators, and the ternary operator.

conditional parameter

Any of the parameters that are set in an environment file and that are specified in order to configure the environment setting parameters and export parameters that are valid only in the physical host or in a specific logical host.

console

The terminal screen.

control statement

Same meaning as script control statement.

core dump

A source of maintenance information collected by a trace program and consisting of core files and dump files. When a problem occurs, the contents of memory are saved to a file that can be used to assist with troubleshooting.

coverage information

Information that provides measurements in tests of the extent of coverage. The two types of coverage information are C0, which is statement coverage information, and C1, which is branch coverage information. C0 measures the ratio (%) of commands in a job definition script that execute, while C1 measures the ratio (%) of branches in a job definition script that execute.

custom job

A predefined job for executing a task with a specific purpose in JP1/AJS. The custom job component for JP1/Advanced Shell is required in order to take advantage of JP1/AJS's custom job functionality in JP1/Advanced Shell.

debug

The process of testing a job definition script created in the development environment or of investigating errors in a script. To debug, you must launch the debugger.

debugger

A program for testing a job definition script created in the development environment and for investigating errors in a script. In the Windows environment, the debugging functions of the JP1/Advanced Shell editor are used. In the UNIX environment, the debugger is started by specifying the -d option in the adshexec command.

definition file

A file that defines the directories into which data for troubleshooting is to be collected.

development environment

An environment provided by JP1/Advanced Shell - Developer that supports development of job definition scripts for batch processing.

dialog box

A window that asks the user to enter a response.

editor

A program for creating job definition scripts efficiently by taking advantage of a variety of features provided in the development environment.

environment file

A file that contains environment information.

environment information

Information, such as environment variables and environment file parameters, that must be set before JP1/Advanced Shell starts.

environment setting parameter

Any of the parameters that are set in an environment file for the purpose of defining the JP1/Advanced Shell execution environment. These parameters are specified in the format #-adsh_conf parameter-value.

environment variable

Any of the variables that contain various system settings that can be set by the user.

execution environment

The environment provided by JP1/Advanced Shell for execution of batch operations. JP1/Advanced Shell refers to the execution environment in its narrow sense.

export parameter

A parameter that is set in the environment file and whose function is to set an environment variable when a command starts.

extended script command

A command that is executed in a job definition script. Compared to normal shell script commands, these commands offer the additional capability to control batch job execution. They are also referred to as job execution control commands. In JP1/Advanced Shell, these commands start with #-adsh.

extended shell command

A built-in command that is internal to the shell and executed by the shell itself. Extended shell commands can be used in job definition scripts.

extended shell variable

A shell variable with a special meaning that is provided by JP1/Advanced Shell.

external command

Any of the UNIX-compatible commands, OS-provided commands, user-created executable files, and other programs that are not shell built-in commands.

fault injection mode

A mode used during debugging to simulate the occurrence of an error.

In UNIX, you enable or disable the fault injection mode with the joberrmode command. In Windows, you choose the Fault Injection Mode menu item in the JP1/Advanced Shell editor.

file allocation

In JP1/Advanced Shell, such operations as registering postprocessing of files are referred to as file allocation.

file descriptor

A numeric identifier for distinguishing the different types of input and output in JP1/Advanced Shell. In JP1/Advanced Shell, the standard output is assigned 1, the standard error output is assigned 2, and 3 through 9 can be allocated and used for other purposes.

flow control

Functionality for controlling the event-issuance interval for JP1 events that are issued during execution of the adshread and adshecho commands.

here document

A redirection functionality used in a job definition script by which standard input is generated with the job definition script.

job controller

A program for controlling a job while the job is running. The adshexec command is the job controller.

job definition script file

A program file that defines a job that has been prepared as a job definition script.

job execution log

A collection of messages output by a job, including the start and end messages for the job and job steps. At the end of a job, the contents of the job execution log are sent to the standard error output by the job controller.

job ID

An identification number (sequentially generated between 000001 and 999999) that is assigned to a job by JP1/Advanced Shell at the time the job is executed. Each job is assigned a unique identifier, so that each job can be identified individually on the basis of its job ID. Once job ID 999999 has been assigned, the next job is assigned job ID 000001.

job information

Information associated with a job, such as the job name, job ID, and job step names.

jobnet

A set of jobs whose execution order is defined. Jobs within the jobnet execute automatically in the predefined order. The jobnet is a functionality provided by JP1/AJS.

job scheduler

A product that performs job scheduling. It is part of a suite of products in JP1/Advanced Shell used to link to JP1/AJS.

job step

A range of processing within a job defined in a job definition script that demarcates a unit of specific processing. The job step is the smallest unit for performing a specific operation (task) in JP1/Advanced Shell. A job is made up of a collection of job steps. Job steps are defined with the #-adsh_step_start, #-adsh_step_error (optional), and #-adsh_step_end commands.

JP1/Advanced Shell

A product used to create and execute batch jobs from job definition scripts. JP1/Advanced Shell can be divided into JP1/Advanced Shell and JP1/Advanced Shell - Developer. In this narrow sense, JP1/Advanced Shell refers to the execution environment in which batch jobs are executed from job definition scripts. Batch jobs in both Windows and UNIX can be run from the same job definition script.

JP1/Advanced Shell - Custom Job

A program for creating jobs that are custom-defined in the operation management console in JP1/Advanced Shell.

JP1/Advanced Shell - Developer

A product used for developing job definition scripts for batch jobs. This term also refers to the development environment in which job definition scripts are developed.

JP1/AJS3

Abbreviation for JP1/Automatic Job Management System 3, which is the successor product to JP1/AJS2. By linking JP1/Advanced Shell to JP1/AJS3, you can achieve distributed processing among multiple PCs.

log

Historical information that is output by the computer. Timestamps, messages, and similar items are output as logs.

long option

A type of option specified in command arguments. A long option begins with two consecutive hyphens (--) followed by a character string.

metacharacter

A character (or character string) that has a special meaning in a job definition script.

operand

A type of command argument specified on the command line. An operand is a default command argument that is specified in addition to option names and option values. Parameter values are also called operands.

option

In general, a pre-selected capability that is added to the instructions provided by a computer input device.

In JP1/Advanced Shell, a command argument consisting of one hyphen (-) followed by one character is called a short option, and a command argument consisting of two consecutive hyphens (--) followed by a character string is called a long option.

An argument specified immediately following an option is the option's value.

pipe

A functionality for linking the standard output of a previous command to the standard input of a subsequent command.

program output data file

A file to which a user program can output its execution results. JP1/Advanced Shell creates the file name automatically in order to consolidate the user program's output results with the system execution log.

quotation

Either the single quotation mark (') or the double quotation mark (").

redirection

Capability before a command in a job definition script is executed to change the input source for the information needed to execute the command or the output destination for the execution results. Typically, the keyboard is assigned as the standard input and the screen is assigned as the standard output, but redirection enables these assignments to be changed.

regular built-in command

Any of a set of the built-in commands among the standard shell commands. In the case of a regular built-in command, even if its command syntax is invalid, it does not exit the shell that is executing the command (see also special built-in command).

regular file

A file used for input or output by a job definition script. Regular files might remain after the job finishes, or regular files might be deleted during execution of the job. Regular files can be defined with the #-adsh_file command or the adshfile command.

reply-request message

A message that asks the operator to enter a reply.

reply-waiting event

A JP1 event that provides notification of a reply-request message.

reserved script command

A command that can be used as a reserved word in a job definition script. An example is the time command.

return code

A code that is returned to report the execution result of a job definition script or a command.

root job

A job executed from JP1/AJS or a login shell that is not a child job.

script

A text file into which is assembled a series of commands that can be executed sequentially from the shell. A script in JP1/Advanced Shell is called a job definition script, and they can be executed in both the Windows and UNIX environments.

script control statement

A statement for managing commands in a job definition script. Examples include the if, for, while, until, and case statements.

script file

A file in which a script that has been created is saved.

shell

A program that interprets instructions provided by a computer input device and passes them to the OS.

shell command

Generic name for any command used in JP1/Advanced Shell that is executed in the shell or from the command prompt.

shell operation command

A command that is provided as an executable binary file or a shell script. The two types of shell operation commands are those that can be used only in job definition scripts and those that can be used not only in job definition scripts but from OS shells and the command prompt. The shell operation commands include the adshexec command (executes batch jobs).

shell option

Any of the pre-selected capabilities that are added to the instructions provided by a computer input device to the shell.

shell script

A text file into which you assemble a series of commands so that you can then execute those commands sequentially from the shell. A shell script in JP1/Advanced Shell is referred to as a job definition script, and it can be executed in both the Windows and UNIX environments.

shell variable

An area of memory assigned as a value in a job definition script. You can reference the value of a created variable.

short option

A type of option specified in command arguments. A short option begins with a hyphen (-) followed by one character.

signal

A mechanism in UNIX by which processes report to each other the occurrence of asynchronous events. For example, a signal is sent when a job is forcibly terminated in JP1/Advanced Shell.

special built-in command

Any of a set of the built-in commands among the standard shell commands. In the case of a special built-in command, if its command syntax is invalid, it exits the shell that is executing the command (see also regular built-in command).

spool

The location where JP1/Advanced Shell stores the execution results of jobs and job execution logs.

spool job

The execution results for each job created in the spool directory.

standard error output (stderr)

A stream to which a program outputs its error messages and other messages.

standard input (stdin)

A stream from which a program receives its input data.

standard output (stdout)

A stream to which a program outputs its data.

standard shell command

A built-in command that is internal to the shell and executed in a process in the shell itself. Standard shell commands can be used in job definition scripts.

subshell

In a UNIX environment, a child process that has the same name as the job controller, is neither a root job nor a child job, and is created temporarily automatically when an external command or a specific syntax is executed in a job definition script.

symbolic link

A link that is implemented as a file that contains the actual file path.

system execution log

A log output by a job controller in JP1/Advanced Shell in order to facilitate integrated management of job execution status by the system administrators. Log information from multiple job controllers can be output to a single log.

temporary file

A file whose use is transient during job execution. Temporary files are created by a job or job step, and they are deleted automatically when the job terminates. Temporary files are defined with the #-adsh_file_temp command.

trace log

Information collected to assist in investigating and resolving problems that occur in JP1/Advanced Shell.

trap action

An action that is defined in the trap command's action argument.

UNIX-compatible command

Any of the standard UNIX commands, such as the ls command, that can be used in JP1/Advanced Shell. These commands can also be used in a Windows environment, which facilitates interoperability between UNIX and Windows.

variable

A location or array in memory that is used to handle values in a job definition script. Examples of variables include shell variables and environment variables.

watchpoint

A special breakpoint that stops a job definition script when the value of a variable or expression changes. A watchpoint can be managed in the same way as any other type of breakpoint.

wildcard

A character, such as the asterisk (*) or the question mark (?), that can be specified as a stand-in for any character or character string. The asterisk (*) represents any character string, and the question mark (?) represents any single character.

In addition, you can use square brackets ([]) to obtain a match with any of the characters in the character string enclosed in the square brackets. You can also use the hyphen (-) to separate values constituting a range, or the exclamation mark (!) for a condition to be true when none of the characters enclosed in square brackets results in a match. You can also use the comma (,) to assemble a comma-separated list of character strings, any one of which can be selected.

To Page Top