destination_file type or format

Products

• Autosys Workload Automation

Issue/Introduction

Users may want to natively control or change the output file type or format (such as converting it directly to a native Excel or CSV format) generated by the destination_file attribute within an AutoSys Workload Automation AE SQL job_type.

Environment

 

• AutoSys Workload Automation AE (All Versions)

• SQL Job Type (job_type: SQL)

 

Resolution

There are no native AutoSys Workload Automation AE JIL settings or attributes available to alter the underlying file type for the destination_file attribute within an SQL job type. The output file type and its raw contents will always be generated as plain text.

However, you can manipulate the SQL query structure itself to format the text output. For example, you can use SQL string concatenation operators to inject commas or other delimiters between field values. This formats the plain text output into a Comma-Separated Values (CSV) structure, which simplifies post-processing, automated parsing, or opening the final file directly within spreadsheet applications like Microsoft Excel.

Example JIL Definition:

Code snippet

 

insert_job: test_SQL
owner: aedbadmin@aedb
job_type: SQL
machine: example
sql_command: select table_name||','||column_name from user_tab_columns
connect_string: "jdbc:oracle:thin:@dbhost:1521:dbname"
destination_file: "/tmp/test_SQL.log"

Note: In the example above, the Oracle concatenation operator (||) is utilized to format the text output with a comma delimiter. Modify the concatenation syntax according to the specific SQL database dialect (e.g., Oracle, MS SQL Server, Sybase) your job connects to.