I found an example where the environment variables are specified
directly in the
ENVAR parm and not in a separate file; maybe this could work for your
use case too ...
//CEEOPTS DD *
ALL31(ON),
STACK(3M,1M,ANY,KEEP),
HEAP(4K,4K,ANY,KEEP),
STORAGE(NONE,NONE,NONE,0),
RPTSTG(ON),RPTOPTS(ON),
ENVAR("_CEE_HEAP_MANAGER=CEL4MCHK",
"_CEE_MEMCHECK_TRACE=ON",
"_CEE_MEMTRACE_DEPTH=32",
"_CEE_MEMCHECK_DEPTH=32",
"_CEE_MEMCHECK_OVERLAY=OFF",
"_CEE_MEMCHECK_OVERLAYLEN=80")
//*
these are CEE related environment variables which control some
attributes of LE itself,
but I don't think that that makes a difference ...
Kind regards
Bernd
Am 25.06.2024 um 19:11 schrieb Colin Paice:
I am writing a program using system SSL (GSK*).
If I define the environment variables in USS everything works.
If I specified the environment variables in JCL
//START1 EXEC PGM=GSKMAIN,REGION=0M,
// PARM=('ENVAR("_CEE_ENVFILE=DD:STDENV")/4000')
//STDENV DD *
GSK_TRACE_FILE=/tmp/zzztrace.file
GSK_TRACE=0xff
GSK_KEYRING_FILE=START1/TN3270
/*
environment variables like GSK_KEYRING_FILE are padded on the right with
blanks. it cannot find the keyring TN3270______.... and gives me a trace
file with blanks on the end!
I guess this is a GSK bug - it should strip trailing blanks, but I wondered
if there was a JCL solution for this?
Colin
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
