Software Development Kit (SDK) and API Discussions

Missing ZAPI errno definitions?

kevingraham

In the 4.1 SDK (and earlier versions) many of the ZAPI calls for CIFS (e.g. cifs-share-list-iter-start, cifs-setup-verify-name) specify a possible return value of ESVCDISABLED, however this constant doesn't appear to be defined in the NaErrno stubs (at least for Perl, Python, and Ruby).


Adding to the confusion, some ZAPI calls that would be used to configure/enable the service (e.g. cifs-start and cifs-setup) also list a possible ESVCDISABLED error state. For most use cases of those APIs, it would be expected/normal for the service to be disabled (since they would be invoked to affect the service state).

Is this a documentation error, or am I missing something?

2 REPLIES 2

sens

Hi,

This constant is indeed present in NaErrno files:

NaErrno.pm: line 1604

   use constant ESVCDISABLED => 13200;

NaErrno.py: line 438

      ESVCDISABLED = 13200

NaErrno.rb: line 438

      ESVCDISABLED = 13200

kevingraham

sens wrote:

Hi,

This constant is indeed present in NaErrno files:

NaErrno.pm: line 1604

   use constant ESVCDISABLED => 13200;

Argh, I made the same mistake the SDK docs did. ESVCDISABLED is there for cifs-setup and cifs-setup-*.

However, cifs-session-list-* and cifs-shares-list-* return values reference the elusive ESERVICEDISABLED (ironically, the one that is present is the case where it's usage seems ambiguous)..

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public