Copy them out. Before ACMS (not the current name) knew about git and put in it's own handling system, I had hooks that took every promote and copied the file out to the ifs and did a commit. Even before that I used to routinely save all of our source into an SVN repository. This is the program I used to do that. SVNMBRS was just output from DSPFD TYPE(*MBR)
PGM
DCLF FILE(SVNMBRS)
LOOP: RCVF
MONMSG MSGID(CPF0864) EXEC(GOTO CMDLBL(ENDPGM)) /* +
EOF */
IF COND(&MBSEU2 *NE ' ') +
THEN(CPYTOSTMF +
FROMMBR('/qsys.lib/msibetobjs.lib/' *TCAT +
&MBFILE *TCAT '.file/' *TCAT &MBNAME +
*TCAT '.mbr') TOSTMF('/svn/' *TCAT +
&MBNAME *TCAT '.' *TCAT &MBSEU2) +
STMFOPT(*REPLACE) STMFCCSID(*PCASCII))
ELSE CMD(CPYTOSTMF +
FROMMBR('/qsys.lib/msibetobjs.lib/' *TCAT +
&MBFILE *TCAT '.file/' *TCAT &MBNAME +
*TCAT '.mbr') TOSTMF('/svn/' *TCAT +
&MBNAME) STMFOPT(*REPLACE) +
STMFCCSID(*PCASCII))
GOTO CMDLBL(LOOP)
ENDPGM: ENDPGM
On Wed, 2020-03-04 at 17:26 +0100, Patrik Schindler wrote:
Hello Jim,
Am 04.03.2020 um 17:04 schrieb
<mailto:midrangel@xxxxxxxxxxxxxxxxx>
midrangel@xxxxxxxxxxxxxxxxx
:
At the level of software you are at you could not use IFS for development.
That's not entirely true. The C-Compiler can read files from IFS. However, I never tested it.
We can now use the IFS in modern RDi and development environments. Been that way for some time.
I believe. But it's still not clear how you want to do this actual migration, because Jim Franz explicitly was mentioning file members.
So, allow me to repeat my question: How's Jim Franz supposed to be exploiting the IFS as intermediate transfer facility? Only QSYS.LIB knows about file members.
:wq! PoC
PGP-Key: DDD3 4ABF 6413 38DE -
<
https://www.pocnet.net/poc-key.asc>
https://www.pocnet.net/poc-key.asc
[
https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com
CONFIDENTIALITY NOTICE
This document and any accompanying this email transmission contain confidential information, belonging to the sender that is legally privileged. This information is intended only for the use of the individual or entity named above. The authorized recipient of this information is prohibited from disclosing this information to any other party and is required to destroy the information after its stated need has been fulfilled. If you are not the intended recipient, or the employee of agent responsible to deliver it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or action taken in reliance on the contents of these documents is STRICTLY PROHIBITED. If you have received this email in error, please notify the sender immediately to arrange for return or destruction of these documents.
midrange.com
