16
Chapter 1
FTAM return_codes
inout_dcb->result.return_code
MESSAGE
FTE004_BUFFER_OVERFLOW
CAUSE
The inout_dcb specified is not large enough to hold the
output of the call.
ACTION
You have two options:
• Call the function with the address of a NULL
inout_dcb, thus requesting the interface to
dynamically allocate the output area.
• Call the function with a larger buffer.
MESSAGE
FTE005_INV_CONN_ID
CAUSE
The connection_id from ft_connect() is no longer active
or ft_connect() did not return the connection_id.
ACTION
Call the function with a valid, active connection_id
returned from an ft_connect() request.
MESSAGE
FTE006_NETWORK_UNAVAIL
CAUSE
All contact with ftam_init was lost either because it
was killed or exited.
ACTION
Call ft_aeactivation() to activate another ftam_init. If
the error still occurs, terminate the application and
refer to the OSI Troubleshooting Guide.
MESSAGE
FTE007_NO_REQ_RESOURCES
CAUSE
Current resources are insufficient to honor the request;
virtual memory is exhausted.
ACTION
Check your memory management. Free any unused
resources (e.g., memory), call ft_dfdcb() to free DCBs
that are no longer needed, and call the function again.
Содержание FTAM/9000
Страница 4: ...4 ...
Страница 6: ...6 ...
Страница 10: ...10 ...
Страница 12: ...12 Contents ...
Страница 52: ...52 Chapter1 FTAM return_codes inout_dcb result return_code ...
Страница 66: ...66 Chapter2 HP vendor_codes inout_dcb result vendor_code ...
Страница 88: ...88 Chapter4 Event Management Errors EM vendor_codes ...
Страница 90: ...90 Chapter5 HP FTAM 9000 PICS ...
Страница 98: ...98 Chapter6 Installation Filesets Files Created During Software Installation ...