rs_dba_job_parameters
The following table lists the columns for the rs_dba_job_parameters view. The equivalent jcs_dba_job_parameters view is available for backward compatibility reasons. The difference between the two is the data type of the date/time columns; the rs_* views use TIMESTAMP WITH TIME ZONE while the jcs_* views use DATE.
| Column | Datatype | Description |
| JOB_ID | NUMBER | The unique job id |
| PARAMETER_NAME | VARCHAR2 | The parameter name |
| ARRAY_PAR | VARCHAR2 | Is this an array parameter |
| ARRAY_SIZE | NUMBER | Array size for fixed-array parameters |
| DATA_TYPE | VARCHAR2 | The data type of the parameter (date, number, varchar2 or char) |
| DATA_LENGTH | NUMBER | The maximum parameter length |
| DATA_PRECISION | NUMBER | The precision, or total number of digits |
| DATA_SCALE | NUMBER | The number of digits to the right of the decimal point |
| PAR_IN | VARCHAR2 | Is the parameter an input parameter (Y or N)? |
| PAR_OUT | VARCHAR2 | Is the parameter an output parameter (Y or N)? |
| NULLABLE | VARCHAR2 | Is the parameter optional (Y or N)? |
| RUNTIME | VARCHAR2 | Is the parameter determined at runtime (Y or N)? |
| DISPLAY | VARCHAR2 | Is the parameter displayed (Y or N)? |
| EDITABLE | VARCHAR2 | May the default parameter value be overwritten? |
| EDITABLE_IF_NULL | VARCHAR2 | May a parameter value be specified if there is no default? |
| GENERATED | VARCHAR2 | The name of the system parameter when the value is generated by Redwood at runtime |
| PARAMETER_ID | NUMBER | The unique parameter id |
| INPUT_FORMAT | VARCHAR2 | The format string used to check the input value |
| OUTPUT_FORMAT | VARCHAR2 | The format string used to pass to child jobs or to the commandfile |
| DEFAULT_LENGTH | NUMBER | The length of the definition for the default parameter value |
| DATA_DEFAULT | VARCHAR2 | The definition of the default parameter value |
| DEFAULT_TYPE | VARCHAR2 | The type of the default parameter value definition |
| DESCRIPTION | VARCHAR2 | The parameter description |
| CMDFILE | VARCHAR2 | Is the parameter to be put into the CMDFILE |
| VALUE_NUM | NUMBER | The numeric value |
| VALUE_VCH | VARCHAR2 | The character value |
| VALUE_DAT | DATE | The date value |
| VALUE_TSTAMP | TIMESTAMP WITH TIME ZONE | The timestamp valueThe timezone is specified as an Olson name. |
| VALUE_CLOB | CLOB | The clob value |
| OUTVALUE_NUM | NUMBER | The numeric output value |
| OUTVALUE_VCH | VARCHAR2 | The character output value |
| OUTVALUE_DAT | DATE | The date output value |
| OUTVALUE_TSTAMP | TIMESTAMP WITH TIME ZONE | The timestamp output valueThe timezone is specified as an Olson name. |
| OUTVALUE_CLOB | CLOB | The clob output value |
| GROUPNAME | VARCHAR2 | The GUI name of the parameter group |
| VISUAL_ATTRIBUTES | VARCHAR2 | Attributes that can be used by the GUI to store representational data |
| CONSTANT | CHAR | Is this parameter a constant parameter |
| COMMENT_TEXT | VARCHAR2 | Comment describing the parameter |
note
VALUE_DAT: It is best to call jcs.set_date_timezone with a olson timezone, that reflects the database host timezone. E.g. in The Netherlands the database host timezone is +01:00 in the winter and +02:00 in the summer where it is now better to call jcs.set_date_timezone('Europe/Amsterdam') first. Where in Cronacle v7 a job-parameter could only have a date value or have a timestamp with time zone value, here both can be filled in. In Cronacle 8 there is no distinction between DATE and TIMESTAMP WITH TIME ZONE.
note
OUTVALUE_DAT: It is best to call jcs.set_date_timezone with a olson timezone, that reflects the database host timezone. E.g. in The Netherlands the database host timezone is +01:00 in the winter and +02:00 in the summer where it is now better to call jcs.set_date_timezone('Europe/Amsterdam') first. Where in Cronacle v7 a job-parameter could only have a date value or have a timestamp with time zone value, here both can be filled in. In Cronacle 8 there is no distinction between DATE and TIMESTAMP WITH TIME ZONE.
note
VALUE_TSTAMP: Where in Cronacle v7 a job-parameter could only have a date value or have a timestamp with time zone value, here both can be filled in. In Cronacle 8 there is no distinction between DATE and TIMESTAMP WITH TIME ZONE.
note
OUTVALUE_TSTAMP: Where in Cronacle v7 a job-parameter could only have a date value or have a timestamp with time zone value, here both can be filled in. In Cronacle 8 there is no distinction between DATE and TIMESTAMP WITH TIME ZONE.
note
VALUE_CLOB: Version 9 does not support CLOB as parameter type.
note
OUTVALUE_CLOB: Version 9 does not support CLOB as parameter type.
note
INPUT_FORMAT: Version 9 does not have input formats for parameters.
note
OUTPUT_FORMAT: Version 9 does not have output formats for parameters.
plsqlTopic
onsiteTopic