Parent Parent directory variable exists ?

[LuGe00]

I want to do something like this:
CRTBNDRPG PGM(&CURLIB/&NAME) SRCSTMF('&RELATIVEPATH') OPTION(*EVENTF) DBGVIEW(*SOURCE) TGTCCSID(*JOB) \n CPYFRMSTMF FROMSTMF('&FULLPATH') TOMBR('/QSYS.LIB/WWSSRC.LIB/&PARENT.FILE/&NAME.MBR') MBROPT(*REPLACE) CVTDTA(*AUTO) DBFCCSID(273)

And what is missing for me is a variable which would hold WWSSRC, which is in our git project hierarchy present like this: WWSSRC/QRPGLESRC/Programm.rpgle and QRPGLESRC can be fetched with &PARENT but WWSSRC is not possible to get.

This is the output of all variables currently available:

&RELATIVEPATH = wwssrc/qrpglesrc/program.rpgle,
&LOCALPATH = c:\Users\User\Desktop\gitrepo\wwssrc\qrpglesrc\program.rpgle,
&FULLPATH = /home/User/wwssrc/qrpglesrc/program.rpgle,
&WORKDIR= /home/User,
&FILEDIR= /home/User/wwssrc/qrpglesrc,
&PARENT =qrpglesrc,
&BASENAME =program.rpgle,
&NAME = program,
&EXT = RPGLE,
&HOME = /home/User,
&BRANCH= master

[LuGe00]

Corresponding Pull Request resolving this issue #3149

[sebjulliand]

There is no &PARENTPARENT variable because it's not a usual use case (heck, someone could even come and ask for PARENTPARENTPARENT for that matter 😉). The actions should remain general purpose only, and are not meant to be a build tool.

This is something that fits your particular use case, though. In this case, I'd suggest you add a shell script to your project that could take care of that particular need (and encapsulate the call to both commands). The Unix commands dirname, basename and xargs are available in bash and could help you get the name of that particular folder.

For example:

echo "/home/User/wwssrc/qrpglesrc" | xargs dirname | xargs basename
# prints "wwssrc" 

Having that script would also have the benefit of having that build logic be reused outside of VS Code, in CI/CD pipeline or a build tool, for example.

[LuGe00]

For people from the future:

I created a .sh script inside the IFS filesystem and executed it with parameters from local actions.json based on the answer from sebjulliand like this:

{
    "name": "Create RPGLE Program and update source member",
    "command": "QSH CMD('/QOpenSys/usr/bin/sh /home/User/buildscripts/build-ibmi.sh ''rpgle-pgm'' ''&FULLPATH'' ''&RELATIVEPATH'' ''&PARENT'' ''&NAME'' ''&CURLIB''')",
    "deployFirst": true,
    "environment": "ile",
    "extensions": [
      "RPGLE"
    ]
  },

Inside the sh script i disassembled the full path so i could get the parent of the parent

sh script header looks like this:

#!/QOpenSys/usr/bin/sh
set -eu

MODE="$1"
FULLPATH="$2"
RELATIVEPATH="$3"
PARENT="$4"
NAME="$5"
CURLIB="$6"

TOPDIR="$(basename "$(dirname "$(dirname "$FULLPATH")")")"
TOPLIB="$(printf '%s' "$TOPDIR" | tr '[:lower:]' '[:upper:]')"
SRCFILE="$(printf '%s' "$PARENT" | tr '[:lower:]' '[:upper:]')"
NAMEU="$(printf '%s' "$NAME" | tr '[:lower:]' '[:upper:]')" 

[sebjulliand]

Great job @LuGe00 , that looks good!
I edited your post to add styling on the JSON and shell parts.

Two more little advices:

• You should consider adding that script header to your Gists in Github for easy sharing: https://gist.github.com/LuGe00
• Instead of running the script using QSH, you can get the action to call it directly into the shell, by changing the environment to PASE or QShell (depending on your need). That would look like this:

{
    "name": "Create RPGLE Program and update source member",
    "command": "/home/User/buildscripts/build-ibmi.sh rpgle-pgm &FULLPATH &RELATIVEPATH &PARENT &NAME &CURLIB",
    "deployFirst": true,
    "environment": "pase",
    "extensions": [
        "RPGLE"
    ]
},

[LuGe00]

Thank you very much @sebjulliand , this wrapped it up :)

[sebjulliand]

Brilliant!