PackageID uniqueness

Genesis1701d1 — Fri, 06 Dec 2019 16:47:33 GMT

I'm trying to understand publishing packages (in my case using a stored process), and I'm looking at this example from the documentation:

https://documentation.sas.com/?docsetId=publishdg&docsetTarget=n1xvf6fybwq7pvn1j8qt77ech1xz.htm&docsetVersion=9.4&locale=en

In particular, they define two packages. One is the main package:

packageId = 0;
   nameValue="type=(test) coverage=(filtering, transports)";
   CALL PACKAGE_BEGIN(packageId,"Main results package.",
      nameValue, rc);

And one is a secondary package that gets nested in the first later on:

gifpid=0;
CALL PACKAGE_BEGIN(gifpid,"Gif nested package.",'', rc);

Both of these packages have a package ID of 0. How can that work? Isn't the packageID supposed to uniquely identify a package?

Re: PackageID uniqueness

Vince_SAS — Sat, 07 Dec 2019 18:26:17 GMT

Yes, the package ID uniquely identifies the package. I think a zero value for the ID after calling PACKAGE_BEGIN indicates that the cal failed. Check the return code value.

https://go.documentation.sas.com/?docsetId=publishdg&docsetTarget=p1iqk0mjufz28sn10hdjzp6pv5js.htm&docsetVersion=9.4

data _null_;
packageId=0;
rc=0;
desc = 'Nightly run.';
nameValue='';
CALL PACKAGE_BEGIN(packageId, desc, nameValue, rc);
putlog packageId= rc=;
run;

Vince DelGobbo

SAS R&D

topic Re: PackageID uniqueness in Developers

PackageID uniqueness

Re: PackageID uniqueness