john e malmberg ho0ebgqslnet test libi18nlangtagst80_all_envt failing vms tests inadvertently setting environment variables persist beyond run mainly shows run tests outside test harness test harness isolates tests process case environment variables c c one issue seems showing setting envfoo empty string apparently causing problems vms resulting logical name showing containing empty string showing containing one nonprinting characters using perl read logical name apparently getting garbage string showing 4 characters record string seem consistently dcl showing logical name resolving simply dcl replacing nonprinting character looks like todo issues vms 1 find happening envfoo fix needed 2 try identify magic environment variables c library dynamically creates reference 3 update pod env handling instructions save restore env variables vms including list magic ones restored 3 search fix mission tests modify environment variables clean john ho0ebgqslnet personal opinion thu 07 aug 2008 193625 0600 env issues vms