Re: Source code on IFS -- MIDRANGE-L

With modern SCM tools, there's no need to remember to store this
information, since your SCM does it all for you (and more).

eg. in git, one can run a "git blame" on a source file and annotate each
line in the file with the following info:
- the commit id
- the user who made the change
- the date and time when it was made
- the line number

eg. git blame ibm_db.c:

9e5f49b8 (Kevin Adler 2015-04-30 15:28:09 -0500 774)
#ifndef PASE
9e5fe8c5 (rahul.priyadarshi@xxxxxxxxxx 2011-05-17 09:01:07 +0000 775)
rc = SQLSetStmtAttr((SQLHSTMT)((stmt_handle
*)handle)->hstmt, opt_key, (SQLPOINTER)option_num, SQL_IS_INTEGER );
9e5f49b8 (Kevin Adler 2015-04-30 15:28:09 -0500 776)
#else
9e5f49b8 (Kevin Adler 2015-04-30 15:28:09 -0500 777)
rc = SQLSetStmtAttr((SQLHSTMT)((stmt_handle
*)handle)->hstmt, opt_key, &option_num, 0 );
9e5f49b8 (Kevin Adler 2015-04-30 15:28:09 -0500 778)
#endif

Most GUI clients will show this stuff in a graphical view as well. You can
find the same info on github:
https://github.com/ibmdb/python-ibmdb/blame/ibmi/IBM_DB/ibm_db/ibm_db.c#L774
In RDi, I believe you use Team->Annotate to do the same. It will
additionally integrate with the RTC to show you the work item that was
used to check in the code.

Subversion has a similar command, with svn blame (or aliased with more
nicely named commands: annotate and praise)

Links for more information:
https://git-scm.com/docs/git-blame
https://help.github.com/articles/using-git-blame-to-trace-changes-in-a-file/
http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.blame.html

BTW, git is coming to 5733-OPS as option 6.

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 05/26/2016
10:34:26 AM:

From: Peter Dow <petercdow@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 05/26/2016 10:35 AM
Subject: Re: Source code on IFS
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

Hi Arco,

<All information about sources changes can easily been found by
comparing between revisions which can be done with a few mouseclicks.>

At one of my customers, we use the leftmost 5 positions for a change
tag, which allows differentiation of changes made the same day for 2
different reasons. How does that work with source compare utilities
you've used?

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /

On 5/26/2016 1:59 AM, Arco Simonse wrote:

Hi Steve,

I have been playing with ifs source in the past, but the omission of
SRCSTMF parameters for binder source on the CRTSVRPGM was the biggest
showstopper for me.
That may have been changed now with 7.3, although I still cannot find

much

info on it.

In our small shop for our sources we use RDI's iProjects. The

iProjects are

under version control with Subversion. This works well, but involves a

lot

of pushing and pulling overhead between the iProject and the i.
So I can see much, much benefit of moving the sources to the ifs if we

can

fully compile from there.

For some people the lose of source change dates and lines might be an
issue. We have banned this source area already for years, since it is

only

extra garbage in modern compare tools. All information about sources
changes can easily been found by comparing between revisions which can

done with a few mouseclicks.

When compiling from the ifs, the source information seems not to be

stored

with the object. When I do a DSPMOD for an ifs compiled object, I

don't see

source info.

CRTRPGMOD MODULE(DIC005) SRCSTMF('/mgsrc/cmkas/modsrc/dic005.rpgle')

Display Module
Information
Display 1
of 7
Module . . . . . . . . . . . . :
DIC005
Library . . . . . . . . . . :
CMKASOBJ
Detail . . . . . . . . . . . . :
*BASIC
Module attribute . . . . . . . :
RPGLE

Module
information:
Module creation date/time . . . . . . . . . . . . . . : 26/05/16
10:53:02
Source file . . . . . . . . . . . . . . . . . . . . .
:
Library . . . . . . . . . . . . . . . . . . . . . .
:
Source member . . . . . . . . . . . . . . . . . . . .
:
Source file change date/time . . . . . . . . . . . .
:

This is an important missing piece of information I believe. I think

i'll

put an RFE for updating that area also for ifs compiles.

Regards,
-Arco

2016-05-25 19:53 GMT+02:00 Steve Jones <sjones@xxxxxxxxxxxxxxx>:

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

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 recipientto

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.

--
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.