RE: MCH0602 Boundary alignment error while calling *srvpgm from CLLE

I guess this is a me too post, but you managed to hit two of my pet
peeves in one message.  CL is a great scripting language for processes
that go from point A to point B without any side trips.  (Maybe the v5r3
CL is better.)  I shy away from doing anything in CL that involves error
checking, looping, or branching.  I really prefer to have separate field
names in program and display file. Maybe I use debug too much.  People
have called me lazy and wasteful, but I've spent enough time with cats
to know that that's really praise.  <g> 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Monday, February 14, 2005 3:10 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: MCH0602 Boundary alignment error while calling *srvpgm from
CLLE

Don't use CL for DSPF. My opinion only but using CL for DSPF always ends
up being a nightmare. When I had to do things like this, I simply
created a standard RPG program to do things like get a parameter. Then I
would just insert the fields I needed and away I went.

The other issue is that I always use unique named fields in a display
file and I always issue a move into those fields. Using the same names
for program fields as display file fields is just a great way to create
a program that is a pain to maintain. We ended up with I_xxxx, O_xxxx,
B_xxxx for field names I for input, O for output and B for both fields.

I believe strongly in explicit moves, not implicit. It takes a bit more
effort but it sure saves time in the long run.

Again my opinions only.


*****************************
NOTICE:
All e-mail sent to or from this e-mail address will be received or otherwise 
recorded by
The Sharper Image corporate e-mail system and is subject to archival, 
monitoring,
and review by and/or disclosure to Sharper Image security and other management.
This message is intended only for the use of the addressee and may contain 
information
that is privileged and confidential.

The contents of this message may contain personal views which are not the views 
of The Sharper Image.
If you are not the intended recipient, dissemination of this communication is 
prohibited.
*****************************