Re: [netrexx-pipelines] Migrate OS/2 pipelines to NetRexx Pipes

[Rony G. F. <Ron...@wu...>]

Hi Mike,

On 6/7/2022 10:40 AM, hp...@we... wrote:
... cut ...
> The output of p4varload_1 looks nice:
>> C:\prgm\NetRexx\examples\VilMA>ripe "(sep !) < vilma.ini!p4varload_1!term
>> VIMDR = C:\PRGM\REXX\VILMA\
>> CTLDR = C:\PRGM\HP-EMULATORS\V41\
>> VILDR = C:\PRGM\HP-EMULATORS\VIRTIL\
>> DELTA = 3
>> ITLVL = STD.VILMA
>> CTRLS = VILMA.CONTROLLERS
>> TPCPT = TYPICAL.CAPTION
>> DIAPOS = 321 23
>
> Now we "only" need to interpret this in ooRexx.

... cut ...

If you have BSF4ooRexx installed 
(https://sourceforge.net/projects/bsf4oorexx/files/GA/BSF4ooRexx-641.20220131-GA/), then add 
"::requires BSF.CLS" (loads BSF4ooRexx) at the end of your program. Afterwards you have access to 
the external Rexx function BsfContextVariables() which allows one to read, set or drop Rexx 
variables from/in the current variable pool.

Here the synopsis:

    BsfContextVariables( "G[et]"  [, name] )
    ... return value of a Rexx variable with given name, if omitted, returns a directory of all
    current Rexx variables in the current context

    BSFContextVariables("S[et]", { name, newValue | directory | stringTable} )
    ... either sets a single Rexx variable name to newValue, or takes all directory or stringtable
    pairs of INDEX (variable name ) and ITEM (value to be set to) and processes them accordingly,
    returns .true

    BSFContextVariables("D[rop]", name)
    ... drops the Rexx variable name from the current context, returns .true

HTH,

---rony