Eric Covener covener

Go to the publish dir and find logs.zip (different then logs/ directory) and download it to your laptop.
Extract the logs.zip
The logs are in EBCDIC so you can't immediately cat/edit/grep through them. You can grab e2a binaries/source from https://github.ibm.com/WASL3/ecurep-btrace/tree/master/tools/e2a to use on your VM or laptop.
Start by checking makezos.5.log and look for compile or link errors (WARNINGS probably n/a)

For example: $ e2a makezos.5.log|grep plugins.http

boss_c -Wc,EXPO,NOANS,CSECT,NOSOURCE,NOSHOWINC,NOEXP,NODIGRAPH,NOINFO,LIST(ZNATV/ws/code/plugins.http/src/common/ws_server.clst),NOXREF,LANGLVL(EXTENDED),NOTEST(NOHOOK),FLOAT(IEEE,MAF),HGPR,ARCH(5),TUNE(8),TARGET(ZOSV1R12),XPLINK(STOREARGS),dll,INLINE(AUTO,1000,8000),-Wc,dll,GONUM,,SERVICE(20240513150715508.00(ws_server)), -D_XOPEN_SOURCE_EXTENDED -D_XOPEN_SOURCE=500 -D_OPEN_SYS -D_OPEN_THREADS -D_POSIX_SOURCE -D_ISOC99_SOURCE -2 -V -c -oZNATV/ws/code/plugins.http/src/common/ws_server.o -Wc,dll,NOXPLINK -DAIX

newRoutingInfo is only ever assigned to in the child process, it is used for the initial routing info and all subsequent ones.

    case MT_S2C_BEGIN_ROUTING_INFO:
        TR_DEBUG(ctx,rec,"clientProcess: received begin routing info message\n");
        odrRoutingInfoRelease(odr->newRoutingInfo);
        odr->newRoutingInfo = odrRoutingInfoCreate(odr);
        break;

	static void getnamas(server_rec main_server, apr_pool_t pconf)
	{
	char buf[256], buf1[10], buf2[10], buf3[10], buf4[10];
	struct mypsa
	{
	unsigned char filler1[540];
	void *__ptr32 tcb;
	unsigned char filler2[4];
	void *__ptr32 ascb;
	};

	#!/bin/sh

	# pstack workalike

	if [ $# -lt 1 ]; then
	echo "$0 pid [gdb args]"
	echo "$0 core executable-path [gdb args]"
	exit 1
	fi

	/* REXX */
	'cgiutils -status 200 -ct text/html'
	say '<HTML>'
	say '<BODY>'
	say '<H1>Processing forms with CGI scripts</H1>'
	say '<P>'
	say 'This is an example of a CGI script which uses the <CODE>'
	say 'cgiutils</CODE> and <CODE>cgiparse</CODE>'
	say 'functions to create a valid HTTP header and parse forms data,'
	say 'respectively.'