RE: Target release levels

On the CRT* commands, the TGTRLS is primarily used to validate that the
source code does not contain opcodes, dds keywords, commands, command
keywords etc. that are not supported on the earlier version of the os -
compilation errors will result in failure to create the object, just as if
you had coded an opcode that does not exist.

In the SAV* commands, the TGTRLS is used to ensure that the object-header
and object-type info written to the tape (or *SAVF) is valid for the target
system, i.e. new object attributes may be available at VRM(*current) that
are not available at VRM(*prv), do they are effectively stripped out.

Jeff Bull

-----Original Message-----
From: Smith, Nelson [mailto:NSmith@lincare.com]
Sent: 18 July 2002 20:31
To: MIDRANGE-L@midrange. com
Subject: Target release levels


Are there any objects other than *pgm and *srvpgm that require a
target-release-level type of parameter when the development compiler is on a
V5R1 or V5R2 machine and the target production machine is on V4R5?

Any other gotchas to watch out for?

Nelson Smith
nsmith@lincare.com
ncsmith@tampabay.rr.com



****************************************************************************
****************************************************************************
****************************************************
This message originates from Lincare Holdings Inc. It contains information
which maybe confidential or privileged and is intended only for the
individual or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use the
contents of this message.
All personal messages express views solely of the sender, which are not to
be attributed to Lincare Holdings Inc., and may not be copied or distributed
without this disclaimer.
If you received this message in error, please notify us immediately at
MailAdmin@lincare.com or (800) 284-2006.
****************************************************************************
****************************************************************************
****************************************************

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________


DISCLAIMER

Any opinions expressed in this email are those of the
individual and not necessarily the Company. This email
and any files transmitted with it, including replies and
forwarded copies (which may contain alterations)
subsequently transmitted from the Company, are
confidential and solely for the use of the intended recipient. If you are not 
the intended recipient or the
person responsible for delivering to the intended recipient,
be advised that you have received this email in error and
 that any use is strictly prohibited.

If you have received this email in error please notify the IT
manager by telephone on +44 (0)870 871 2233 or via
email to Administrator@itm-group.co.uk, including a copy
of this message. Please then delete this email and
destroy any copies of it.

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________