Error while creating new jobs in DataStage

If you face the error error similar to below can occur when trying to save a newly created job:

Error On CREATE.FILE command
Creating file "RT_CONFIG4817 as type 30, mkdbfile: connot create file
RT_CONFIG4817. Unable to create operating system file "RT_CONFIG4817"

How to Schedule Jobs and Sequencers via Datastage Scheduler

Datastage Native Job Scheduler

Datastage includes a scheduling option, it does not have its own. DataStage doesn't include a "scheduler" so leverages the underlying O/S. For UNIX that means cron and a check of the crontab entries for the scheduling user will have what you need. DataStage leverages cron for recurring schedules and at for 'one off' schedules. For Windows, it uses scheduled tasks of Windows. 

From the operating system command line, logged in as the scheduling user, a "crontab -l" will list the scheduled jobs.

Error : Datastage Job Aborts with "The record is too big to fit in a block"

To fix this error you need to increase the block size to accommodate the record size:

1. Log into Designer and open the job.

2. Open the job properties--> parameters-->add environment variable and select: 
   APT_DEFAULT_TRANSPORT_BLOCK_SIZE

Failure to connect to DataStage services tier: invalid port

When you attempt to start one of the DataStage clients, the following message is displayed:

Failed to authenticate
the current user against the selected Domain:  Could not connect to
server [servername] on port [portnumber].

DataStage compile error 65280; Couldn't change directory to /tmp

Error when trying to compile parallel (PX) jobs in a project.

The compilation errors include the following:

Subprocess command failed with exit status 65280.
Output from subprocess: Couldn't change directory to /tmp : No such file or directory

What can you delete to free up disk space in IBM InfoSphere Information Server

What can you delete to free up disk space in IBM InfoSphere Information Server when disks are becoming full?

What to do ????

Here are some things you can do to clean up space:

• Clear the &PH& file in the Project directory. There is a &PH& directory in each DataStage project directory, which contains information about active stages that is used for diagnostic purposes. The &PH& directory is added to every time a job is run, and needs periodic cleaning out.
  

Commands to delete files in &PH& directories in IBM InfoSphere DataStage

How should we manage cleaning up the &PH& directories for my DataStage projects? Can the process be automated?

Files in the &PH& directories under DataStage project directories store runtime information when jobs are run and need to be cleared out periodically.

 

Steps :

To clear the &PH& directory from within DataStage:

Datastage Job Scheduler

Datastage includes a scheduling option, it does not have its own. DataStage doesn't include a "scheduler" so leverages the underlying O/S. For UNIX that means cron and a check of the crontab entries for the scheduling user will have what you need. DataStage leverages cron for recurring schedules and at for 'one off' schedules. For Windows, it uses scheduled tasks of Windows.

From the operating system command line, logged in as the scheduling user, a "crontab -l" will list the scheduled jobs.

Schema File in Datastage

Schema files and partial Schemas:

You can also specify the meta data for a stage in a plain text file known as a schema file. This is not stored in the Repository but you could, for example, keep it in a document management or source code control system, or publish it on an intranet site.

DataStage-Director: Unable to open DICT 'RT_LOG###'

When attempting to open a job log in Director, user gets the following error message: Error selecting from log file RT_LOG### Error was: Unable to open DICT 'RT_LOG###'. This is because the D_RT_LOG file is missing from the projects directory.

DS Director Error (Unable to open Specific folder)

Reason -

Unable to open a specific folder in the director, it prompts the following error message. when I say, 'OK' , Director gets close. But there is no problem with the other folders. The Error message is "Run-time error '457'; This key is already associated with an element of this collection"

Something about DataStage Phantom(&PH& - Universe DB file) directory

&PH& directory which is a UniData/UniVerse/U2 file structure in the DataStage contain the files which get created during a job's execution. 
The two letters in the name of the directory hint to the word "phantom" which is the naming convention in DataStage for background processes. Every time a job runs, it generates these logs which contain the status of the different phantom processes generated during the run. 
There are two types of the files that can be seen in &PH& directory one which starts from DSD.RUN and another one which starts from DSD.OshMonitor. 

Know your DataStage Jobs Status without Director

Hi All
I am getting lot of comments abt a post in which I wrote a script for Monitoring the job without director, But I have removed that due to some code issue.

Here, I wrote a small script to check the job status without director...

DataStage FAQ1

1. What are the ways to execute DataStage jobs?

A job can be run using a few different methods:

* from DataStage Director (menu Job -> Run now...)

* from command line using a dsjob command

* DataStage routine can run a job (DsRunJob command)

* by a job sequencer

2. How to invoke a DataStage shell command?

DataStage shell commands can be invoked from :

* DataStage administrator (projects tab -> Command)

* Telnet client connected to the DataStage server