"Pin 1 not initialized" error
Moderators: chulett, rschirm, roy
"Pin 1 not initialized" error
Hello, I have a problem with a server job
The log in Director is:
Info - Read_FLAG_SCARICO: Set NLS locale to US-ENGLISH,US-ENGLISH,US-ENGLISH,US-ENGLISH,US-ENGLISH
Info - Read_FLAG_SCARICO..TRX: DSD.StageRun Active stage starting, tracemode = 0.
Info - Read_FLAG_SCARICO..TRX: NLS stage locale is US-ENGLISH,US-ENGLISH,US-ENGLISH,US-ENGLISH,US-ENGLISH
Info - Read_FLAG_SCARICO..D_STG_LOG_STATUS_GLOBALE:
Info - Read_FLAG_SCARICO..DUMMY: Using project default NLS map ISO8859-1
Warning - Read_FLAG_SCARICO..TRX: Pin 1 not initialized
Fatal - Read_FLAG_SCARICO..TRX: |-100|
Warning - Attempting to Cleanup after ABORT was raised in stage Read_FLAG_SCARICO..TRX
Warning - Read_FLAG_SCARICO..TRX: Pin 1 not initialized
Warning - Read_FLAG_SCARICO..TRX.To_TRX: DSP.Close Error -100 in $DSP.Abort.
The job design is:
OCI ---> Transformer --> Sequential File
Can anybody help me?
Thanks
The log in Director is:
Info - Read_FLAG_SCARICO: Set NLS locale to US-ENGLISH,US-ENGLISH,US-ENGLISH,US-ENGLISH,US-ENGLISH
Info - Read_FLAG_SCARICO..TRX: DSD.StageRun Active stage starting, tracemode = 0.
Info - Read_FLAG_SCARICO..TRX: NLS stage locale is US-ENGLISH,US-ENGLISH,US-ENGLISH,US-ENGLISH,US-ENGLISH
Info - Read_FLAG_SCARICO..D_STG_LOG_STATUS_GLOBALE:
Info - Read_FLAG_SCARICO..DUMMY: Using project default NLS map ISO8859-1
Warning - Read_FLAG_SCARICO..TRX: Pin 1 not initialized
Fatal - Read_FLAG_SCARICO..TRX: |-100|
Warning - Attempting to Cleanup after ABORT was raised in stage Read_FLAG_SCARICO..TRX
Warning - Read_FLAG_SCARICO..TRX: Pin 1 not initialized
Warning - Read_FLAG_SCARICO..TRX.To_TRX: DSP.Close Error -100 in $DSP.Abort.
The job design is:
OCI ---> Transformer --> Sequential File
Can anybody help me?
Thanks
-
- Premium Member
- Posts: 892
- Joined: Thu Oct 16, 2003 5:18 am
What is your OCI stage name? Has this job ever run and/or have any OCI-reading jobs run in this installation? Have you tried recompiling the job?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
OCI stage name is D_STG_LOG_STATUS_GLOBALEArndW wrote:What is your OCI stage name? Has this job ever run and/or have any OCI-reading jobs run in this installation? Have you tried recompiling the job?
All other server reading jobs fail in this installation with the same error!
I have recompiled the job but anything has changed
*All* Jobs? Or just ones that have a certain stage type?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I have seen this caused by people manually editing the DSParams file to insert environment variables. Apparently at 8.1 this is just not safe to do anymore, it causes a corrupted project and the server jobs abort with the "Pin 1 not initialized" error.
Did someone manually edit DSParams to setup the new project?
Did someone manually edit DSParams to setup the new project?
Ok - basically same issue (corrupted project), different cause then.
If you have access to customer support this is time to call them and have them run you through the procedures to recover from a corrupted project.
If you don't have access to customer support, the safest thing to do is to create a new project, dump all your jobs, routines, table definitions, etc. to a large dsx file and then load it into the new project (after you setup environment variables etc). This isn't trivial, but it is the safest way to get rid of the corruption.
If you have access to customer support this is time to call them and have them run you through the procedures to recover from a corrupted project.
If you don't have access to customer support, the safest thing to do is to create a new project, dump all your jobs, routines, table definitions, etc. to a large dsx file and then load it into the new project (after you setup environment variables etc). This isn't trivial, but it is the safest way to get rid of the corruption.
-
- Premium Member
- Posts: 892
- Joined: Thu Oct 16, 2003 5:18 am
There is an IBM APAR that addresses this. Please read below for "JR33952: DS STAGETYPES NOT POPULATED TO UV RESPOSITORY WHEN IMPORTING DSXPROJECTS."
APAR statusClosed as program error.
Error descriptionWhen importing dsx project into Information Server 8.1, the DS
Stagetypes records for the project are imported into XMeta. But
these stagetypes records are not copied to the UV repository.
So, if customer imports the compiled job and tries to run the
job, they get a "pin initialization error". Customer has to
recompile their job or open the stagetype in DS Designer for
that record to be copied over.
Local fix1/ Recompile the job
2/ Open the stagetypes in DS Designer.
RECOMMENDATION:
patch_JR33952_client_windows introduces a new client program
(DSStageTypeUpdater.exe) that can be used to ensure that all
Stage Types which are installed for a project are provisioned
to the server in one command.
This fix is included in 8.1 FP1
****************************************************************
Problem conclusion:
If the job design is compiled, or the missing stage is opened
in the Designer, the equired Stage Type record will be
automatically provisioned onto the server. This will remove
APAR statusClosed as program error.
Error descriptionWhen importing dsx project into Information Server 8.1, the DS
Stagetypes records for the project are imported into XMeta. But
these stagetypes records are not copied to the UV repository.
So, if customer imports the compiled job and tries to run the
job, they get a "pin initialization error". Customer has to
recompile their job or open the stagetype in DS Designer for
that record to be copied over.
Local fix1/ Recompile the job
2/ Open the stagetypes in DS Designer.
RECOMMENDATION:
patch_JR33952_client_windows introduces a new client program
(DSStageTypeUpdater.exe) that can be used to ensure that all
Stage Types which are installed for a project are provisioned
to the server in one command.
This fix is included in 8.1 FP1
****************************************************************
Problem conclusion:
If the job design is compiled, or the missing stage is opened
in the Designer, the equired Stage Type record will be
automatically provisioned onto the server. This will remove