5.9.1 Allocating regular files and performing postprocessing

Use the #-adsh_file command (extended script command) or the adshfile command (shell operation command) to do the following:

Performing postprocessing on the allocated files according to the results of the corresponding job step or job.
If the #-adsh_file command is used, assigning to shell variables and environment variables the file paths of regular files that will be used in the job or job step and the commands that will be started.

The table below describes the functional differences between the #-adsh_file and adshfile commands. For details about the #-adsh_file command, see #-adsh_file command (specifies assignment and postprocessing of regular files). For details about the adshfile command, see adshfile command (specifies the allocation and postprocessing of regular files).

Item	#-adsh_file command	adshfile command
Specifying file paths in environment variables	Y	N
Timing of file postprocessing	Outside the step When the job terminates Inside the step When the step terminates	Specifies either job termination or step termination.
Whether specification is permitted in external scripts specified in `.` (dot) commands	N	Y
Whether specification is permitted within iteration processing	N	Y
Whether specification is permitted within functions	N	Y
Postprocessing of allocated regular files in the event of a file allocation error	Assumes `keep` and does not delete files. For details, see 5.9.1(2)(a) #-adsh_file command.	Depends on the specification of the `-a` argument. For details, see 5.9.1(2)(b) adshfile command.

Legend:

Y: Supported.

N: Not supported.

Important note: Regular files allocated with the adshfile command are managed separately from regular files allocated with the #-adsh_file command. Postprocessing is performed on regular files allocated by the adshfile command before it is performed on regular files allocated by the #-adsh_file command. If the same file is allocated with both commands, it will be postprocessed twice, which might result in an error.

Organization of this subsection

(1) Allocating regular files
(2) Postprocessing regular files
(3) Example of adshfile command specification (within iteration processing)
(4) Example of adshfile command specification (within a function)

(1) Allocating regular files

The #-adsh_file command assigns the file path of a regular file to a shell variable and an environment variable that have the same name as the file environment variable definition name.

The #-adsh_file and adshfile commands do not create the entities of the specified regular files.

To check whether a file exists when the file is to be allocated, specify exist for -chk in the #-adsh_file command and for -c in the adshfile command. When exist is specified and the specified file does not exist at the time of allocation, an error results.

To allocate a file regardless of whether the file exists, specify no for -chk in the #-adsh_file command and for -c in the adshfile command. When no is specified, the command allocates the specified file, even if the file does not exist without treating it as an error.

The following examples allocate regular file test1 to FILE by using the #-adsh_file command:

Windows

#-adsh_file FILE 'C:\home\test\test1' -chk exist -normal keep -abnormal keep

UNIX

#-adsh_file FILE /home/test/test1 -chk exist -normal keep -abnormal keep

The following shows a usage example of the chk attribute in UNIX:

#-adsh_job FILE_CHK
#-adsh_step_start STEP01
  #-adsh_file FILE01 /home/test/test1 -chk no -normal keep -abnormal keep
  #-adsh_file FILE02 /home/test/test2 -chk exist -normal keep -abnormal keep
  cmdA ${FILE01} ${FILE02}
#-adsh_step_end

When it allocates FILE01, the command does not check whether the file exists. Therefore, the file is always allocated even if /home/test/test1 does not exist.

When it allocates FILE02, the command checks whether the file exists. Therefore, if /home/test/test2 does not exist, the file allocation processing results in an error.

To Page Top

(2) Postprocessing regular files

Regular files are postprocessed when the job step or job that allocated the files terminates. Postprocessing by the #-adsh_file command includes resetting the shell and environment variables in which the file paths are set to their previous values before the file paths were set. The processing described below is also performed according to the termination status of the job step or job and values specified in the command.

If the job step and job terminated normally, the #-adsh_file command performs postprocessing according to the value specified for -normal, and the adshfile command performs postprocessing according to the value specified for -n. The following explains the postprocessing of regular files, depending on the specified value:

If del is specified, a regular file is deleted when the job step or job terminates.
If keep is specified, a regular file is not deleted when the job step or job terminates.

If the job step or job terminates with an error, postprocessing is performed according to the value specified for -abnormal in the #-adsh_file command, or the value specified for -a in the -adshfile command. The following explains the postprocessing of regular files, depending on the specified value.

If del is specified, a regular file is deleted when the job step or job terminates.
If keep is specified, a regular file is not deleted when the job step or job terminates.

The following table explains postprocessing when -abnormal is specified in the #-adsh_file command or the -a option is specified in the adshfile command:

Cause of an error in the job step or job	Postprocessing of regular files allocated with the #-adsh_file command	Postprocessing of regular files allocated with the adshfile command
An error occurred while a regular file was being allocated by the subsequent `#-adsh_file` command	`keep` is assumed unconditionally.	Depends on the `-a` option of the `adshfile` command.^# (`keep` is not assumed.)
An error occurred while a regular file was being allocated by the subsequent `adshfile` command	Depends on the `-abnormal` option of each `#-adsh_file` command.	Depends on the `-a` option of the `adshfile` command.
An error occurred while a temporary file was being allocated by the subsequent `#-adsh_temp` command	`keep` is assumed unconditionally.	Depends on the `-a` option of the `adshfile` command.^# (`keep` is not assumed.)
An error occurred while a program output data file was being allocated by the subsequent `#-adsh_spoolfile` command	`keep` is assumed unconditionally.	Depends on the `-a` option of the `adshfile` command.^# (`keep` is not assumed.)
Error in a subsequent command or program other than the above	Depends on the `-abnormal` option of each `#-adsh_file` command.	Depends on the `-a` option of the `adshfile` command.

#: If you want to retain files unconditionally in the event of an allocation error, use the #-adsh_file command.

Because the actual file is not created when a regular file is allocated, any file that does not exist when postprocessing is performed remains nonexistent.

(a) #-adsh_file command

The following shows an example of postprocessing in Windows:

#-adsh_job JOB
#-adsh_file FILE01 'C:\user\file01' -chk exist -normal keep -abnormal del
 
#-adsh_step_start STEP
    #-adsh_file FILE02 'C:\user\file02' -chk exist -normal del -abnormal del
    #-adsh_file FILE03 'C:\user\file03' -chk exist -normal keep -abnormal del
    uap
#-adsh_step_end
 
#-adsh_file FILE04 'C:\user\file04' -chk exist -normal del -abnormal del

Example 1:

Allocation of FILE03 resulted in an error.

The regular file allocated to FILE01 is postprocessed when the job terminates. The regular file is deleted according to the specified abnormal attribute.
The regular file allocated to FILE02 is postprocessed when the job step terminates. The command assumes keep regardless of the specified normal and abnormal attributes and does not delete the regular file.
The regular file whose allocation to FILE03 was attempted is not postprocessed because allocation is not completed.
Allocation of FILE04 is not performed.

Example 2:

Allocation of FILE04 resulted in an error.

The regular file allocated to FILE01 is postprocessed when the job terminates. The command assumes keep regardless of the specified normal and abnormal attributes and does not delete the regular file.
The regular file allocated to FILE02 is postprocessed when the job step terminates. The command deletes the regular file according to the specified normal attribute.
The regular file allocated to FILE03 is postprocessed when the job step terminates. The command does not delete the regular file according to the specified normal attribute.
The regular file whose allocation to FILE04 was attempted is not postprocessed because allocation is not completed.

Example 3:

UAP resulted in an error.

The regular file allocated to FILE01 is postprocessed when the job terminates. The regular file is deleted according to the specified abnormal attribute.
The regular file allocated to FILE02 is postprocessed when the job step terminates. The command deletes the regular file according to the specified abnormal attribute.
The regular file allocated to FILE03 is postprocessed when the job step terminates. The command deletes the regular file according to the specified abnormal attribute.
Allocation of FILE04 is not performed.

Example 4:

File allocation terminated normally.

The regular file allocated to FILE01 is postprocessed when the job terminates. The command does not delete the regular file according to the specified normal attribute.
The regular file allocated to FILE02 is postprocessed when the job step terminates. The command deletes the regular file according to the specified normal attribute.
The regular file allocated to FILE03 is postprocessed when the job step terminates. The command does not delete the regular file according to the specified normal attribute.
The regular file allocated to FILE04 is postprocessed when the job terminates. The command deletes the regular file according to the specified normal attribute.

(b) adshfile command

The following shows an example of postprocessing. In this example, the names of the regular files are file01_execution-date and file02_execution-date, where execution-date is replaced with the execution time of the job.

#-adsh_job JOB
 
VAL01=file01_`date +%y%m%d`
VAL02=file02_`date +%y%m%d`
VAL03=file03_`date +%y%m%d`
VAL04=file04_`date +%y%m%d`
VAL05=file05_`date +%y%m%d`
 
 
adshfile -s job -n keep -a del ${VAL01}
 
#-adsh_step_start STEP
    adshfile -s step -n del -a del ${VAL02}
    adshfile -s step -n keep -a keep ${VAL03}
    adshfile -s step -n keep -a del ${VAL04}
    uap
#-adsh_step_end
 
adshfile -s job -n del -a del ${VAL05}

Example 1:

Allocation of VAL04 resulted in an error.

The regular file allocated to VAL01 is postprocessed when the job terminates. The regular file is deleted according to the specified -a option.
The regular file allocated to VAL02 is postprocessed when the job step terminates. The regular file is deleted according to the specified -a option (unlike the #-adsh_file command, postprocessing is performed according to the specified -a option; keep is not assumed).
The regular file allocated to VAL03 is postprocessed when the job step terminates. The command does not delete the regular file according to the specified -a option.
VAL04 results in a command error, and the regular file whose allocation to VAL04 was attempted is not postprocessed because allocation was not completed.
Allocation of VAL05 is not performed.

Example 2:

Allocation of VAL05 resulted in an error.

The regular file allocated to VAL01 is postprocessed when the job terminates. The regular file is deleted according to the specified -a option (unlike the #-adsh_file command, postprocessing is performed according to the specified -a option; keep is not assumed).
The regular file allocated to VAL02 is postprocessed when the job step terminates. The command deletes the regular file according to the specified -n option.
The regular file allocated to VAL03 is postprocessed when the job step terminates. The command does not delete the regular file according to the specified -n option.
The regular file allocated to VAL04 is postprocessed when the job step terminates. The command does not delete the regular file according to the specified -n option.
VAL05 results in a command error, and the regular file whose allocation to VAL05 was attempted is not postprocessed because allocation was not completed.

Example 3:

uap resulted in an error.

The regular file allocated to VAL01 is postprocessed when the job terminates. The regular file is deleted according to the specified -a option.
The regular file allocated to VAL02 is postprocessed when the job step terminates. The regular file is deleted according to the specified -a option.
The regular file allocated to VAL03 is postprocessed when the job step terminates. The command does not delete the regular file according to the specified -a option.
The regular file allocated to VAL04 is postprocessed when the job step terminates. The regular file is deleted according to the specified -a option.
Allocation of VAL05 is not performed.

Example 4:

File allocation terminated normally.

The regular file allocated to VAL01 is postprocessed when the job terminates. The command does not delete the regular file according to the specified -n option.
The regular file allocated to VAL02 is postprocessed when the job step terminates. The command deletes the regular file according to the specified -n option.
The regular file allocated to VAL03 is postprocessed when the job step terminates. The command does not delete the regular file according to the specified -n option.
The regular file allocated to VAL04 is postprocessed when the job step terminates. The command does not delete the regular file according to the specified -n option.
The regular file allocated to VAL05 is postprocessed when the job terminates. The command deletes the regular file according to the specified -n option.

To Page Top

(3) Example of adshfile command specification (within iteration processing)

The following example specifies the adshfile command within iteration processing in UNIX:

[user001@hosta user001]$ /opt/jp1as/bin/adshexec Tloop.ash
KNAX7901-I The adshexec command will wait for all asynchronous processes at the end of the job.
KNAX0724-I The job ID was assigned. job ID=000500
---------------------------------------------------------------
 Advanced Shell 10-10
 
 [Information]
   Job ID          : 000500
   Spool directory : /var/opt/jp1as/spool/000500/
   Date            : 2013/12/06
   EnvFile(system) :
   EnvFile(job)    :
   Host name       : hosta
 [Environment variable from Automatic Job Management System]
---------------------------------------------------------------
********  JOB CONTROLLER MESSAGE  ********
15:23:22 000500 KNAX0091-I LOOP The job started.
15:23:22 000500 KNAX7901-I The adshexec command will wait for all asynchronous processes at the end of the job.
15:23:22 000500 KNAX7902-I The adshexec command will run in tty stdin mode.
15:23:22 000500 KNAX6112-I Execution of the command echo (line=3) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:23:22 000500 KNAX6116-I Execution of the command /bin/ls (line=4) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:23:22 000500 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=8) finished successfully. exit status=0 execution time=0.011s CPU time=0.000s
15:23:22 000500 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=9) finished successfully. exit status=0 execution time=0.009s CPU time=0.010s
15:23:22 000500 KNAX6112-I Execution of the command echo (line=10) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:23:22 000500 KNAX6112-I Execution of the command echo (line=11) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:23:22 000500 KNAX6116-I Execution of the command /bin/cat (line=12) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:23:22 000500 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=8) finished successfully. exit status=0 execution time=0.006s CPU time=0.000s
15:23:22 000500 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=9) finished successfully. exit status=0 execution time=0.009s CPU time=0.010s
15:23:22 000500 KNAX6112-I Execution of the command echo (line=10) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:23:22 000500 KNAX6112-I Execution of the command echo (line=11) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:23:22 000500 KNAX6116-I Execution of the command /bin/cat (line=12) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:23:22 000500 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=8) finished successfully. exit status=0 execution time=0.006s CPU time=0.000s
15:23:22 000500 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=9) finished successfully. exit status=0 execution time=0.009s CPU time=0.010s
15:23:22 000500 KNAX6112-I Execution of the command echo (line=10) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:23:22 000500 KNAX6112-I Execution of the command echo (line=11) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:23:22 000500 KNAX6116-I Execution of the command /bin/cat (line=12) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:23:22 000500 KNAX1890-I The file was deallocated as "keep". path=/home/user001/test.txt
15:23:22 000500 KNAX1890-I The file was deallocated as "del". path=/home/user001/output_test.txt
15:23:22 000500 KNAX1604-I The file /home/user001/output_test.txt was deleted.
15:23:22 000500 KNAX1890-I The file was deallocated as "keep". path=/home/user001/test01.txt
15:23:22 000500 KNAX1890-I The file was deallocated as "del". path=/home/user001/output_test01.txt
15:23:22 000500 KNAX1604-I The file /home/user001/output_test01.txt was deleted.
15:23:22 000500 KNAX1890-I The file was deallocated as "keep". path=/home/user001/test02.txt
15:23:22 000500 KNAX1890-I The file was deallocated as "del". path=/home/user001/output_test02.txt
15:23:22 000500 KNAX1604-I The file /home/user001/output_test02.txt was deleted.
15:23:22 000500 KNAX0098-I LOOP The job ended. exit status=0 execution time=0.126s CPU time=0.050s
 
********   Script IMAGE    ********
 
***** /home/user001/Tloop.ash *****
0001 : #-adsh_job LOOP
0002 :
0003 :   echo -E "<<< list >>>" >&2
0004 :   ls test* >&2
0005 :
0006 :   for MEMBER in test*
0007 :   do
0008 :     ${ADSH_DIR_BIN}adshfile -s job -n keep -a keep $MEMBER
0009 :     ${ADSH_DIR_BIN}adshfile -s job -n del -a del output_$MEMBER
0010 :     echo -E "MEMBER=$MEMBER" >output_$MEMBER
0011 :     echo -E  "<<< output_$MEMBER >>>" >&2
0012 :     cat output_$MEMBER >&2
0013 :   done
0014 :
 
***** CONVERSION INFORMATION *****
 
********   JOB SCOPE STDERR    ********
<<< list >>>
test.txt
test01.txt
test02.txt
<<< output_test.txt >>>
MEMBER=test.txt
<<< output_test01.txt >>>
MEMBER=test01.txt
<<< output_test02.txt >>>
MEMBER=test02.txt
KNAX0098-I LOOP The job ended. exit status=0 execution time=0.126s CPU time=0.050s
 
******** JOBSTEP OUTPUT ********
KNAX6380-I A job name will be added to the spool job directory of the root job. spool job directory="/var/opt/jp1as/spool/000500-LOOP/"
KNAX7999-I Advanced Shell ended. exit status=0
[user001@hosta user001]$

To Page Top

(4) Example of adshfile command specification (within a function)

The following example specifies the adshfile command within a function in UNIX:

[user001@hosta user001]$ /opt/jp1as/bin/adshexec Tfunction.ash
KNAX7901-I The adshexec command will wait for all asynchronous processes at the end of the job.
KNAX0724-I The job ID was assigned. job ID=000503
---------------------------------------------------------------
 Advanced Shell 10-10
 
 [Information]
   Job ID          : 000503
   Spool directory : /var/opt/jp1as/spool/000503/
   Date            : 2013/12/06
   EnvFile(system) :
   EnvFile(job)    :
   Host name       : hosta
 [Environment variable from Automatic Job Management System]
---------------------------------------------------------------
********  JOB CONTROLLER MESSAGE  ********
15:42:00 000503 KNAX0091-I FUNCTION The job started.
15:42:00 000503 KNAX7901-I The adshexec command will wait for all asynchronous processes at the end of the job.
15:42:00 000503 KNAX7902-I The adshexec command will run in tty stdin mode.
15:42:00 000503 KNAX0092-I FUNCTION.STEP001 step started.
15:42:00 000503 KNAX6112-I Execution of the command echo (line=15) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=4) finished successfully. exit status=0 execution time=0.014s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=5) finished successfully. exit status=0 execution time=0.009s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/cmd/cp (line=6) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:42:00 000503 KNAX6112-I Execution of the command echo (line=7) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/cmd/cat (line=8) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:42:00 000503 KNAX6112-I Execution of the command echo (line=15) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=4) finished successfully. exit status=0 execution time=0.013s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=5) finished successfully. exit status=0 execution time=0.009s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/cmd/cp (line=6) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:42:00 000503 KNAX6112-I Execution of the command echo (line=7) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/cmd/cat (line=8) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:42:00 000503 KNAX6112-I Execution of the command echo (line=15) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=4) finished successfully. exit status=0 execution time=0.014s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=5) finished successfully. exit status=0 execution time=0.009s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/cmd/cp (line=6) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:42:00 000503 KNAX6112-I Execution of the command echo (line=7) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/cmd/cat (line=8) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:42:00 000503 KNAX6112-I Execution of the command echo (line=15) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=4) finished successfully. exit status=0 execution time=0.014s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/bin/adshfile (line=5) finished successfully. exit status=0 execution time=0.009s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/cmd/cp (line=6) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:42:00 000503 KNAX6112-I Execution of the command echo (line=7) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:42:00 000503 KNAX6116-I Execution of the command /opt/jp1as/cmd/cat (line=8) finished successfully. exit status=0 execution time=0.001s CPU time=0.000s
15:42:00 000503 KNAX1890-I The file was deallocated as "del". path=/home/user001/infile1
15:42:00 000503 KNAX1604-I The file /home/user001/infile1 was deleted.
15:42:00 000503 KNAX1890-I The file was deallocated as "del". path=/home/user001/outfile1
15:42:00 000503 KNAX1604-I The file /home/user001/outfile1 was deleted.
15:42:00 000503 KNAX1890-I The file was deallocated as "del". path=/home/user001/infile2
15:42:00 000503 KNAX1604-I The file /home/user001/infile2 was deleted.
15:42:00 000503 KNAX1890-I The file was deallocated as "del". path=/home/user001/outfile2
15:42:00 000503 KNAX1604-I The file /home/user001/outfile2 was deleted.
15:42:00 000503 KNAX1890-I The file was deallocated as "del". path=/home/user001/infile3
15:42:00 000503 KNAX1604-I The file /home/user001/infile3 was deleted.
15:42:00 000503 KNAX1890-I The file was deallocated as "del". path=/home/user001/outfile3
15:42:00 000503 KNAX1604-I The file /home/user001/outfile3 was deleted.
15:42:00 000503 KNAX1890-I The file was deallocated as "del". path=/home/user001/infile4
15:42:00 000503 KNAX1604-I The file /home/user001/infile4 was deleted.
15:42:00 000503 KNAX1890-I The file was deallocated as "del". path=/home/user001/outfile4
15:42:00 000503 KNAX1604-I The file /home/user001/outfile4 was deleted.
15:42:00 000503 KNAX6597-I FUNCTION.STEP001 step succeeded. exit status=0 execution time=0.204s CPU time=0.000s
15:42:00 000503 KNAX6112-I Execution of the command echo (line=21) finished successfully. exit status=0 execution time=0.000s CPU time=0.000s
15:42:00 000503 KNAX0098-I FUNCTION The job ended. exit status=0 execution time=0.207s CPU time=0.000s
 
********   Script IMAGE    ********
 
***** /home/user001/Tfunction.ash *****
0001 : #-adsh_job FUNCTION
0002 :
0003 : myfunc(){
0004 :    ${ADSH_DIR_BIN}adshfile -s step -n del -a del -c exist $1
0005 :    ${ADSH_DIR_BIN}adshfile -s step -n del -a del $2
0006 :    ${ADSH_DIR_CMD}cp $1 $2
0007 :    echo -E "<<< $2 >>>" >&2
0008 :    ${ADSH_DIR_CMD}cat  $2 >&2
0009 : }
0010 :
0011 : #-adsh_step_start STEP001
0012 :
0013 :     for CNT in 1 2 3 4
0014 :     do
0015 :       echo -E "dddd$CNT" >infile$CNT
0016 :       myfunc infile$CNT outfile$CNT
0017 :     done
0018 :
0019 : #-adsh_step_end
0020 :
0021 : echo -E "JOB_FUNCTION_END" >&2
 
***** CONVERSION INFORMATION *****
 
********   JOB SCOPE STDERR    ********
KNAX6597-I FUNCTION.STEP001 step succeeded. exit status=0 execution time=0.204s CPU time=0.000s
JOB_FUNCTION_END
KNAX0098-I FUNCTION The job ended. exit status=0 execution time=0.207s CPU time=0.000s
 
******** JOBSTEP OUTPUT ********
KNAX0719-I STEP. step number=0001 step name=STEP001 output destination=STDERR
<<< outfile1 >>>
dddd1
<<< outfile2 >>>
dddd2
<<< outfile3 >>>
dddd3
<<< outfile4 >>>
dddd4
 
KNAX6380-I A job name will be added to the spool job directory of the root job. spool job directory="/var/opt/jp1as/spool/000503-FUNCTION/"
KNAX7999-I Advanced Shell ended. exit status=0
[user001@hosta user001]$

To Page Top