IDQ input parameter file error - informatica

In IDQ infacmd I am trying to execute multiple wf with source input parameter file, The first infacmd gets success but the second infacmd mapping fails because of input parameter is taking the default value not the assigned value.

I have got resolved it, I have created a parameter in workflow level and assigned the mapping parameter to wf parameter and called the wf level parameter in the infacmd . It just done my work.

Related

how to Give inputs to Lauterbach script?

I have practice script that take password from dialog box and set it to var. I want to modify it instead of taking password from dialog box it take it from command line like entering parameters to script.
I have read the ref but i can't find it out.
You can call a script with parameters by providing the parameters after the file name. Each parameter should be quoted:
DO my_script.cmm "<my_parameter1>" "<my_parameter2>"
The script can retrieve the parameter like below. In this example the script would fall-back to dialog or error handling if there is no password provided by command line.
PRIVATE &password
PARAMETERS &password
IF "&password"==""
(
;if no password provided from command line,
;then fall back to dialog or error handling.
)
PRINT "Password: &password"
ENDDO

Step Function fails to transfer output of Succeeded State

I have an AWS Step Function with 12 states and out of thousands of executions I've only seen this error occur once which makes me think that this isn't a configuration issue and instead this is an AWS error.
When my Step Function transfers from one state to the next it fails to pass the output from one state as the input to next. A concrete example, Copy Asset passes some data to Verify Asset but somewhere down the line this data disappears. As mentioned before, I've only seen one instance of this error through thousands of executions.
Here's an image describing the issue:
To try to narrow where the execution fails I will write the various states step-by-step:
LambdaFunctionScheduled Copy Asset. This succeeds, and in the UI the input to the execution is visible so everything is working as expected.
LambdaFunctionStarted Copy Asset. The UI shows the empty set {}, strangely this is also expected since successful executions also show the same state.
LambdaFunctionSucceeded Copy Asset. The UI shows the following output:
{ "output": null, "outputDetails": { "truncated": false } }
Why is the output of Copy Asset empty even though it succeeded. All other successful executions correctly pass the output to the next step.
The Copy Asset Lambda takes the input, does some executions and then passes the input as the output so if there are no errors thrown, and the input isn't empty then the output shouldn't be empty either.
My question is how can I retry on this error if it happens and how can I avoid it?

How to pass source value to pre processing one at a time/iterate within the same taskflow?

I’ve tried to assign source row value to InOut parameter/ Mapping variable using SetVariable($$p_file_name, FileName).
But It does not update the value once set. I tried solutions from web :
- SetVariable($$p_file_name, Null) ,
- Taskflow variable with assignment to the mapp variable,
- splitting the mapping into 2 parts ( 1st gets the value in Mapp Var & 2nd tries to use it in pre processing cmd) ,
—UserParameter file permanent sets the value &
- Default value with a empty string.
Nothing worked consistently to update the Inout Parameter/Mapping Variable every time a row is read with a new value from source table.
Note : I’ve the run xcopy manually & it works from cmd prompt using the $$p_file_name as source.
My recommendation is to script with variables the manual xcopy you preformed. Admittedly there are many other solutions though maintaining your own script and variables will give you a consistent result.

Parameter list issue in HP Load Generator

I have a VUGen script that uses a parameter list of type=File with Select Next Row = Unique and Update value on = Once. This file (UsernameAndPassword.dat) is located in a Shared Folder.
When I run the Performance Test with more that 1 VUser, all the VUsers keep only the first record of that parameter. I mean, all the VUsers run with the same user/password values, i.e.:
parameter list
username,password
john,12345
caty,67890
alfred,09876
greg,54321
Vusers 1: john,12345
Vusers 2: john,12345
Vusers 3: john,12345
etc.
However, if I use an internal parameter list (type=file, and so on like above), when I run the test, each VUser obtains a different value of username.
For internal parameter list, I mean the file .dat is wrapped in the script.
How can I read the external file sequentially like an internal parameter list?
A file is a file is a file. When you start your virtual user your parameter file, whether it is sent with your script or referenced on a common drive, will be pulled into RAM on you load generator. This is why you can't write to a parameter file during a test and have the values available for use, because the file which is in use is actually in RAM.
Have you tried setting your block size manually to 1, then update once?
Check the software version of your load generator to the major.minor(patch) level. All sorts of henky things occur when the controller and the load generators are out of sync on a version level.

BuildForge - Passing variables as parameters that are declared as Assing Hidden

I have a build forge job that executes a bat file and intake password as a paramter. If i declare this paramter variable as normal text it works fine. But when I declare password as "Assing Hidden" it doesnt work and throws out error as meniotned below.
Any help is appreciated.
Command I am executing
call MpToSbx.bat SF %account% %password% %REL_NUM% %Track%
Condition
1. Works fine if password is delcared as regular text.
2. When password assigned as hidden it throws out error as below.I feels the command is not iterated correctly some how.
Error Message:
The system cannot find the path specified.
EXEC 'MpToSbx.bat' is not recognized as an internal or external command,
EXEC operable program or batch file.
The most probable cause of this error is that %password% is taken as a single word inside MpToSbx.bat file. To solve this error, first edit that file and change %2 by %~2 (to eliminate quotes in the parameter) and then enclose the password between quotes in the call; for example:
call MpToSbx.bat SF %account% "%password%" %REL_NUM% %Track%