The cron scheduler was calling the cobrun executable to run a COBOL program.

That program then called a second program, using CALL “SYSTEM” where cobrun was again loaded. The second program was in a sub directory from where the initial program was running from.

The issue encountered was that the second program did not run.

Following is an example of how crontab might be set up:
 

# crontab -e
# */5 * * * * cobrun /home/test/prog1

The called program prog1 resides in /home/test.

Prog1 makes a call to the operating system
 

CALL “SYSTEM” USING COMMAND-STRING

where COMMAND-STRING contains the string:

cobrun subdir/bin/prog2

Full article: https://portal.microfocus.com/s/article/KM000017023