Workstation objects can change even if AutoConfig is turned off. At my
previous employer AutoConfig was turned off; each device had a specific id.
Yet about once or twice a year one of the printers got changed to a
workstation, which raised holy hell when a process tried to print to it.
I filed a PMR with IBM. They confirmed that, "Yes, that can happen during
signon." After much back and forth I filed a DCR: "But it shouldn't
happen." The DCR was finally rejected - working as designed.
Jerry C. Adams
IBM i Programmer/Analyst
You're only as smart as your ERA - Jim Bouton
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: pctech-bounces@xxxxxxxxxxxx [mailto:pctech-bounces@xxxxxxxxxxxx] On
Behalf Of CRPence
Sent: Thursday, January 26, 2012 4:32 PM
To: pctech@xxxxxxxxxxxx
Subject: Re: [PCTECH] Sideways characters
On 26-Jan-2012 11:41 , daparnin@xxxxxxxxxxxxxx wrote:
<<SNIP>>
I did get the problem solved. I found a similar printer on the
system that had a different manufacturer, had host print transform
turned off, and was using a workstation customizing object. I made
the parameters match and it worked fine. Since it had been working
and then suddenly stopped made me think that it was a setting on the
printer. How it had been working for months and suddenly stopped, I
don't know.
I see SJL alluded similarly to my reply [text below] that I had
composed earlier but had hesitated to post. And that a reply to SJL
indicated the creation-date precludes the delete and re-create by an
auto-configuration from being responsible [assuming that the
implementation of autoconfig is to first delete and then re-create; i.e.
irrespective of what may be implied and inferred from messaging by that
feature]. I do know that workstation device descriptions are often only
"changed" versus delete and re-create by auto-config, so I expect the
same could be true of printer device descriptions.
The following may not apply to the scenario in the quoted text,
however the comments could have some value to someone else or another
situation...
If a printer is local attach and the QAUTOCFG is turned on, then I
suppose a printer device could get re-created, and at least the WSCST
would seem unlikely to get associated, except when done explicitly; i.e.
for its being a "customization". Using the device description creation
date\time to review the history for around that date\time would probably
identify such an activity. Or by looking for the auto-configuration
messages, if the creation date had not been collected prior to recovery
actions; dsplog qhst ((*avail *begin)) msgid(cpc2600 cpi2600) I believe,
and then searching the output for the device name. Similarly with the
change date of a printer device description, but then by a review of
both the history and auditing for that time-period; much more difficult
if the dspobjd details for the device had not been spooled prior to
recovery actions. The change could have been effected by a user, or
possibly auto-configuration; for the latter, one might expect that the
WSCST specification would not be lost for a mere "change" by auto-config.?
Regards, Chuck
midrange.com
