Compliance Rules Reference

.pjb.grm

Parallel job

.qjb.grm

Sequence job

.sjb.grm

Server job

.psc.grm

Parallel shared container

.ssc.grm

Server shared container

Yes

-

-

Recommends considering replacing a Transformer Stage using a Surrogate Key with a Surrogate Key Generator stage.

Yes

Yes

Yes

Identifies where naming standards for Job Parameters and Parameter Sets are breached

Yes

Yes

-

Identifies potentially redundant sorting (a sort stage or link sort) situated immediately after a Join stage

Yes

Yes

-

Identifies redundant sorts within a job

Yes

Yes

-

Identifies calls to deprecated functions in the Transformer Stage code generated by DataStage

Yes

Yes

-

Identify unencrypted Job parameters used for storing passwords

Yes

Yes

-

Identifies row limits in file-based stages (Sequential File, Complex Flat File)

Yes

-

-

Identifies the use of system time in the job

Yes

-

-

Identifies Lookup Stages with Lookup set to Fail

Yes

Yes

-

Identifies unique sorts

Yes

-

-

Identify Oracle Stages not configured to use partitioned reads

Yes

Yes

-

Detect duplicate Stage names in a job

Yes

Yes

-

Identifies the use of deprecated stages in Parallel Jobs and suggests an alternative

Yes

Yes

-

Identifies Connector Stages using customer SQL employing a ‘SELECT *’ clause

Yes

Yes

Yes

Identifies Connectors Stages with a configured Database Row Limit

Yes

-

-

Detect an 'Abort after rows' greater than 0 setting in a Parallel Transformer.

Yes

-

Identifies Row Splitter Stage with output format delimited but no delimiter specified

-

-

Yes

Identifies Job Sequences that are not restartable

Yes

Yes

-

Lists the stages that are not yet supported by IBM Data Flow Designer

Yes

Yes

-

This rule detects the use of stages in Parallel Jobs that don't support automatic lineage

Yes

Yes

-

Identify Stages configured to Log column values on first row error

Yes

Yes

-

Ensures that all Database Connectors and Stages must use variables for location and credentials

Yes

-

-

Avoid Reading from Sequential Files Using the Same Partitioning Method

-

-

Yes

Verifies that a job sequence automatically handles failed activities

-

-

Yes

Identifies where a Job Activity Execution Action is not Reset if required, then run

Yes

Yes

Yes

Identifies where sensitive information may potentially be present in DataStage Job and Sequence Annotations

Yes

-

-

Checks that range lookups are correctly configured

-

Yes

-

Identifies stage columns with names using characters not supported by the Parallel Engine.

Yes

Yes

Yes

Stage Naming Standards for Parallel and Server Jobs and Job Sequences

Yes

Yes

-

Identifies Transformer Stage with an unreferenced Stage Variable (including Loop Variables)

Yes

Yes

Yes

Identify Job parameters within a default value

Yes

-

-

Identifies Join stages where the join key does not match the partitioning key

Yes

Yes

-

Verifies that there is only one data flow in a DataStage job

Yes

-

-

Detect the use of Schema Files

Yes

Yes

-

Identify the use of hardcoded SQL in Database Connectors or Enterprise Database Stages.

Yes

-

-

Identifies Job parameters which are not used within the job.

Yes

Yes

-

Identifies whether a Job has too many Stages

Yes

Yes

-

Identifies stages that are not yet supported by IBM Cloud Pak for Data

Yes

Yes

-

This rule detects the use of Custom stages in Parallel Jobs

Yes

-

-

Identifies link sorts

Yes

Yes

-

Identified job designs with adjacent Transformer stages.

Yes

Yes

-

Verifies that a file is only referenced once in a DataStage job (Sequential File, Complex Flat File and DataSet)

-

-

Yes

Sequence Job with Hardcoded Parameter Values

Yes

Yes

-

Ensures that all Database Connectors and Stages must use valid variants

Yes

-

-

Identify the use of a Rnd() function in Parallel Transformers.

Yes

Yes

-

Identifies where database table references are fully-qualified

Yes

Yes

-

Ensures that all File Stages must use variables for determining paths

Yes

Yes

-

Verifies that a job does not contain one or more prohibited stages

Yes

Yes

Yes

Identifies Job parameters which are not members of a parameter sets

Yes

Yes

Yes

Checks the job name against a blocklist of known bad names (e.g. CopyOf*)

Yes

Yes

Yes

Identify whether the a ‘Job Description’ annotation contains instances of particular arbitrary text. This example rule looks for dates.

Yes

Yes

-

Identifies Jobs with Job Control Routines defined

-

-

Yes

Identify Sequence Job activities with references to non-existent parameters.

Yes

Yes

-

Ensures a Database Connector uses Auto Generated SQL

Yes

Yes

Yes

Identifies Jobs or Sequences where the MettleCI Unit Testing parameter is not present

Yes

-

-

Identifies Data Sets not using the 'Same' partitioning method

Yes

-

-

Identifies Sequential Files with a Reject Mode not set to fail

Yes

-

-

Identifies Parallel Aggregator Stages not preceded by a ‘Check’ Sort Stage.

Yes

-

-

Identifies row limits in debug stages (Peek, Sample, Tail)

Yes

Yes

-

Ensures that all Connectors and Stages must use encrypted Passwords

Yes

Yes

-

Identify Db2 Stages using bulk load with Non Recovery Load set to No

Yes

Yes

-

Ensures that all File Stages must use variables for determining paths

Yes

Yes

Yes

Default Stage Names for Parallel Jobs, Server Jobs, and Job Sequences

Yes

Yes

-

Identify deprecated stages and suggests the recommended alternative