WPCi 2BV[Z !|d2cpi (M)LtTddd,dp@~rQ@HP LaserJet IIIDHPLASIII.PRSdp@~rQ,\,Bj@!|d2GM ZvpdCourier 12cpiPrestige Elite 12cpi (D)Prestige Elite 12cpi Italic (D)HP LaserJet IIIHPLASIII.PRSd6X@8;,\,Bj@a8DocumentgDocument Style StyleXX` `  ` a4DocumentgDocument Style Style . 2kkqva6DocumentgDocument Style Style GX  a5DocumentgDocument Style Style }X(# a2DocumentgDocument Style Style<o   ?  A.  a7DocumentgDocument Style StyleyXX` ` (#` 2t) 7 BibliogrphyBibliography:X (# a1Right ParRight-Aligned Paragraph Numbers:`S@ I.  X(# a2Right ParRight-Aligned Paragraph Numbers C @` A. ` ` (#` a3DocumentgDocument Style Style B b  ?  1.  2  _   a3Right ParRight-Aligned Paragraph Numbers L! ` ` @P 1. ` `  (# a4Right ParRight-Aligned Paragraph Numbers Uj` `  @ a. ` (# a5Right ParRight-Aligned Paragraph Numbers _o` `  @h(1)  hh#(#h a6Right ParRight-Aligned Paragraph Numbersh` `  hh#@$(a) hh#((# 2m  v +B a7Right ParRight-Aligned Paragraph NumberspfJ` `  hh#(@*i) (h-(# a8Right ParRight-Aligned Paragraph NumbersyW"3!` `  hh#(-@p/a) -pp2(#p a1DocumentgDocument Style StyleXqq   l ^) I. ׃  Doc InitInitialize Document Style  0*0*  I. A. 1. a.(1)(a) i) a) I. 1. A. a.(1)(a) i) a)Documentg2[&Tech InitInitialize Technical Style. k I. A. 1. a.(1)(a) i) a) 1 .1 .1 .1 .1 .1 .1 .1 Technicala5TechnicalTechnical Document Style)WD (1) . a6TechnicalTechnical Document Style)D (a) . a2TechnicalTechnical Document Style<6  ?  A.   2"4a3TechnicalTechnical Document Style9Wg  2  1.   a4TechnicalTechnical Document Style8bv{ 2  a.   a1TechnicalTechnical Document StyleF!<  ?  I.   a7TechnicalTechnical Document Style(@D i) . 25TX Ra8TechnicalTechnical Document Style(D a) . PleadingHeader for numbered pleading paperP@n   $] X X` hp x (#%'0*,.8135@8:pQ@tTddd,'dphQQH 2t) 7BibliogrphyBibliogra2g#dp@>pQWm@#X` hp x (#%'0*,.8135@8:pQWm@#Programmers Reference Manual for FIPS PUB 123 Function Library Appendix D: FIPS PUB 123 Function Library Error Handling    tT 3/93` `  $hh*06pp<B  HxxN T DՊ .Appendix D T FIPS PUB 123 Function Library Error Handling 0*$$  tT D.` ` FIPS PUB 123 FUNCTION LIBRARY ERROR HANDLING(#` ` ` The FIPS 123 Function Library does not provide error messages. However, each function returns a value of 0 upon failure and a value of 1 for success as described in section 3.2.2. These function return values provide the programmer with a mechanism for determining that an error occurred during processing. It is possible to determine the cause for library function failure by  tT` examining the status or option values passed into or out of the failed function.(#` ` ` When processing a FIPS 123 DDF opened in 'read' mode, functions which read, backup, and retrieve descriptions may fail if the DDF does not conform to the current version of FIPS PUB 123 (February 28, 1986). When processing a DDF opened in 'write' mode, functions  tT may fail if invoked with an incorrect write option or when creating a file that does not conform to the standard.(#` ` ` In general, for errors occurring within functions operating on files opened in 'read' mode, the programmer should(#`  tT  ` `  o$Verify the existence of the file on the input direct access storage device(#  tT  ` `  o$Verify the file access permission(#  tTx ` `  o$Examine the file for FIPS PUB 123 conformance.(# ` ` For errors occurring within functions operating on files opened in 'write' mode, the programmer should: (#` (#0*$$Ԍ tT ` ` X oX$Ensure that there is sufficient space on the output direct access storage device(#  tT ` `  o$Ensure the output device permits write capability(#  tT ` `  o$Review the write option used or status returned during function failure.(# ` ` The most common cause of function failure in the MSDOS environment is insufficient main or conventional memory available for dynamic memory allocation. (#`