SPI Programming Manual (G06.24+, H06.03+, J06.03+)

SPI Concepts and Protocol
SPI Programming Manual—427506-006
2-53
Sample Error Responses
To indicate that this error list describes an error reported by the file system, FUP gives
the error list the subsystem ID of the file system.
Error List Example 4
Nested error lists (subsystems FUP, SORT, and GUARDLIB):
<ZSPI-TKN-RETCODE> ! y (FUP command failed with
! SORT error)
<ZSPI-TKN-ERRLIST>
<ZSPI-TKN-ERROR>
Z-SSID ! Subsystem ID for FUP
Z-ERROR ! y (FUP command failed with
! SORT error)
<ZFUP-MAP-CMD-ERROR>
Z-COMMAND ! LOAD command
Z-OBJECT ! FILE object type
Z-NAME ! name of file FUP was unable
! to load
<ZSPI-TKN-ERRLIST> ! List from SORT
<ZSPI-TKN-ERROR>
Z-SSID ! Subsystem ID for SORT
Z-ERROR ! 64 (cannot allocate segment)
<ZSPI-TKN-ERRLIST> ! List from operating system
<ZSPI-TKN-ERROR>
Z-SSID ! SSID for procedure library
Z-ERROR ! 43 (no space on disk)
<ZSPI-TKN-PROC-ERR> ! ALLOCATESEGMENT
<ZSPI-TKN-ENDLIST> ! end GUARDLIB error list
<ZSPI-TKN-ENDLIST> ! end SORT error list
<ZSPI-TKN-ENDLIST> ! end FUP error list
In this example, a FUP LOAD command failed because SORT could not allocate an
extended segment. Again, because SORT and the system library procedures
(including ALLOCATESEGMENT) do not have programmatic command interfaces
based on SPI, FUP constructs error lists on their behalf, nesting the error lists to show
the pass-through relationships.