Thanks Ray!
Leonid Frumker
Developer
(847) 286-0336, B4-175B
"Ray Wurlod"
cc:
Subject: Re: Warning message
01/19/2004 02:07
PM
Please respond to
datastage-users
"Printer segment removed" is a purely informational message. It indicates
that a cleanup is being performed so that the new DataStage process can be
given a resource that it requires. That resource is called the "printer
segment" (as Dave said, for historical (UniVerse) reasons).
While it does indicate that an earlier abend occurred, it's not a problem
in and of itself.
----- Original Message -----
From:
lfrumke@sears.com
Date: Mon, 19 Jan 2004 10:15:10 -0600
To:
Subject: Re: Warning message
>
> David,
>
> It just happened first time yesterday with two jobs. There were no
abends.
> We will monitor the process to make sure it won't happen again.
>
> Thank you.
> Leonid Frumker
> Developer
> (847) 286-0336, B4-175B
>
>
>
> "David T. Meeks"
>
> ftware.com> cc:
> Subject: Re:
Warning message
> 01/19/2004 10:16 AM
> Please respond to
> datastage-users
>
>
>
>
>
>
> Ok... Here comes more info than you ever wanted to know about,
> though I'm leaving out tons of the detail... Skip to "Summary" if
> you just want to know the bottom line...
>
> The DS Server product deals with interprocess communcation via the
> usage of shared memory. A number of different regions are set up,
> including one global segment that controls concurrency control,
> licensing, status, etc... one that maintains all NLS maps and locales
> if NLS is enabled, and what is known as the 'Printer Segment' that
> you see here...
>
> Each process that is created, at initialization time, connects to the
> aforementioned global segments, and creates it's own local Printer
> Segment. Any subsequent processes created as children will
> share this one printer segment.
>
> Upon startup, if a job goes to initialize itself, it checks to see if
that
> shared memory segment is in use (each initialization routine has
> a mechanism to determine a segment ID that should be relatively
> unique to them). If it finds one out there, which generally indicates
> an abnormal condition, it will cleanup and remove it before starting.
>
> Now, typically, the only way you would typically see this is if you
> had a job abort in some very ugly fashion, preventing the job from
> going through it's normal cleanup activities.
>
> Note One: this doesn't mean your normal 'aborted' job, such as that
> caused by having bad data, poorly formed job, etc... but rather,
> something where the underlying process itself aborted (core dump,
> signal, etc...)
>
> Note Two: It's called a 'Printer' segment for historical reasons...
>
> Summary:
>
> This represents the cleanup activity of a DS Engine process, upon
> finding a previously aborted job. In and of itself, it represents normal
> behavior. However, what it represents is that some previous job has
> abnormally aborted and left this segment around.
>
> If you are seeing this message on a regular basis, and don't believe
> you are having jobs abnormally abort at any point, contact support
> as it could represent a problem.
>
> At 09:45 AM 1/19/2004 -0600, you wrote:
> >Hi,
> >
> >Have anybody seen this warning message and what is this all about?
> >
> >PRINTER memory segment removed
> >
> >Thank you.
> >Leonid Frumker
>
> ========================================================================
> David T. Meeks || "All my life I'm taken by surprise
> Architect, Technology Office || I'm someone's waste of time
> Ascential Software || Now I walk a balanced line
>
dave.meeks@ascentialsoftware.com || and step into tomorrow" - IQ
> ========================================================================
>
>
>
>
>