How to use Unix in Informatica?

Use of UNIX in Informatica

Hi guys, you may be well aware of Informatica through the posts that I have
put before.Now we will see how important is Unix in Informatica.
Informatica server can be installed either on Windows or Unix.When
installed on Windows its easy to handle ,but in case of Unix we need to know
about the scripts like PMCMD for aborting workflow and scheduling jobs or
running workflows etc.
For Example in order to start workflow in command line mode we have to
use:
pmcmd StartWorkflow
<<-service|-sv> service [<-domain|-d> domain] [<-timeout|-t> timeout]>
<<-user|-u> username|<-uservar|-uv> userEnvVar>
<<-password|-p> password|<-passwordvar|-pv> passwordEnvVar>
[<-folder|-f> folder]
[<-recovery|-norecovery>]
[<-paramfile> paramfile]
[<-localparamfile|-lpf> localparamfile]
[<-osprofile|-o> OSUser]
[-wait|-nowait]
[<-runinsname|-rin> runInsName]
Workflow
Also apart from that we can use Unix in many other cases also like

To create Paramerter files or some other important files on Informatica

For sending emails to users

To check flat files if they are in proper or not

Used to delete,insert and update during Pre and Post sessions

Types of Tasks in Informatica

There are different types of tasks in Informatica Workflow manager which we
use while running a workflow.I have listed it below.
Tasks
Description
Assignme Used to assign a value to a
nt
workflow variable
Comman Used to run a shell command
d
during the workflow
Control
Used to stop or abort the
workflow
Decision
Tells a condition to evaluate
Email
Used to send email during the
workflow
EventNotifies the Event-Wait task
Raise
that an event has occurred
EventIt waits for the event to
Wait
completed in order to start the
next task
Session
Used to run the mapping
created in Designer buy linking
to session
Timer
It waits for a already timed
event to start

How to Change the Session Log Name in Informatica Workflow-OBIA

Whenever we run the session in Informatica, integration service creates
session log file. By default Session Log File Directory defaults to the service
process variable, $PMSessionLogDir and the Session Log File Name
defaults to $PMSessionLogFile.
In order to change the session log name you can set the
$PMSessionLogFile to Session_test.txt in the parameter file. When you
make this change in the parameter file and run the session, the integration
service creates a session log file named Session_test.txt.
You might also like:

Session Log Parameter in Informatica

Session Log Parameter
The Workflow Manager provides a built-in session parameter named
$PMSessionLogFile. Use $PMSessionLogFile in the session properties to
change the name or location of the session log between runs. When you use
$PMSessionLogFile in the session properties, define the parameter in the
parameter file.
Changing the Session Log Name
You can use $PMSessionLogFile to change the session log name between
sessions. In the General Options settings of the Properties tab, enter
$PMSessionLogFile in the Session Log Filename field. Then define
$PMSessionLogFile in the parameter file. When the PowerCenter Server runs
the session, it creates a session log in the directory listed in the Session Log
File Directory field and names the session log as instructed by the parameter
file. If a session log with the same name already exists, the PowerCenter
Server overwrites the existing file.
For example, in a session, you leave Session Log File Directory set to its
default value, the $PMSessionLogDir server variable. For Session Log File
Name, you enter the session parameter $PMSessionLogFile. In the parameter
file, you set $PMSessionLogFile to TestRun.txt. When you registered the
PowerCenter Server, you defined $PMSessionLogDir as C:/Program
Files/Informatica/PowerCenter Server/SessLogs. When the PowerCenter
Server runs the session, it creates a session log named TextRun.txt in the
C:/Program Files/Informatica/PowerCenter Server/SessLogs directory.
Steps for Using $PMSessionLogFile
Use $PMSessionLogFile when you want to change the name and/or location
of a session log between session runs.
To use the session log parameter:
1. In the session properties, click the General Options settings of the
Properties tab.
2. Enter $PMSessionLogFile in the Session Log File field.
3. If you want $PMSessionLogFile to represent both the session log name
and directory, clear the Session Log File Directory field.
4. Enter a parameter file and directory in the Parameter File Name field.
5. Click OK.
Before you run the session, create the parameter file in the specified
directory and define $PMSessionLogFile.

Difference between Mapping Parameter and Session Parameter

Mapping Parameter
Mapping parameters are
user defined variables
defined at mapping level
or using parameter files.

Session Parameter
Session parameters are used for
specific
purposes
like
defining
connection name or input file name or
bad file name or lookup file name or
output file name
Mapping parameter is set Session parameter is set at the
at the mapping level
session level
Mapping parameter dose Session parameters can change from
not change from session session to session
to session.
Mapping parameter uses Session parameters uses '$'
'$$'
Example:
Example:
$$Datasource_num_id
$DBConnection_[Name]
$InputFile_[Name]
$OutputFile_[Name]
$LookupFile_[Name]
$BadFile_[Name]

Null Values in Aggregate Functions When you configure the Integration

Service, you can choose how you want the Integration Service to handle null
values in aggregate functions(NULL or zero). By default the Integration
services treats null values as Null in Aggregate functions, If you dont want
it to be like that then you can configure to treat null values as Zero.
Types of Session Errors in Informatica Workflow
Session Errors in Informatica can be of two types
1. Fatal error: Allows the Integration service to stop the session
2. Non Fatal error: Dose not forces the session to stop on its first occurrence.
Non Fatal Error:
A non-fatal error is an error that does not force the session to stop on its first
occurrence.To check the occurrence we can set the Stop on Error Option in the
session properties and the Integration service counts these errors.There are mainly
three types of non fatal errors:

Reader Errors: This error happens while reading form the database source or
flat files or any other kind of source systems

Writer Errors: This error occurs while writing to the target or database

Transformation Errors: This error is encountered by the Integration service

while transforming the data.

Fatal errors:
As discussed the fatal errors results in stopping the session. All the reading and
writing are stopped and it rolls back all the data that is not committed to the target
database.
This happens when there is a loss of connection and not able to access source
,target or repository. This can include loss of connection or target database errors,
such as lack of database space to load data.