What about using initialized variables instead of literals?
Paul
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, February 20, 2013 9:16 AM
To: midrange-l@xxxxxxxxxxxx
Subject: cl compile severity level
Is there something for CL similar to on the command CRTBNDRPG GENLVL(41)?
The problem is that my source has to be on my development machine. I send only the object over to the production machine. The production machine has devices that the development machine does not. So there's too darn much validity checking going on in BRMS commands. If I try to compile a program with:
DUPMEDBRM VOL(VRT001) FROMDEV(VRTDEV) TODEV(TAPKVL01) FROMVOL(VRT001) +
FROMSYS(APPN.GDWEB) TOVOL(*MOUNTED) EXPDATE(*MEDPCY) MOVPCY(
*MEDPCY) +
MARKDUP(*MEDPCY) MARKHST(*MEDPCY) SAVMEDINF(*NONE) It bombs with BRM1430 device not found. I created both VRTDEV and
TAPKVL01 as dummy virtual tape drives. However, now it's insisting I enroll TAPKVL01 into BRMS (and probably VRTDEV also).
BRM1430 is a sev 40 message.
Message ID . . . . . . . . . : BRM1430
Message file . . . . . . . . : Q1AMSGF
Library . . . . . . . . . : QBRM
Severity . . . . . . . . . . : 40
Log problem . . . . . . . . : *NO
Default program . . . . . . : *NONE
Default library . . . . . :
Message level . . . . . . . : 05/09/09 55
Alert option . . . . . . . . : *NO
Data to be dumped . . . . . : *NONE
Default reply . . . . . . . : *NONE
CCSID . . . . . . . . . . . : 65535
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
