We are migrating our batch workload to the 24x7 Java Edition
running on Solaris servers.

Our current scheduler captures and stores all output
sent to STDOUT by Unix shell scripts. Will 24x7 also
capture output to STDOUT?

The output is not captured by default. What most people do is redirecting output to a log file and using available macro parameters to generate unique file name with a date or date/time suffix, for example

sh /home/me/jobs/mybatch.sh > /home/me/logs/mybatch@V"ddmmyyyy".log

Here when the job runs 24x7 replaces @V"ddmmyyyy" with current date, todays it would be 11012006. So you get the idea....

: We are migrating our batch workload to the 24x7 Java Edition
: running on Solaris servers.

: Our current scheduler captures and stores all output
: sent to STDOUT by Unix shell scripts. Will 24x7 also
: capture output to STDOUT?

: The output is not captured by default. What most people do is redirecting
: output to a log file and using available macro parameters to generate
: unique file name with a date or date/time suffix, for example

: sh /home/me/jobs/mybatch.sh >
: /home/me/logs/mybatch@V"ddmmyyyy".log

: Here when the job runs 24x7 replaces @V"ddmmyyyy" with current
: date, todays it would be 11012006. So you get the idea....

I have tried create a job which the command line as follows:

/u01/app/oracle/admin/scripts/backups/backup_db.ksh SWDEV01 > /var/opt/oracle/logs/scheduler/backups/j@V"job_id".log

The job runs but no log is produced. If I run the same command line
(without the @V"job_id") directly in a shell on the target host, the
log is created OK.

You need to put ksh shell executable in front of the command line. Redirecting output is a function of shell.

: I have tried create a job which the command line as follows:
: /u01/app/oracle/admin/scripts/backups/backup_db.ksh SWDEV01 >
: /var/opt/oracle/logs/scheduler/backups/j@V"job_id".log

: The job runs but no log is produced. If I run the same command line
: (without the @V"job_id") directly in a shell on the target host,
: the
: log is created OK.

: You need to put ksh shell executable in front of the command line.
: Redirecting output is a function of shell.

I've tried this:

/bin/ksh /u01/app/oracle/admin/scripts/backups/backup_db.ksh SWDEV01 > /var/opt/oracle/logs/scheduler/j008.log

but I still don't get any log file produced when the job is run through
the scheduler.

Try this

/bin/ksh "/u01/app/oracle/admin/scripts/backups/backup_db.ksh SWDEV01 > /var/opt/oracle/logs/scheduler/j008.log"

then the entire thing will be sent to the shell as a single command rather then 3 separate parameters

: I've tried this: /bin/ksh /u01/app/oracle/admin/scripts/backups/backup_db.ksh
: SWDEV01 > /var/opt/oracle/logs/scheduler/j008.log

: but I still don't get any log file produced when the job is run through
: the scheduler.