
---

# SAS Packages Framework, version `20260727`

---

- [SAS Packages Framework help](#helpinfo)
  * [the `installPackage` macro](#installpackage)
  * [the `helpPackage` macro](#helppackage)
  * [the `loadPackage` macro](#loadpackage)
  * [the `loadPackageS` macro](#loadpackages)
  * [the `unloadPackage` macro](#unloadpackage)
  * [the `listPackages` macro](#listpackages)
  * [the `verifyPackage` macro](#verifypackage)
  * [the `previewPackage` macro](#previewPackage)
  * [the `generatePackage` macro](#generatepackage)
  * [the `extendPackagesFileref` macro](#extendpackagesfileref)
  * [the `loadPackageAddCnt` macro](#loadpackageaddcnt)
  * [the `requestPackage` macro](#requestpackage)
  * [the `splitCodeForPackage` macro](#splitcodeforpackage)
  * [the `relocatePackage` macro](#relocatepackage)
  * [the `isPackagesFilerefOK` macro](#ispackagesfilerefok)
  * [the `SasPackagesFrameworkNotes` macro](#saspackagesframeworknotes)
  * [the `bundlePackages` macro](#bundlepackages)
  * [the `unbundlePackages` macro](#unbundlepackages)
  * [Some more examples](#some-more-examples)

--------------------------------------------------------------------------------------------


##      This is short SAS Packages Framework help information <a name="helpinfo"></a>

A **SAS package** is an automatically generated, single, stand alone *zip* file containing organized and ordered code structures, created by the developer and extended with additional automatically generated "driving" files (i.e. description, metadata, load, unload, and help files).

The *purpose of a package* is to be a simple, and easy to access, code sharing medium, which will allow: on the one hand, to separate the code complex dependencies created by the developer from the user experience with the final product and, on the other hand, reduce developer's and user's unnecessary frustration related to a remote deployment process.

In this repository we are presenting the **SAS Packages Framework** which allows to develop and use SAS packages. The latest version of SPF is **`20260727`**.

**To get started with SAS Packages** try this [**`Introduction to SAS Packages`**](https://youtube.com/playlist?list=PLeMzGEImIT5eV13IGXQIgWmTFCJt_cLZG&si=ElQm0_ifq76mvUbq "Introduction to SAS Packages video series") video series or [**`Getting Started with SAS Packages`**](https://github.com/yabwon/SAS_PACKAGES/blob/main/SPF/Documentation/Getting_Started_with_SAS_Packages.pdf "Getting Started with SAS Packages") presentation (see the `./SPF/Documentation` directory).

**The documentation and more advance reading** would be the [**`SAS(r) packages - the way to share (a how to)- Paper 4725-2020 - extended.pdf`**](https://github.com/yabwon/SAS_PACKAGES/blob/main/SPF/Documentation/SAS(r)%20packages%20-%20the%20way%20to%20share%20(a%20how%20to)-%20Paper%204725-2020%20-%20extended.pdf "SAS packages - the way to share") article (see the `./SPF/Documentation` directory).

*Note:* Filenames references `packages` and `package` are **reserved keywords.**
The first one should be used to point local folder with packages and the framework.
The second is used internally by macros.
After assigning the directory do not change them when using the SPF since it may affect stability of the framework.


##      Tutorial on SAS Packages and SAS Packages Framework

"From 0 to hero" tutorial explaining what are SAS Packages, and how to work with
them using the SPF can be found [**HERE**](https://github.com/yabwon/HoW-SASPackages).

--------------------------------------------------------------------------------------------


##       This is short help information for the `installPackage` macro <a name="installpackage"></a>
--------------------------------------------------------------------------------------------

 Macro to install SAS packages, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and embedded inside the zip.

 The `%installPackage()` macro installs the package zip
 in the packages folder. The process of installation is equivalent with
 manual downloading the package zip file into the packages folder.

 In case the packages fileref is a multi-directory one the first directory
 will be selected as a destination.

--------------------------------------------------------------------------------------------

### Parameters:

 1. `packagesNames` Space separated list of packages names _without_
                    the zip extension, e.g. myPackage1 myPackage2,
                    Required and not null, default use case:
                    `%installPackage(myPackage1 myPackage2)`.
                    If empty displays this help information.
                    If the package name is *SPFinit* or *SASPackagesFramework*
                    then the framework itself is downloaded.

 - `sourcePath=`   Location of the package, e.g. "www.some.web.page/" (mind the "/" at the end of the path!)
                   Current default location for packages is:
                   `https://github.com/SASPAC/`
                   Current default location for the framework is:
                   `https://raw.githubusercontent.com/yabwon/SAS_PACKAGES/main/SPF/`

 - `mirror=`       Indicates which web location for packages installation is used.
                   Value `0` or `SASPAC` indicates:
                   `https://github.com/SASPAC/`
                   Value `1` indicates:
                   `https://raw.githubusercontent.com/yabwon/SAS_PACKAGES/main`
                   Value `2` indicates:
                   `https://pages.mini.pw.edu.pl/~jablonskib/SASpublic/SAS_PACKAGES`
                   Value `3` or `PharmaForest` indicates:
                   `https://github.com/PharmaForest/`
                   Default value is `0`.

 - `version=`      Indicates which historical version of a package to install.
                   Historical version are currently available only if `mirror=0` is set.
                   Default value is null which means "install the latest".
                   When there are multiple packages to install version variable
                   is scan sequentially.

 - `replace=`      When set to `1` and a package file exists, it forces the package
                   file replacement by the new downloaded file.
                   It is a binary indicator ('0' or '1'). Default value is `1`.

 - `backup=`       When set to `1` and a package file exists, it creates a backup copy
                   of the package file. The backup copy is created with a suffix of the
                   following format: `_BCKP_yyyymmddJJMMSS`.
                   If `replace=0` then `backup` is set to `0`.
                   It is a binary indicator ('0' or '1'). Default value is `0`.

 - `URLuser=`      A user name for the password protected URLs, no quotes needed.

 - `URLpass=`      A password for the password protected URLs, no quotes needed.

 - `URLoptions=`   Options for the `sourcePath` URLs filename. Consult the SAS
                   documentation for the further details.

 - `loadAddCnt=`   *Optional.* A package zip may contain additional
                   content. The option indicates if it should be loaded
                   Default value of zero (`0`) means "No", one (`1`)
                   means "Yes". Content is extracted into the **packages** fileref
                   directory in `<packageName>_AdditionalContent` folder.
                   For other locations use `%loadPackageAddCnt()` macro.

 - `instDoc=`      *Optional.* A package may be provided with a markdown file
                   containing combined documentation of the package. The option
                   indicates if the `.md` file should be also downloaded.
                   Default value of zero (`0`) means "No", one (`1`) means "Yes".

 - `SFRCVN=`      *Optional.* Provides a NAME for a macro variable to store value of the
                  *success-failure return code* of the installation process. Return value
                  has the following form: `<number of successes>.<number of failures>`
                  The macro variable is created as a *global* macro variable.

 - `github=`      *Optional.* A name of a user or an organization in GitHub.
                  Allows an easy set of the search path for packages available on GitHub:
                   `https://github.com/<github>/<packagename>/raw/.../`
                  All characters except `[A-z0-9_.-]` are compressed.

  - `githubRepo=`  *Optional.* A name of a repository in GitHub.
                   Allows an easy set of the search path for packages available on GitHub:
                    `https://github.com/<github>/<githubRepo>/raw/.../`
                   By default lowercase name of installed package is used.

  - `githubToken=` *Optional.* A fine-grained personal access token for GitHub.
                   When the value is non-missing it triggers GitHub API access to
                   private repositories. Of course the token used has to be configured
                   properly for the access.
                   Read GitHub documentation to learn how to create and setup your token:
                   `https://docs.github.com/en/authentication/`
                    `keeping-your-account-and-data-secure/`
                     `managing-your-personal-access-tokens`
                      `#creating-a-fine-grained-personal-access-token`
                   (lines break added for easier reading)
                   Public repositories do not need authentication.
                   [NOTE!] This feature is experimental in this release.

--------------------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation` to learn more.

 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example ################################################################################

   Enabling the SAS Package Framework
   from the local directory and installing & loading
   the SQLinDS package from the Internet.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
%include packages(SPFinit.sas);      %* enable the framework;

%installPackage(SQLinDS)  %* install the package from the Internet;
%helpPackage(SQLinDS)     %* get help about the package;
%loadPackage(SQLinDS)     %* load the package content into the SAS session;
%unloadPackage(SQLinDS)   %* unload the package content from the SAS session;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

### Example ################################################################################

   Enabling the SAS Package Framework
   from the local directory and installing & loading
   multiple packages with versions from the Internet.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
filename packages "C:/SAS_PACKAGES";
%include packages(SPFinit.sas);

%installPackage(baseplus(1.17) macroarray(1.0) dfa(0.5) GSM)
%loadPackageS(GSM, baseplus(1.17), macroarray(1.0), dfa(0.5))
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


##       This is short help information for the `helpPackage` macro <a name="helppackage"></a>
-------------------------------------------------------------------------------

 Macro to get help about SAS packages, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and provided with
 a single `help.sas` file (also embedded inside the zip).

 The `%helpPackage()` macro prints in the SAS log help
 information about the package provided by the developer.

-------------------------------------------------------------------------------

### Parameters:

 1. `packageName`      *Required.* Name of a package, e.g. myPackage,
                       Required and not null, default use case:
                        `%helpPackage(myPackage).`
                       If empty displays this help information.

 2. `helpKeyword`      *Optional.*  A phrase to search in help,
                       - when empty prints description,
                       - "*" means: print all help,
                       - "license" prints the license.

 - `path=`             *Optional.* Location of a package. By default it
                       looks for location of the **packages** fileref, i.e.
                        `%sysfunc(pathname(packages))`

 - `options=`          *Optional.* Possible options for ZIP filename,
                       default value: `LOWCASE_MEMNAME`

 - `source2=`          *Optional.* Option to print out details about
                       what is loaded, null by default.

 - `zip=`              Standard package is zip (lowcase),
                        e.g. `%helpPackage(PiPackage)`.
                       If the zip is not available use a folder.
                       Unpack data to "pipackage.disk" folder
                       and use helpPackage in the following form:
                        `%helpPackage(PiPackage, , zip=disk, options=)`

 - `packageContentDS=` *Optional.* Indicates if a data set with package
                       content should be generated in `WORK`,
                       with default value (`0`) the dataset is not produced,
                       if set to `1` then `WORK.packageName_content`.

-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.

 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

## Example ####################################################################

   Enabling the SAS Package Framework
   from the local directory and installing & loading
   the SQLinDS package from the Internet.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
%include packages(SPFinit.sas);      %* enable the framework;

%installPackage(SQLinDS)  %* install the package from the Internet;
%helpPackage(SQLinDS)     %* get help about the package;
%loadPackage(SQLinDS)     %* load the package content into the SAS session;
%unloadPackage(SQLinDS)   %* unload the package content from the SAS session;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---

##      This is short help information for the `loadPackage` macro <a name="loadpackage"></a>
-------------------------------------------------------------------------------

 Macro to *load* SAS packages, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and included by
 a single `load.sas` file (also embedded inside the zip).

 The `%loadPackage()` macro loads package content, i.e. macros,
 functions, formats, etc., from the zip into the SAS session.

-------------------------------------------------------------------------------
### Parameters:

 1. `packageName`      *Required.* Name of a package, e.g. myPackage,
                       Required and not null, default use case:
                        `%loadPackage(myPackage).`
                       If empty displays this help information.

 - `path=`             *Optional.* Location of a package. By default it
                       looks for location of the **packages** fileref, i.e.
                        `%sysfunc(pathname(packages))`

 - `options=`          *Optional.* Possible options for ZIP filename,
                       default value: `LOWCASE_MEMNAME`

 - `source2=`          *Optional.* Option to print out details about
                       what is loaded, null by default.

 - `requiredVersion=`  *Optional.* Option to test if the loaded
                       package is provided in required version,
                       default value: `.`

 - `lazyData=`         *Optional.* A space separated list of names of lazy
                       datasets to be loaded. If not null datasets from the
                       list are loaded instead of the package.
                       An asterisk (*) means *load all lazy datasets*.

 - `zip=`              *Optional.* Standard package is zip (lowcase),
                        e.g. `%loadPackage(PiPackage)`.
                       If the zip is not available use a folder.
                       Unpack data to "pipackage.disk" folder
                       and use loadPackage in the following form:
                        `%loadPackage(PiPackage, zip=disk, options=)`

 - `cherryPick=`       *Optional.* A space separated list of selected elements
                       of the package to be loaded into the SAS session.
                       Default value of an asterisk (*) means:
                       "load all elements of the package".

 - `loadAddCnt=`       *Optional.* A package zip may contain additional
                       content. The option indicates if it should be loaded
                       Default value of zero (`0`) means "No", one (`1`)
                       means "Yes". Content is extracted into the **Work**
                       directory in `<packageName>_AdditionalContent` folder.
                       For other locations use `%loadPackageAddCnt()` macro.

 - `suppressExec=`     *Optional.* Indicates if loading of `exec` type files
                       should be suppressed, default value is `0`,
                       when set to `1` `exec` files are *not* loaded

 - `DS2force=`         *Optional.* Indicates if loading of `PROC DS2` packages
                       or threads should overwrite existing SAS data sets.
                       Default value of `0` means "do not overwrite".

-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.

 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

## Example 1 ##################################################################

   Enabling the SAS Package Framework
   from the local directory and installing & loading
   the SQLinDS package from the Internet.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
%include packages(SPFinit.sas);      %* enable the framework;

%installPackage(SQLinDS)  %* install the package from the Internet;
%helpPackage(SQLinDS)     %* get help about the package;
%loadPackage(SQLinDS)     %* load the package content into the SAS session;
%unloadPackage(SQLinDS)   %* unload the package content from the SAS session;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

## Example 2 ##################################################################

   Enabling the SAS Package Framework
   from the local directory and installing & cherry picking
   elements of the BasePlus package.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
%include packages(SPFinit.sas);      %* enable the framework;

%installPackage(BasePlus) %* install the package from the Internet;
%loadPackage(BasePlus, cherryPick=getVars) %* cherry pick the content;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

## Utility macros generated during loading a package ###########################

If a package contains IML modules or CASL user defined functions additional
utility macros for IML Modules and CASL UDFs are generated when package is loaded.

Macros are generated with the following names: `%<packageName>IML()` and `%<packageName>CASLudf()`.

Their purpose is to make loading of Modules or UDFs (with potentially multiple
dependencies) easy in Proc IML and Proc CAS.

Run them, accordingly, as the first line in the Proc IML or Proc CAS to access the package content.
For Proc IML the use is as follows:
~~~~~~sas
  proc IML;
    %<packageName>IML()

    <... your code using IML modules from the package ...>
  quit;
~~~~~~
For Proc CAS the use is as follows:
~~~~~~sas
  proc CAS;
    %<packageName>CASLudf()

    <... your code using CASL UDFs from the package ...>
  quit;
~~~~~~

If a utility macro is generated appropriate note and a code snippet
is printed in the log of the package loading process.

In 99% cases macros are used with default parameters values but,
in case when deeper insight about macros parameters is needed,
help info is printed in the log when the following code is run:
~~~~~~sas
  %<packageName>IML(list=HELP)
~~~~~~
or
~~~~~~sas
  %<packageName>CASLudf(list=HELP)
~~~~~~

If created, those macros are automatically deleted when the `%unloadPackage()` macro is run.

---

##      This is short help information for the `loadPackageS` macro <a name="loadpackages"></a>
-------------------------------------------------------------------------------

 Macro wrapper for the loadPackage macro, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and embedded inside the zip.

 The `%loadPackageS()` allows to load multiple packages at one time,
 *ONLY* from the *ZIP* with *DEFAULT OPTIONS*, into the SAS session.

### Parameters:

 1. `packagesNames`  A comma separated list of packages names,
                     e.g. myPackage, myPackage1, myPackage2, myPackage3
                     Required and not null, default use case:
                      `%loadPackageS(myPackage1, myPackage2, myPackage3)`.
                     Package version, in brackets behind a package name, can
                     be provided, example is the following:
                      `%loadPackageS(myPackage1(1.7), myPackage2(4.2))`.
                     If empty displays this help information.


-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.

 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example ###################################################################

   Enabling the SAS Package Framework
   from the local directory and installing & loading
   the SQLinDS package from the Internet.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
%include packages(SPFinit.sas);      %* enable the framework;

%installPackage(SQLinDS DFA)   %* install packages from the Internet;
%loadPackageS(SQLinDS, DFA)    %* load packages content into the SAS session;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-----------------------------------------------------------------------------------------


##      This is short help information for the `unloadPackage` macro <a name="unloadpackage"></a>
-------------------------------------------------------------------------------

 Macro to unload SAS packages, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and provided with
 a single `unload.sas` file (also embedded inside the zip).

 The `%unloadPackage()` macro clears the package content
 from the SAS session.

-------------------------------------------------------------------------------

### Parameters:

 1. `packageName`      *Required.* Name of a package, e.g. myPackage,
                       Required and not null, default use case:
                        `%unloadPackage(myPackage).`
                       If empty displays this help information.

 - `path=`             *Optional.* Location of a package. By default it
                       looks for location of the **packages** fileref, i.e.
                        `%sysfunc(pathname(packages))`

 - `options=`          *Optional.* Possible options for ZIP filename,
                       default value: `LOWCASE_MEMNAME`

 - `source2=`          *Optional.* Option to print out details about
                       what is loaded, null by default.

 - `zip=`              Standard package is zip (lowcase),
                        e.g. `%unloadPackage(PiPackage)`.
                       If the zip is not available use a folder.
                       Unpack data to "pipackage.disk" folder
                       and use unloadPackage in the following form:
                        `%unloadPackage(PiPackage, zip=disk, options=)`

-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.

 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example ###################################################################

   Enabling the SAS Package Framework
   from the local directory and installing & loading
   the SQLinDS package from the Internet.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
%include packages(SPFinit.sas);      %* enable the framework;

%installPackage(SQLinDS)  %* install the package from the Internet;
%helpPackage(SQLinDS)     %* get help about the package;
%loadPackage(SQLinDS)     %* load the package content into the SAS session;
%unloadPackage(SQLinDS)   %* unload the package content from the SAS session;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


##       This is short help information for the `listPackages` macro <a name="listpackages"></a>
-----------------------------------------------------------------------------------------

 Macro to list available SAS packages, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and embedded inside the zip.

 The `%listPackages()` macro lists packages available
 in the packages folder. List is printed in the SAS Log.

### Parameters:

 1. `listDataSet`  Name of a SAS data set to store results in.
                   No data set options are honored.

 - `quiet=`      *Optional.* Indicates if the LOG printout should be suspended.
                 Default value of zero (`0`) means "Do printout", other means "No".

 When used as: `%listPackages(HELP)` it displays this help information.

-----------------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.

 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example #############################################################################

   Enabling the SAS Package Framework
   from the local directory and listing
   available packages.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
%include packages(SPFinit.sas);      %* enable the framework;

%listPackages()                      %* list available packages;

%listPackages(ListDS,quiet=1)        %* save packages list in ListDS data set;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


##      This is short help information for the `verifyPackage` macro <a name="verifypackage"></a>
-------------------------------------------------------------------------------

 Macro to verify SAS package with it hash digest, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and embedded inside the zip.

 The `%verifyPackage()` macro generate package SHA256 hash
 and compares it with the one provided by the user.
 Works with `zip` packages only.


 *Minimum SAS version required for the process is 9.4M6.*

### Parameters:

 1. `packageName`      Name of a package, e.g. myPackage,
                       Required and not null, default use case:
                        `%loadPackage(myPackage)`.
                       If empty displays this help information.

 - `hash=`             A value of the package `SHA256` hash.
                       Provided by the user. When the value is not provided
                       then macro calculates `SHA256`, `SHA1`, and `MD5`
                       digests and display then in the log.

 - `path=`             Location of a package. By default it looks for
                       location of the "packages" fileref, i.e.
                        `%sysfunc(pathname(packages))`

-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.

### Example ###################################################################

   Enabling the SAS Package Framework
   from the local directory and installing & loading
   the SQLinDS package from the Internet.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
filename packages "C:/SAS_PACKAGES"; %* set-up a directory for packages;
%include packages(SPFinit.sas);      %* enable the framework;

%installPackage(SQLinDS)  %* install the package from the Internet;
%verifyPackage(SQLinDS,   %* verify the package with provided hash;
               hash=HDA478ANJ3HKHRY327FGE88HF89VH89HFFFV73GCV98RF390VB4)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

##    This is short help information for the `previewPackage` macro <a name="previewpackage"></a>
-------------------------------------------------------------------------------

 Macro to get preview of a SAS packages, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and provided with
 a single `preview.sas` file (also embedded inside the zip).

 The `%previewPackage()` macro prints, in the SAS log, content
 of a SAS package. Code of a package is printed out.

-------------------------------------------------------------------------------

### Parameters:

 1. `packageName`      *Required.* Name of a package, e.g. myPackage,
                       Required and not null, default use case:
                        `%previewPackage(myPackage).`
                       If empty displays this help information.

 2. `helpKeyword`      *Optional.*  A phrase to search in preview,
                       - when empty prints description,
                       - "*" means: print all preview,
                       - "license" prints the license.

 - `path=`             *Optional.* Location of a package. By default it
                       looks for location of the **packages** fileref, i.e.
                        `%sysfunc(pathname(packages))`

 - `options=`          *Optional.* Possible options for ZIP filename,
                       default value: `LOWCASE_MEMNAME`

 - `source2=`          *Optional.* Option to print out details about
                       what is loaded, null by default.

 - `zip=`              Standard package is zip (lowcase),
                        e.g. `%previewPackage(PiPackage)`.
                       If the zip is not available use a folder.
                       Unpack data to "pipackage.disk" folder
                       and use previewPackage in the following form:
                        `%previewPackage(PiPackage, , zip=disk, options=)`

-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.

 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example ###################################################################

   Enabling the SAS Package Framework
   from the local directory and installing & loading
   the SQLinDS package from the Internet.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
%include packages(SPFinit.sas);      %* enable the framework;

%installPackage(SQLinDS)  %* install the package from the Internet;
%previewPackage(SQLinDS)  %* get content of the package;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

##      This is short help information for the `generatePackage` macro <a name="generatepackage"></a>
-------------------------------------------------------------------------------

 Macro to generate SAS packages, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and embedded inside the zip.

 The `%generatePackage()` macro generates SAS packages.
 It wraps-up the package content, i.e. macros, functions, formats, etc.,
 into the zip file and generate all metadata content required by other
 macros from the SAS Packages Framework.

-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to read about the details of package generation process.

### Parameters:

 1. `filesLocation=`      Location of package files, example value:
                           `%sysfunc(pathname(work))/packagename`.
                          Default use case:
                           `%generatePackage(filesLocation=/path/to/packagename)`
                          If empty displays this help information.

 - `buildLocation=`       Points to a location where the ZIP file with the package
                          should be generated. If the value is null (default)
                          the `filesLocation=` value is used.

 Testing parameters:

 - `testPackage=`         Indicator if tests should be executed.
                          Default value: `Y`, means "execute tests"

 - `packages=`            Location of other packages for testing
                          if there are dependencies in loading the package.
                          Has to be a single directory, if more than one are
                          provided than only the first is used.
                          If path to location contains spaces it should be quoted!

 - `testResults=`         Location where tests results should be stored,
                          if null (the default) then the session WORK is used.

 - `workInTestResults=`   Indicates if WORK directories for test sessions should
                          be located in the same place as results.
                          The default value: `0` means "do not do this".
                          Available values are `0` and `1`.

 - `testWorkPath=`        Points a location where tests sessions work directories
                          should be stored. By default it is null what means that
                          a sub-directory of the main SAS session WORK is used.
                          Takes precedence over `workInTestResults=`.

 - `sasexe=`              Location of a DIRECTORY where the SAS binary is located,
                          if null (the default) then the `!SASROOT` is used.

 - `sascfgFile=`          Location of a FILE with testing session configuration
                          parameters, if null (the default) then no configuration
                          file is pointed during the SAS invocation,
                          if set to `DEF` then the `!SASROOT/sasv9.cfg` is used.

 - `delTestWork=`         Indicates if `WORK` directories generated by user tests
                          should be deleted, i.e. the (NO)WORKTERM option is set.
                          The default value: `1` means "delete tests work".
                          Available values are `0` and `1`.

 Documentation parameters:

 - `markdownDoc=`         Indicates if a markdown file with documentation
                          be generated from help information blocks.
                          The default value: `0` means "do not generate the file".
                          Available values are `0` and `1`.

 - `easyArch=`            When creating documentation file (`markdownDoc=1`)
                          indicates if a copy of the zip and markdown files
                          with the version number in the file name be created
                          The default value: `0` means "do not create files".
                          Available values are `0` and `1`.

 - `archLocation=`        Location for versioned package ZIP file (if `easyArch=1`)
                          If empty (default) the `buildLocation` value is used.

-------------------------------------------------------------------------------

Locate all files with code in base folder, i.e. at `filesLocation` directory.

Remember to prepare the `description.sas` file for you package.
The colon (:) is a field separator and is restricted
in lines of the header part.
The file should contain the following obligatory information:

--------------------------------------------------------------------------------------------
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
/*>> **HEADER** <<*/
Type: Package
Package: PackageName
Title: A title/brief info for log note about your package.
Version: X.Y.Z
Author: Firstname1 Lastname1 (xxxxxx1@yyyyy.com), Firstname2 Lastname2 (xxxxxx2@yyyyy.com)
Maintainer: Firstname Lastname (xxxxxx@yyyyy.com)
License: MIT
Encoding: UTF8

Required: "Base SAS Software"                    :%*optional, COMMA separated, QUOTED list, names of required SAS products, values must be like from "proc setinit" output *;
ReqPackages: "macroArray (0.1)", "DFA (0.1)"     :%*optional, COMMA separated, QUOTED list, names of required packages *;

/*>> **DESCRIPTION** <<*/
/*>> All the text below will be used in help <<*/
DESCRIPTION START:
  Xxxxxxxxxxx xxxxxxx xxxxxx xxxxxxxx xxxxxxxx. Xxxxxxx
  xxxx xxxxxxxxxxxx xx xxxxxxxxxxx xxxxxx. Xxxxxxx xxx
  xxxx xxxxxx. Xxxxxxxxxxxxx xxxxxxxxxx xxxxxxx.
DESCRIPTION END:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--------------------------------------------------------------------------------------------

Name of the `type` of folder and `files.sas` inside must be in the _low_ case letters.

If order of loading is important, the sequential number
can be used to order multiple types in the way you wish.

If folder name starts with `!` (e.g., `!ignore_me`) or *type* of the folder is "unknown" (e.g., not supported one)
the content of such folder is ignored during package generation process.

The "tree structure" of the folder could be for example as follows:

All files have to have `.sas` extension. Other files are ignored.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
 <packageName>
  ..
   |
   +-000_libname [one file one libname]
   |           |
   |           +-abc.sas [a file with a code creating libname ABC]
   |
   +-001_macro [one file one macro]
   |         |
   |         +-hij.sas [a file with a code creating macro HIJ]
   |         |
   |         +-klm.sas [a file with a code creating macro KLM]
   |
   +-002_function [one file one function,
   |            |  option OUTLIB= should be: work.&packageName.fcmp.package
   |            |  option INLIB=  should be: work.&packageName.fcmp
   |            |  (both literally with macrovariable name and "fcmp" sufix)]
   |            |
   |            +-efg.sas [a file with a code creating function EFG, _with_ "Proc FCMP" header]
   |
   +-003_functions [mind the S at the end!, one file one function,
   |             |  only plain code of the function, without "Proc FCMP" header]
   |             |
   |             +-ijk.sas [a file with a code creating function EFG, _without_ "Proc FCMP" header]
   |
   +-004_format [one file one format,
   |          |  option LIB= should be: work.&packageName.format
   |          |  (literally with macrovariable name and "format" suffix)]
   |          |
   |          +-efg.sas [a file with a code creating format EFG and informat EFG]
   |
   +-005_data [one file one dataset]
   |        |
   |        +-abc.efg.sas [a file with a code creating dataset EFG in library ABC]
   |
   +-006_exec [so called "free code", content of the files will be printed
   |        |  to the log before execution]
   |        |
   |        +-<no file, in this case folder may be skipped>
   |
   +-007_format [if your codes depend each other you can order them in folders,
   |          |  e.g. code from 003_... will be executed before 006_...]
   |          |
   |          +-abc.sas [a file with a code creating format ABC,
   |                     used in the definition of the format EFG]
   +-008_function
   |            |
   |            +-<no file, in this case folder may be skipped>
   |
   |
   +-009_lazydata [one file one dataset]
   |            |
   |            +-klm.sas [a file with a code creating dataset klm in library work
   |                       it will be created only if user request it by using:
   |                       %loadPackage(packagename, lazyData=klm)
   |                       multiple elements separated by space are allowed
   |                       an asterisk("*") means "load all data"]
   |
   +-010_imlmodule [one file one IML module,
   |             |  only plain code of the module, without "Proc IML" header]
   |             |
   |             +-abc.sas [a file with a code creating IML module ABC, _without_ "Proc IML" header]
   |
   +-011_casludf [one file one CAS-L user defined function,
   |             |  only plain code of the function, without "Proc CAS" header]
   |             |
   |             +-abc.sas [a file with a code creating CAS-L user defined function ABC, _without_ "Proc CAS" header]
   |
   +-012_kmfsnip [one file one KMF-abbreviation snippet,
   |             |  code snipped proper tagging]
   |             |
   |             +-abc.sas [a file with a KMF-abbreviation snippet ABC, _with_ proper tagging, snippets names are in low-case]
   |
   +-<sequential number>_<type [in lower case]>
   |
   +-0nn_clean [if you need to clean something up after exec file execution,
   |         |  content of the files will be printed to the log before execution]
   |         |
   |         +-<no file, in this case folder may be skipped>
   |
   +-...
   |
   +-998_addcnt [additional content for the package, can be only one!, content of this
   |          |  directory is copied "as is"]
   |          |
   |          +-arbitrary_file1 [an arbitrary file ]
   |          |
   |          +-subdirectory_with_files [an arbitrary directory with some files inside]
   |          |
   |          +-...
   |
   +-999_test [tests executed during package generation, XCMD options must be turned-on]
   |        |
   |        +-test1.sas [a file with a code for test1]
   |        |
   |        +-test2.sas [a file with a code for test2]
   |
   +-...
   ...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--------------------------------------------------------------------------------------------

##      This is short help information for the `extendPackagesFileref` macro <a name="extendpackagesfileref"></a>
-----------------------------------------------------------------------------------------

 Macro to list directories pointed by 'packages' fileref, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and embedded inside the zip.

 The `%extendPackagesFileref()` macro lists directories pointed by
 the packages fileref. It allows to add new directories to packages folder list.

### Parameters:

 1. `packages`      *Optional.* A valid fileref name, when empty the "packages" is used
 When used as: `%extendPackagesFileref(HELP)` it displays this help information.

------------------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.

 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example ###################################################################

   Enabling the SAS Package Framework
   from the local directory and adding
   new directory.

   Assume that the `SPFinit.sas` file
   is located in one of "C:/SAS_PK1" or "C:/SAS_PK2" folders.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
filename packages ("C:/SAS_PK1" "C:/SAS_PK2"); %* setup a directory for packages;
%include packages(SPFinit.sas);                %* enable the framework;

filename packages ("D:/NEW_DIR" %extendPackagesFileref()); %* add new directory;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----------------------------------------------------------------------------------------

##      This is short help information for the `loadPackageAddCnt` macro <a name="loadpackageaddcnt"></a>
-------------------------------------------------------------------------------

 Macro to load *additional content* for a SAS package, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and included by
 a single `load.sas` file (also embedded inside the zip).

 The `%loadPackageAddCnt()` macro loads additional content
 for a package (of course only if one is provided).

-------------------------------------------------------------------------------
### Parameters:

 1. `packageName`      *Required.* Name of a package, e.g. myPackage,
                       Required and not null, default use case:
                        `%loadPackageAddCnt(myPackage)`.
                       If empty displays this help information.

 - `path=`             *Optional.* Location of a package. By default it
                       looks for location of the **packages** fileref, i.e.
                        `%sysfunc(pathname(packages))`

 - `target=`           *Optional.* Location where the directory with
                       additional content will be generated,
                       name of the directory created is set to
                       `<packagename>_AdditionalContent`, the default
                       location is `%sysfunc(pathname(WORK))`

 - `source2=`          *Optional.* Option to print out details about
                       what is loaded, null by default.

 - `requiredVersion=`  *Optional.* Option to test if the loaded
                       package is provided in required version,
                       default value: `.`


-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.

 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

-------------------------------------------------------------------------------

 By *default* additional content is not deployed automatically e.g.,
 from security point of view, or production job doesn't need it to run, etc.
 But if there is a need for it there are three ways to get it:

 - The first one ("by-the-book"), and also the recommended one. The additional
   content is extracted during the automatic installation process using the
   `\%installPackage()` macro. For this to work the `loadAddCnt=` parameter
   has to be set to `1`. The additional content is extracted to the
   `<packageName>_AdditionalContent` directory into the same location where
   the package is installed i.e., inside `packages` fileref location.
 - The second one ("by-the-work"), when the additional content is extracted
   during the loading process with the `\%loadPackage()` macro. For this to
   work also the `loadAddCnt=` parameter has to be set to `1`. The additional
   content is extracted to the `<packageName>_AdditionalContent` directory
   inside the `Work` library location.
 - The third one ("by-the-user"), when the additional content is extracted
   with dedicated `%loadPackageAddCnt()` macro. By default the additional
   content is extracted to the `<packageName>_AdditionalContent` directory
   inside the `Work` library location too, but it can be altered by changing
   the `target=` parameter, which indicates the location.

 If done "by-the-book", or "by-the-user" with `target=` parameter, the
 additional content is not automatically deleted when SAS session ends,
 in this case the "additionals" have to be deleted manually by the User.


### Example 1 ##################################################################

   Enabling the SAS Package Framework
   from the local directory and installing & loading additional content
   for the SQLinDS package.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
%include packages(SPFinit.sas);      %* enable the framework;

%installPackage(SQLinDS)  %* install the package from the Internet;
%loadPackageAddCnt(SQLinDS) %* load additional content for the package;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----------------------------------------------------------------------------------------



##      This is short help information for the `requestPackage` macro <a name="requestpackage"></a>

--------------------------------------------------------------------------------------------

 Macro to request (install and load) SAS packages, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and embedded inside the zip.

 The `%requestPackage()` macro installs and loads the package zip
 in the packages folder. The process takes care of installing or loading
 dependencies too.

 In case the packages fileref is a multi-directory one the first directory
 will be selected as a destination.

--------------------------------------------------------------------------------------------

### Parameters:

 1. `packageName `  Name of a package _without_ the zip extension, e.g., myPackage1.
                    Required and not null, default use case:
                    `%requestPackage(myPackage1)`.
                    If empty displays this help information.

  **Installation options:**

 - `requiredVersion=`  *Optional.* Indicates which (at least) package version we want
                       to be requested. Empty value by default means: "load currently
                       installed version or install and load the latest available one."
                       When loaded (installed) package version is greater or equal
                       than requested, lower requested version is not loaded (installed).

 - `sourcePath=`   Location of the package, e.g. "www.some.web.page/"
                   Mind the "/" at the end of the path!
                   Current default location for packages is:
                   `https://github.com/SASPAC/`
                   Current default location for the framework is:
                   `https://raw.githubusercontent.com/yabwon/SAS_PACKAGES/main/SPF/`

 - `mirror=`       Indicates which web location for packages installation is used.
                   Value `0` or `SASPAC` indicates:
                    `https://github.com/SASPAC/`
                   Value `1` indicates:
                    `https://raw.githubusercontent.com/yabwon/SAS_PACKAGES/main`
                   Value `2` indicates:
                    `https://pages.mini.pw.edu.pl/~jablonskib/SASpublic/SAS_PACKAGES`
                   Value `3` or `PharmaForest` indicates:
                    `https://github.com/PharmaForest/`
                   Default value is `0`.

 - `replace=`      When set to `1` and a package file exists, it forces the package
                   file replacement by the new downloaded file.
                   It is a binary indicator ('0' or '1'). Default value is `1`.

 - `backup=`       When set to `1` and a package file exists, it creates a backup copy
                   of the package file. The backup copy is created with a suffix of the
                   following format: `_BCKP_yyyymmddJJMMSS`.
                   If `replace=0` then `backup` is set to `0`.
                   It is a binary indicator ('0' or '1'). Default value is `0`.

 - `URLuser=`      A user name for the password protected URLs, no quotes needed.

 - `URLpass=`      A password for the password protected URLs, no quotes needed.

 - `URLoptions=`   Options for the `sourcePath` URLs filename. Consult the SAS
                   documentation for the further details.

 - `loadAddCnt=`   *Optional.* A package zip may contain additional
                   content. The option indicates if it should be loaded
                   Default value of zero (`0`) means "No", one (`1`)
                   means "Yes". Content is extracted into the **packages** fileref
                   directory in `<packageName>_AdditionalContent` folder.
                   For other locations use `%loadPackageAddCnt()` macro.

 - `instDoc=`      *Optional.* A package may be provided with a markdown file
                   containing combined documentation of the package. The option
                   indicates if the `.md` file should be also downloaded.
                   Default value of zero (`0`) means "No", one (`1`) means "Yes".

  - `github=`      *Optional.* A name of a user or an organization in GitHub.
                   Allows an easy set of the search path for packages available on GitHub:
                    `https://github.com/<github>/<githubRepo>/raw/.../`
                   All characters except `[A-z0-9_.-]` are compressed.

  - `githubRepo=`  *Optional.* A name of a repository in GitHub.
                   Allows an easy set of the search path for packages available on GitHub:
                    `https://github.com/<github>/<githubRepo>/raw/.../`
                   By default lowercase name of installed package is used.

  - `githubToken=` *Optional.* A fine-grained personal access token for GitHub.
                   When the value is non-missing it triggers GitHub API access to
                   private repositories. Of course the token used has to be configured
                   properly for the access.
                   Read GitHub documentation to learn how to create and setup your token:
                   `https://docs.github.com/en/authentication/
                     keeping-your-account-and-data-secure/
                      managing-your-personal-access-tokens
                       #creating-a-fine-grained-personal-access-token`
                   (lines break added for easier reading)
                   Public repositories do not need authentication.
                   [NOTE!] This feature is experimental in this release.

  **Loading options:**

 - `loadPackage=`  *Optional.* Indicates if requested package should be loaded too
                   or only installed. Dependencies are only installed.
                   Default value of zero (`0`) means "No", one (`1`) means "Yes".

 - `force=`        *Optional.* Indicates if requested package should be reloaded
                   even if it was already loaded to the session.
                   Default value of zero (`0`) means "No", one (`1`) means "Yes".

 - `ignoreDepVer=` *Optional.* Indicates if packages versions in dependencies list
                   should be ignored and the latest available version be used.
                   Default value of zero (`0`) means "No", one (`1`) means "Yes".

--------------------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.
 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example ################################################################################

   Enabling the SAS Package Framework
   from the local directory and requesting (installing & loading)
   the bpUTiL package from the Internet.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
 filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
 %include packages(SPFinit.sas);      %* enable the framework;

 %requestPackage(bpUTiL)   %* install and load the package from the Internet;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
### Example #################################################################################

   Enabling the SAS Package Framework
   from the local directory and installing & loading
   a package with a particular version from the Internet.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
 filename packages "C:/SAS_PACKAGES";
 %include packages(SPFinit.sas);

 %requestPackage(LibnameZIP, requiredVersion=0.1.0)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-----------------------------------------------------------------------------------------


##     This is short help information for the `splitCodeForPackage` macro <a name="splitcodeforpackage"></a>
-------------------------------------------------------------------------------

 Utility macro to *split* single file with SAS package code into multiple
 files with separate snippets, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and included by
 a single `load.sas` file (also embedded inside the zip).

 The `%splitCodeForPackage()` macro takes a file with SAS code
 snippets surrounded by `/*##$##-code-block-start-##$## <tag spec> */` and
 `/*##$##-code-block-end-##$## <tag spec> */` tags and split that file into
 multiple files and directories according to a tag specification.

 The `<tag spec>` is a list of pairs of the form: `type(object)` that
 indicates how the file should be split. See example 1 below for details.

-------------------------------------------------------------------------------
### Parameters:

 1. `codeFile=`        *Required.* Name of a file containing code
                        that will be split. Required and not null.
                        If empty displays this help information.

 - `packagePath=`      *Required.* Location for package files after
                        splitting into separate files and directories.
                        If missing or not exist then `WORK` is used.

 - `debug=`            *Optional.* Turns on code printing for debugging.

 - `nobs=`             *Optional.* Technical parameter with value `0`.
                        Do not change.

-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.

 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example 1 ##################################################################

   Assume that the `myPackageCode.sas` file
   is located in the `C:/lazy/` folder and
   contain the following code and tags:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas

/*##$##-code-block-start-##$## 01_macro(abc) */
%macro abc();
  %put I am "abc".;
%mend abc;
/*##$##-code-block-end-##$## 01_macro(abc) */

/*##$##-code-block-start-##$## 01_macro(efg) */
%macro efg();
  %put I am "efg".;
%mend efg;
/*##$##-code-block-end-##$## 01_macro(efg) */

proc FCMP outlib=work.f.p;
/*##$##-code-block-start-##$## 02_functions(xyz) */
function xyz(n);
  return(n**2 + n + 1)
endfunc;
/*##$##-code-block-end-##$## 02_functions(xyz) */
quit;

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 and we want results in `C:/split/` folder, we run the following:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
%include packages(SPFinit.sas);      %* enable the framework;

%splitCodeForPackage(
   codeFile=C:/lazy/myPackageCode.sas
  ,packagePath=C:/split/ )
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

##      This is short help information for the `relocatePackage` macro <a name="relocatepackage"></a>
-------------------------------------------------------------------------------

 Macro to *locally copy or move* (relocate) SAS packages, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and included by
 a single `load.sas` file (also embedded inside the zip).

 The `%relocatePackage()` is a utility macro for local copying or moving
 SAS packages. The macro transfers packages located in the `PACKAGES`
 fileref to a selected directory (`DISK` device), folderpath (`FILESRVC`
 device), or a zip file (`ZIP` device).

 The macro allows for a bidirectional transfer of packages, i.e., from the
 `PACKAGES` fileref to the selected *target*, or from the selected *source*
 to the `PACKAGES` fileref.

-------------------------------------------------------------------------------
### Parameters:

 1. `packageName`      *Required.* Name of a package, e.g. myPackage.
                       A space-separated(!) list of packages to transfer is
                       also accepted. If empty displays this help information.

 - `source=`           *Required/Optional.* Source location for packages.
                       When used, indicates a directory (`DISK` device),
                       a folderpath (`FILESRVC` device), or a zip file (`ZIP`
                       device) *from* where packages will be copied.
                       In this case `PACKAGES` fileref is target location.
                       Cannot be used together with `target=` parameter.

 - `target=`           *Required/Optional.* Target location for packages.
                       When used, indicates a directory (`DISK` device),
                       a folderpath (`FILESRVC` device), or a zip file (`ZIP`
                       device) *to* where packages will be copied.
                       In this case `PACKAGES` fileref is source location.
                       Cannot be used together with `source=` parameter.

 - `sDevice=`          *Required/Optional.* When `source=` is used this
                       parameter provides which type of device to be use.
                       Default value is `DISK`, values `ZIP` and `FILESRVC`
                       are allowed. For `FILESRVC` the `folderpath=` is used.

 - `tDevice=`          *Required/Optional.* When `target=` is used this
                       parameter provides which type of device to be use.
                       Default value is `DISK`, values `ZIP` and `FILESRVC`
                       are allowed. For `FILESRVC` the `folderpath=` is used.

 - `checksum=`         *Optional.* Indicates if packages should be copied only
                       if the source (from file) checksum is different than
                       the target (to file). Default value is 0 (always copy).

 - `move=`             *Optional.* Indicates if packages should be moved from
                       source to target, default value is `0`,
                       when set to `1`: after *successful* copying packages
                       in the source are *deleted*. Use carefully!

 - `debug=`            *Optional.* Indicates if debug notes should be printed,
                       default value is `0`, when set to `1`: debug info
                       is printed.

 - `try=`              *Optional.* Number of tries when copy is unsuccessful,
                       default value is `3`, allowed values are integers
                       from 1 to 9. Time between tries is quarter of a second.

-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.
 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example 1 ##################################################################

   Enabling the SAS Package Framework from the local
   directory, copying SQLinDS package from Viya Files
   service, and loading the package to the SAS session.

   Assume that the `SPFinit.sas` file is located in the "/home/user/PCKG"
   directory and Viya Files service location is "/files/packages/"

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
 filename packages "/home/user/PCKG"; %* setup a directory for packages;
 %include packages(SPFinit.sas);      %* enable the framework;

 %relocatePackage(SQLinDS  %* copy the package from Viya Files service;
                 ,source=/files/packages/
                 ,sDevice=FILESRVC)
 %loadPackage(SQLinDS)   %* load the package content into the SAS session;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

### Example 2 ##################################################################

   Enabling the SAS Package Framework from the local directory
   and creating a "bundle" file by moving 3 packages: the BasePlus,
   the SQLinDS, and the MacroArray package into the target file.

   Assume that the `SPFinit.sas` file
   is located in the "C:/SAS_PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
 filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
 %include packages(SPFinit.sas);      %* enable the framework;

 %relocatePackage(BasePlus SQLinDS MacroArray %* create a bundle of packages;
                 ,target=D:/archive/bundle_2025_12_15.zip
                 ,tDevice=ZIP, move=1)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

##       This is short help information for the `isPackagesFilerefOK` macro <a name="ispackagesfilerefok"></a>
-----------------------------------------------------------------------------------------

 Macro to check if the `packages` fileref is "correct", version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and embedded inside the zip.

 The `%isPackagesFilerefOK()` macro checks if the `packages` fileref
 is correct, i.e. all listed directories exist, are accessible (can be open), and
 are assigned with the DISK device.

 The Macro works as a macro function. It returns `1` when everything is OK, and
 it returns `0` if at least one issue exists.

### Parameters:

 1. `vERRb`  - *Optional* Indicates if the macro should return value AND be verbose
               (e.g., print errors and notes) or just return value.
               `1` means "verbose", `0` means "quiet".

 When used as: `%isPackagesFilerefOK(HELP)` it displays this help information.

-----------------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.
 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example #############################################################################

   Enabling the SAS Package Framework from the local
   directory, expanding PACKAGES fileref, and checking
   if the new one is still correct for installing new package.

   Assume that the `SPFinit.sas` file
   is located in the "/sas/PACKAGES/" directory.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
 filename packages "/sas/PACKAGES";                        %* set packages filename;
 %include packages(SPFinit.sas);                           %* enable the framework;

 filename packages ("~/myPCKGs" %extendPackagesFileref()); %* add new directory;

 %if %IsPackagesFilerefOK() %then                          %* check fileref;
   %do; %InstallPackage(SQLinDS) %end;                     %* install SQLinDS;

 %listPackages()                                           %* list packages;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

##   This is short help information for the `SasPackagesFrameworkNotes` macro <a name="saspackagesframeworknotes"></a>
-------------------------------------------------------------------------------

 Macro prints help notes for SAS Packages Framework macros, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and included by
 a single `load.sas` file (also embedded inside the zip).

 The `%SasPackagesFrameworkNotes()` macro provides help notes about
 components of the SAS Packages Framework.

-------------------------------------------------------------------------------
### Parameters:

1. `SPFmacroName`     *Required.* Names of a SPF components.
                      Names should be space separated, asterisk(*) is
                      allowed too. In such case ALL help notes are printed
                      If equal `HELP` displays this help information.
                      If empty displays list of SPF macros.
                      If equal `VERSION`, `VER`, or just `V` returns (in
                      a function stule) version number, but since the macro
                      is compiled as "secure" it **cannot** be called through
                      the `%put` statement. Direct assignment to a
                      macrovariable has to be executed, e.g.,
                      `%let version = %SasPackagesFrameworkNotes(V);`


-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.
 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example 1 ##################################################################

   Run the following code to print all SPF help notes:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
 %SasPackagesFrameworkNotes(*)       %* print ALL notes;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

### Example 2 ##################################################################

   Run the following code to list all SPF macros:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
 %SasPackagesFrameworkNotes()        %* list all macro names;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

### Example 3 ##################################################################

   Run the following code to print help notes:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
 %SasPackagesFrameworkNotes(generatePackage helpPackage)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


##      This is short help information for the `bundlePackages` macro <a name="bundlepackages"></a>
-------------------------------------------------------------------------------

 Macro to *create bundles* of SAS packages, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and included by
 a single `load.sas` file (also embedded inside the zip).

 The `%bundlePackages()` macro allows to bundle a bunch of SAS packages
 into a single file (a SAS packages bundle), just like a snapshot.

-------------------------------------------------------------------------------
### Parameters:

 1. `bundleName`       *Required.* Name of a bundle, e.g. myBundle,
                       if the value is empty a default name is generated:
                       `saspackagesbundle_createdYYYYMMDDtHHMMSS`, an
                       extension `.bundle.zip` is automatically added.
                       For value `HELP` this help information is displayed.

 - `path=`             *Required.* Location of the bundle. Must be a valid
                       directory. Takes precedence over `pathRef` parameter.
                       Either `path=` or `pathRef=` must be non-empty.

 - `pathRef=`          *Optional.* Fileref to location of the bundle.
                       Either `path=` or `pathRef=` must be non-empty.

 - `packagesList=`     *Optional.* A space-separated list of packages
                       to bundle. If the value is empty all available
                       packages are used.

 - `packagesPath=`     *Optional.* Location of packages for the bundle.
                       Takes precedence over `packagesRef` parameter.
                       When non-empty, must be a valid directory.

 - `packagesRef=`      *Optional.* Fileref to location of packages for the
                       bundle. Default value is `packages`.

 - `ods=`              *Optional.* V7 style name of SAS data set for report.

-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.
 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

### Example 1 ##################################################################

   Enabling the SAS Package Framework
   from the local directory and create a bundle of
   selected packages in user home directory.

   Assume that the `SPFinit.sas` file
   is located in the "/sas/PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
 filename packages "/sas/PACKAGES/";  %* setup a directory for packages;
 %include packages(SPFinit.sas);      %* enable the framework;

 %bundlePackages(myLittleBundle
                ,path=/home/user/bundles
                ,packagesList=basePlus SQLinDS macroarray
                ,packagesRef=PACKAGES)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


##     This is short help information for the `unbundlePackages` macro <a name="unbundlepackages"></a>
-------------------------------------------------------------------------------

 Macro to *extract* SAS packages from a bundle, version `20260727`

 A SAS package is a zip file containing a group
 of SAS codes (macros, functions, data steps generating
 data, etc.) wrapped up together and included by
 a single `load.sas` file (also embedded inside the zip).

 The `%unbundlePackages()` macro allows to extract SAS packages from
 a bundle into a single directory.

-------------------------------------------------------------------------------
### Parameters:

 1. `bundleName`       *Required.* Name of a bundle, e.g. myBundle,
                       extension `.bundle.zip` is automatically added.
                       For empty value or `HELP` this help information
                       is displayed.

 - `path=`             *Required.* Location of the bundle. Must be a valid
                       directory. Takes precedence over `pathRef` parameter.
                       Either `path=` or `pathRef=` must be non-empty.

 - `pathRef=`          *Optional.* Fileref to location of the bundle.
                       Either `path=` or `pathRef=` must be non-empty.

 - `packagesPath=`     *Optional.* Location for packages extracted from
                       the bundle. Takes precedence over `packagesRef`.
                       When non-empty, must be a valid directory.

 - `packagesRef=`      *Optional.* Fileref to location where packages will
                       be extracted. Default value is `packages`.

 - `ods=`              *Optional.* V7 style name of SAS data set for report.

 - `verify=`           *Optional.* Indicates if verification code should
                       be executed after bundle extraction.
                       Value `1` means yes, Value `0` (default) means no.

 - `reportOnly=`       *Optional.* Indicates if packages unbundling should
                       be suspended and only a report with bundle content
                       be produced and printed.
                       Value `1` means yes, Value `0` (default) means no.

 - `quiet=`           *Optional.* Indicates if printout of the summary report
                       should be suspended.
                       Value `1` means yes, Value `0` (default) means no.

-------------------------------------------------------------------------------

 Visit: `https://github.com/yabwon/SAS_PACKAGES/tree/main/SPF/Documentation`
 to learn more.
 Tutorials available at: `https://github.com/yabwon/HoW-SASPackages`

## Example 1 ##################################################################

   Enabling the SAS Package Framework
   from the local directory and extract a bundle of
   packages from user home directory to packages.

   Assume that the `SPFinit.sas` file
   is located in the "/sas/PACKAGES/" folder.

   Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
 filename packages "/sas/PACKAGES/";  %* setup a directory for packages;
 %include packages(SPFinit.sas);      %* enable the framework;

 %unbundlePackages(myLittleBundle
                  ,path=/home/user/bundles
                  ,verify=1
                  ,packagesRef=PACKAGES)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
## Some more examples <a name="some-more-examples"></a> #############################################################

### Example 1. ###################################################################
Enabling the SAS Package Framework
and loading the SQLinDS package from the local directory.

Assume that the `SPFinit.sas` file and the SQLinDS
package (sqlinds.zip file) are located in
the "C:/SAS_PACKAGES/" folder.

Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
  filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
  %include packages(SPFinit.sas);      %* enable the framework;

  %helpPackage(SQLinDS)                %* get help about the package;
  %loadPackage(SQLinDS)                %* load the package content into the SAS session;
  %unloadPackage(SQLinDS)              %* unload the package content from the SAS session;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

### Example 2. ###################################################################
Enabling the SAS Package Framework
from the local directory and installing & loading
the SQLinDS package from the Internet.

Assume that the `SPFinit.sas` file
is located in the "C:/SAS_PACKAGES/" folder.

Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
  filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
  %include packages(SPFinit.sas);      %* enable the framework;

  %installPackage(SQLinDS)             %* install the package from the Internet;
  %helpPackage(SQLinDS)                %* get help about the package;
  %loadPackage(SQLinDS)                %* load the package content into the SAS session;
  %unloadPackage(SQLinDS)              %* unload the package content from the SAS session;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

### Example 3. ###################################################################
Enabling the SAS Package Framework
and installing & loading the SQLinDS package
from the Internet.

Run the following code in your SAS session:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
  filename packages "%sysfunc(pathname(work))"; %* setup WORK as a temporary directory for packages;

  filename spfinit url "https://raw.githubusercontent.com/yabwon/SAS_PACKAGES/main/SPFinit.sas";
  %include spfinit;                    %* enable the framework;

  %installPackage(SQLinDS)             %* install the package from the Internet;
  %helpPackage(SQLinDS)                %* get help about the package;
  %loadPackage(SQLinDS)                %* load the package content into the SAS session;
  %unloadPackage(SQLinDS)              %* unload the package content from the SAS session;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

### Example 4. ###################################################################
Assume that the `SPFinit.sas` file and the SQLinDS package (`sqlinds.zip` file)
are located in the "C:/SAS_PACKAGES/" folder.

In case when user SAS session does not support ZIP fileref
the following solution could be used.

Unzip the `packagename.zip` content into the `packagename.disk` folder
and run macros with the following options:                     ;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
  %loadPackage(packageName,zip=disk,options=)
  %helpPackage(packageName,,zip=disk,options=) %* mind the double comma!! ;
  %unloadPackage(packageName,zip=disk,options=)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

### Example 5. ###################################################################
Enabling the SAS Package Framework from the local directory
and installing the SQLinDS package from the Internet.

Assume that the `SPFinit.sas` file is located in
the "C:/SAS_PACKAGES/" folder.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~sas
  filename packages "C:/SAS_PACKAGES"; %* setup a directory for packages;
  %include packages(SPFinit.sas);      %* enable the framework;

  %installPackage(SQLinDS);            %* install package;
  %installPackage(SQLinDS);            %* overwrite already installed package;
  %installPackage(SQLinDS,replace=0);  %* prevent overwrite installed package;

  %installPackage(NotExistingPackage); %* handling with not existing package;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-------------------------------------------------------------------------------

