
Xprint F.A.Q. Document revision 10 (16.09.2008)
Page 80/89
Reference: None
XP_SHOW_PERMANENT_ID
Context: Introduced in V7.0A to show the new permanent job identifier at job submission.
Description: If set, the client receives a permanent job identifier instead of a local job alias when a
xpadd, xpdel and xpmod are submitted.
Initialisation time: before xpadd -job, xpmod -job or xpdel -job
Possible values: Any value other than 1 disables this functionnality.
Behaviour if unspecified: the default behaviour is kept (local job alias is shown).
Reference: None
XP_SPEC_OBJ
Context: Introduced in V7.0A to enable the use of special objects (Xprint objects whose names begin
with the underscore).
Description: The use of Xprint special objects is activated by setting this environment variable with the
value "XPRINT_SPECIAL_OBJECTS_ALLOWED". In that case, the Xprint naming convention is
modified so that special objects can be handled like any other standard Xprint objects of the same type.
When this environment variable is not set or if it is set with the wrong value, any creation of object
bearing a name beginning with underscore is refused and such objects already existing in the system are
not visible nor accessible any more.
Initialisation time: before the xprint command that refers to special objects.
Possible values: Only the value "XPRINT_SPECIAL_OBJECTS_ALLOWED" is significant. Other
values are ignored.
Behaviour if unspecified: The default Xprint naming convention is kept. It is impossible to create,
handle or view Xprint special objects.
Reference: None
XP_DB_MAX_RETRY
Context: TD #1443 – Pble at OSRAM customer – Bad mastering take over
Description: This variable determines the maximum number of retry when a DB connection is busy.
Initialisation time: Before xpstart
Possible values: max number of retry when DB connection busy
Behaviour if unspecified: value is 90
Reference: Release note Xprint 7.0A20 / PRISMAnet 7.02.00
XP_DBSLEEP_SYNCH
Context: Pble on Linux – DBman2 doesn’t start
Description: This variable determines a sleep to be done before launch DBman2 process.
Initialisation time: Before xpstart
Possible values: 0-99
Behaviour if unspecified: 0
Reference: After PRISMAnet 7.02.02
XP_NOTIF_TIMESTAMP
Context: When a user requires notifications (job, device) via the FILE method, the timestamp is never
put in the event message.
Description: This variable determines where to put the timestamp in the notification message.
Initialisation time: Before xpstart
Possible values: NONE, BEGIN, END
Behaviour if unspecified: BEGIN
Reference: From Xprint 8.0B00
Comentários a estes Manuais