Re: Source code on IFS

Steve,

Ok a long list coming from a guy that spent more time on windows and linux
boxes than the IBM i.

First of all the fact that source members have char and not varchar means
a lot of space is wasted. Someone might tell me with compression or storage
internals this is a moot point though. However, if I have a source line
with ten characters and four spaces of indent, it takes 15 bytes (one extra
for the newline). In a source members thats 80 characters.

Secondly, the hard limit of a column length is really annoying. I write
some complex DDL and sometimes an 80 character hard limit is annoying. This
is from years of writing stored procedures on Microsoft SQL server, so I
tend to write complex joins, common table expressions (WITH CLAUSE) and
other things where I tend to indent a lot. I also use the long column names
in my SQL. If your used to 80 columns, its probably not something you
notice. However write tables with long columns names and add the 10
character labels after the fact, not the other way around.

Third, more text editor support. To my knowledge your choices are RDi, SEU,
and some other expensive commercial eclipse tool for editing source
members. I SEU in a pinch, and can't justify the price tag of RDi for the
occasional CL I write, or the times I have to hand edit SQL in a source
member as opposed to calling qsys2.generate_ddl(). However with stuff on
the IFS I have the following choices that I actively use:

- SEU in a pinch
- the editor built into farmanager (http://farmanager.com) via ssh
- vi (the one built into pase)
- Notepad++
- Visual Studio Code (via UNC paths)
- PHPStorm, and the other JetBrain IDEs
- Zend Studio

Eventually all those editors will have syntax highlighting for RPG. I'd put
money on it. Of course all of them are at least partially open source, so I
could write the syntax highlighting config file myself to avoid paying).

Fourth, while its not full change management, git or subversion give me
more than I lose in source members. If I check my code into git, I have a
time stamp, WITH a user name of when I checked in each line of code. I also
can see what files I committed at the same time. I can certainly use
release branching to create a home gorwn change management system to keep
my auditors happy too,



Justin



On Wed, May 25, 2016 at 2:37 PM (WalzCraft) Jerry Forss <
JForss@xxxxxxxxxxxxx> wrote:

I am currently in a small shop with no change management (Except for me).

Before I make a pgm change I archive the source to the IFS. My pgm gets
the next version number and makes it part of the file name.

I also have a pgm that displays a list of all versions of the source and
can display/restore from the IFS.

Works well for my needs.


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steve Jones
Sent: Wednesday, May 25, 2016 12:54 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Source code on IFS

Having returned from COMMON - Thank You to all the speakers that
presented, we heard some talk about having your source code stored on the
IFS.

Does anyone have some insight as to the pros/cons/why of doing this?

This maybe the wrong list to post this, so feel free to move it to the
correct list.

Thanks

--
Steve Jones
H-P Products, Inc
330-871-2054

--
NOTE: The information in this email is confidential and may be legally
privileged. If you are not the intended recipient, you must not read, use
or disseminate the information; please advise the sender immediately by
reply email and delete this message and any attachments without retaining a
copy. Although this email and any attachments are believed to be free of
any virus or other defect that may affect any computer system into which it
is received and opened, it is the responsibility of the recipient to ensure
that it is virus free and no responsibility is accepted by H-P Products,
Inc. for any loss or damage arising in any way from its use.
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Subject to Change Notice:

WalzCraft reserves the right to improve designs, and to change
specifications without notice.

Confidentiality Notice:

This message and any attachments may contain confidential and privileged
information that is protected by law. The information contained herein is
transmitted for the sole use of the intended recipient(s) and should "only"
pertain to "WalzCraft" company matters. If you are not the intended
recipient or designated agent of the recipient of such information, you are
hereby notified that any use, dissemination, copying or retention of this
email or the information contained herein is strictly prohibited and may
subject you to penalties under federal and/or state law. If you received
this email in error, please notify the sender immediately and permanently
delete this email. Thank You;

WalzCraft PO Box 1748 La Crosse, WI. 54602-1748
www.walzcraft.com Phone... 608-781-6355
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.