file-system-test-return-code

This test object that will not be supported in any
released product.  Setting this object allows the next
file system call return code to be specified or to
simulate uninitialized or unistalled volumes.  The POS
will specify the binary format.
Additional information:
A three byte binary value.  The first
byte indicates what function is being effected by
this set.  
value | function  
------+------------------  
1   | PersFSCtl  
2   | PersFSDirClose  
3   | PersFSDirCreate  
4   | PersFSDirDelete  
5   | PersFSDirOpen  
6   | PersFSDirRead  
7   | PersFSDirReadStd  
8   | PersFSDirRewind  
9   | PersFSDirSeek  
10  | PersFSDirTell  
11  | PersFSFileClose  
12  | PersFSFileDelete  
13  | PersFSFileMove  
14  | PersFSFileOpen  
15  | PersFSFileRead  
16  | PersFSFileSeek  
17  | PersFSFileStatus  
18  | PersFSFileWrite  
19  | PersFSFlush  
20  | PersFSVolChk  
21  | PersFSVolFix  
22  | PersFSVolInit  
23  | PersFSVolStatus  
The return value of the function being effected will
return the value -1 to indicate an error occurred.  
The second byte is the
value returned by the next call to PersFSErrNo()
(after the call being effected is called).  Refer to
the 'Copernicus Personality Interface Volume 2 Disk
File System' documentation for a list of values
returned by PersFSErrNo().  The third byte indicates 
which call to the specified file system routine will 
fail.  A value of one means the first call will fail.
A value of two means the second call will fail, and
so on.  Writing this object causes any previous write to 
this object to be invalidated.  
Note: The error triggering 
mechanism is actually implemented at the message 
interface to the file system rather than at the PersFSxxx()
function call interface.  This is easier to do, and 
it is better for NFS because NFS uses the message 
interface rather than the PersFSxxx() functions.  
Fortunately there is a one-to-one mapping between 
messages and PersFSxxx() functions so everything 
works out nicely.  
The printer will uninitialize the mass storage device if
the first byte is one of the values listed below.  
value | meaning  
------+------------------  
101  | Effects the printer state  
102  | Effects the data on the device  
The Moby printer supports 3 volumes zero, so the
second byte must be 0 - 2. The third byte has no meaning
and must be zero.

MIB

HP-LASERJET-COMMON-MIB

OID

.1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.3

Type

scalar

Access

readwrite

Status

mandatory

Parent

settings-file-system

Siblings

10