Help with SWAPUSRPRF

[Gad Miron <gadmiron@xxxxxxxxx>]

Hello Rob, Alan

I guess I was not too clear indeed

First, a code snippet

CALL       PGM(SWAPUSRPRF) PARM('AS400' '*NOPWDCHK')
DLYJOB     DLY(2)
MKDIR      DIR(&PATH)
MONMSG     MSGID(CPF0000)

CHGVAR     VAR(&FULLFILENM) VALUE(&PATH *TCAT '/' *CAT  &TXTFILEm)
CPYTOIMPF  FROMFILE(QTEMP/CRDSNDmF) TOSTMF(&FULLFILENM)
     MBROPT(*REPLACE) STMFCCSID(1255)  RCDDLM(*CRLF) DTAFMT(*FIXED)
 NUMFLDPAD(*NONE) ORDERBY(*arrival)

  as you can see there is no MONMSG following CPYTOIMPF
(and no, there is no MONMSG  MSGID(CPF0000) at the start of the program  )

Second,
The program worked fine a month ago

Third
Why swapping is not done when calling  SWAPUSRPR in the CL PGM
  but works fine when called in the command line

Forth
Why without swapping an empty file is created .

a shot in the dark, Activation group ?

TIA
Gad







> Hi Gad
> You ask
> I certainly could use some advice .
> The question I have to ask is - on what?
> I am guessing that you are wondering why the CL PGM where SWAPUSRPRF does
> not do the swap (or so it seems)
> You are wondering why no error is returned
> Without seeing the actual CL PGM, its going to be hard
> Maybe the CL program has an all encompassing
> MONMSG     MSGID(CPF0000)
> At the start of the program
> This means that ANY error the program encounters - well - just keep on
> marching as if nothing happened
> Another thought is that the error happens on the windows side - but is not
> conveyed back to the CL program
>
> You also don't say what release you are on
> I don't know if that makes any difference - but you never know
>
>
> Alan Shore
> E-mail : ASHORE@xxxxxxxx
> Phone [O] : (631) 200-5019
> Phone [C] : (631) 880-8640
> 'If you're going through hell, keep going.'
> Winston Churchill
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
> Of Gad Miron
> Sent: Wednesday, October 21, 2020 6:46 AM
> To: midrange-l@xxxxxxxxxxxxxxxxxx
> Subject: [EXTERNAL] Help with SWAPUSRPRF
>
> Hello pundits
>
> We have several CL programs calling SWAPUSRPRF ('WINUSER'  *NOPWDCHK)
> before executing CPYTOIMPF (using a user a known to the Windowz domain) and
> then revert to the original user.
>
> I recently encountered a CL PGM where SWAPUSRPRF does not do the swap (or
> so it seems) No error is returned and an empty file is created in the
> target directory.
>
> Executing the same CALL  SWAPUSRPRF ('WINUSER'  *NOPWDCHK) in the COMMAND
> LINE  and then calling the A/M CL PGM  works fine .
>  - a (non-empty) file is created in the target Windows directory alright.
>
> We use an RPGLE version of  SWAPUSRPRF
>
> I certainly could use some advice .
>
> TIA
> Gad
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
>
>
>
>
>
> I'm a little confused also.
> One question I have is how can it create a blank file on the target but
> not write to it?  Is the error really on the source?
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  7310 Innovation Blvd, Suite 104
>           Ft. Wayne, IN 46818
> Ship to:  7310 Innovation Blvd, Dock 9C
>           Ft. Wayne, IN 46818
> http://www.dekko.com
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Alan Shore via MIDRANGE-L
> Sent: Wednesday, October 21, 2020 7:47 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Cc: Alan Shore <ashore@xxxxxxxx>
> Subject: RE: [EXTERNAL] Help with SWAPUSRPRF
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> Hi Gad
> You ask
> I certainly could use some advice .
> The question I have to ask is - on what?
> I am guessing that you are wondering why the CL PGM where SWAPUSRPRF does
> not do the swap (or so it seems)
> You are wondering why no error is returned
> Without seeing the actual CL PGM, its going to be hard
> Maybe the CL program has an all encompassing
> MONMSG     MSGID(CPF0000)
> At the start of the program
> This means that ANY error the program encounters - well - just keep on
> marching as if nothing happened
> Another thought is that the error happens on the windows side - but is not
> conveyed back to the CL program
>
> You also don't say what release you are on
> I don't know if that makes any difference - but you never know
>
>
> Alan Shore
> E-mail : ASHORE@xxxxxxxx
> Phone [O] : (631) 200-5019
> Phone [C] : (631) 880-8640
> 'If you're going through hell, keep going.'
> Winston Churchill
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
> Of Gad Miron
> Sent: Wednesday, October 21, 2020 6:46 AM
> To: midrange-l@xxxxxxxxxxxxxxxxxx
> Subject: [EXTERNAL] Help with SWAPUSRPRF
>
> Hello pundits
>
> We have several CL programs calling SWAPUSRPRF ('WINUSER'  *NOPWDCHK)
> before executing CPYTOIMPF (using a user a known to the Windowz domain) and
> then revert to the original user.
>
> I recently encountered a CL PGM where SWAPUSRPRF does not do the swap (or
> so it seems) No error is returned and an empty file is created in the
> target directory.
>
> Executing the same CALL  SWAPUSRPRF ('WINUSER'  *NOPWDCHK) in the COMMAND
> LINE  and then calling the A/M CL PGM  works fine .
>  - a (non-empty) file is created in the target Windows directory alright.
>
> We use an RPGLE version of  SWAPUSRPRF
>
> I certainly could use some advice .
>
> TIA
> Gad
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
>
>
> ------------------------------
>
> message: 4
> date: Wed, 21 Oct 2020 14:29:20 +0200
> from: Alex Mart?nez <ajut400@xxxxxxxxx>
> subject: Re: Trying to recover after losing a disk
>
> Hi
>
> Perhaps there is an error on the JS12 #8250 SAS Expansion Card (CFFv) and
> it is the cause of the loss of connectivity with the external disks
>
> Have you checked the VIOS errlog annotations?
>
>
> El mi?., 21 oct. 2020 a las 3:26, Pete Helgren (<pete@xxxxxxxxxx>)
> escribi?:
>
> > Take a trip on the wayback....
> >
> > I have a JS12 Blade in a BC-S.  Two storage modules with 6 15k 300GB SAS
> > drives each.  No RAID controller (standard SAS controller).  The JS12
> > has VIOS which is mirrored in rootvg - he seems to be OK. For IBM i I
> > have two LPARs  1 LPAR running 7.2 has 4 disks but they are "double
> > mirrored"; that is I have two sets of mirrored drives (don't ask) and
> > LPAR 2 has one set of mirrored drives.  I have a 3rd LPAR running SUSE
> > on a single drive.  I cannot connect at the moment to anything but VIOS
> > and the AMM. Using the 5250 console fails to connect to either LPAR.  I
> > swapped out the bad drive and I have a vague feeling that was the wrong
> > thing to do.  But the biggest issue issue I that I cannot connect to
> > either IBM i LPAR.
> >
> > IVM shows that each LPAR has an SRC.  The 7.2 partition has SRC
> > A6010255  and the 7.1 partition has SRC A6010255   When I looked up the
> > 7.2 SRC it had this helpful note:
> >
> > Explanation
> > Contact was lost with the device indicated.
> > Response
> > Do not power off the system.
> > Perform the procedure indicated in the failing item list.
> > Failing Item
> > LICIP13
> > FI00580
> > FI00500
> > FI00302
> > FI00301
> > AJDG301
> >
> > Nice...except how do I find out the "failing item"?  When I click on the
> > SRC link in IVM it gives me this:
> >
> > Reference code:    A60C0255
> > Description:    Contact was lost with the device indicated
> > Time stamp (UTC):    10/21/20 12:05:18 AM
> > Word 2:    0DB08062
> > Word 3:    00010004
> > Word 4:    00000027
> > Word 5:    00000000
> > Word 6:    000100FF
> > Word 7:    00FF0280
> > Word 8:    6B220050
> > Word 9:    B6005120
> >
> > Nice again....but where is the failing item indicated?   I know it's a
> > hard disk that failed because the AMM told me that.  But I am not 100%
> > sure it failed on one of my IBM i partitions.  It failed in the storage
> > module but I am not sure the lost drive was used by IBM i.  Plus, the
> > drives are mirrored so they should be degraded, not inaccessible....
> >
> > Perhaps something else failed rather than only the drive....this guy is
> > getting pretty long in the tooth.  So if someone could point me as to
> > how to move forward on this adventure, I would appreciate it.
> >
> > --
> > Pete Helgren
> > www.petesworkshop.com
> > GIAC Secure Software Programmer-Java
> > AWS Certified Cloud Practitioner
> > Twitter - Sys_i_Geek  IBM_i_Geek
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at https://archive.midrange.com/midrange-l.
> >
> > Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> > questions.
> >
> > Help support midrange.com by shopping at amazon.com with our affiliate
> > link: https://amazon.midrange.com
>
>
> ------------------------------
>
> message: 5
> date: Wed, 21 Oct 2020 07:30:03 -0500
> from: Pete Helgren <pete@xxxxxxxxxx>
> subject: Re: Trying to recover after losing a disk
>
> Thanks Roberto,
>
> Below Partition 2 is the 7.2 LPAR amd Partition 3 is the 7.1 LPAR?? I
> just checked with the guys who manage the rack and they mentioned the
> power was off for several hours a week ago (I was out of town).?
> Everything came back up (supposedly).? So, again, the error listed in
> the IVM is SRC A60C0255 "Description: Contact was lost with the device
> indicated"?? So how do I determine the "device"??? I assumed it was the
> disk but without knowing for sure, something else could have failed.
>
> It's a development machine so I wasn't really paying attention. The
> system error in the AMM is from the 14th: "(10/14/20 16:24:06)? (System
> Event) system hardware failure"? The disk failure that the AMM reported
> is now gone as I replaced the disk.
>
>
> $ lsmap -all
> SVSA??????????? Physloc Client Partition ID
> --------------- --------------------------------------------
> ------------------
> vhost0????????? U7998.60X.10270CA-V1-C11 0x00000002
>
> VTD?????????????????? vtscsi0
> Status??????????????? Available
> LUN?????????????????? 0x8100000000000000
> Backing device??????? hdisk2
> Physloc?????????????? U4545.001.07AY127-P1-D1
>
> VTD?????????????????? vtscsi1
> Status??????????????? Available
> LUN?????????????????? 0x8200000000000000
> Backing device??????? hdisk3
> Physloc?????????????? U4545.001.07AY127-P1-D2
>
> VTD?????????????????? vtscsi2
> Status??????????????? Available
> LUN?????????????????? 0x8300000000000000
> Backing device??????? hdisk4
> Physloc?????????????? U4545.001.07AY127-P1-D3
>
> VTD?????????????????? vtscsi3
> Status??????????????? Available
> LUN?????????????????? 0x8400000000000000
> Backing device??????? hdisk14
> Physloc?????????????? U4545.001.07AY127-P1-D4
>
> SVSA??????????? Physloc Client Partition ID
> --------------- --------------------------------------------
> ------------------
> vhost1????????? U7998.60X.10270CA-V1-C13 0x00000003
>
> VTD?????????????????? vtopt0
> Status??????????????? Available
> LUN?????????????????? 0x8200000000000000
> Backing device
> Physloc
>
> VTD?????????????????? vtscsi4
> Status??????????????? Available
> LUN?????????????????? 0x8100000000000000
> Backing device??????? hdisk6
> Physloc?????????????? U4545.001.07AY127-P1-D5
>
> SVSA??????????? Physloc Client Partition ID
> --------------- --------------------------------------------
> ------------------
> vhost2????????? U7998.60X.10270CA-V1-C14 0x00000002
>
> VTD?????????????????? vttape0
> Status??????????????? Available
> LUN?????????????????? 0x8100000000000000
> Backing device??????? rmt0
> Physloc U78A5.001.WIH1BE8-P1-C10-T1-L5005076312447387-L0
>
>
> Pete Helgren
> www.petesworkshop.com
> GIAC Secure Software Programmer-Java
> AWS Certified Cloud Practitioner
> Twitter - Sys_i_Geek  IBM_i_Geek
>
> On 10/20/2020 9:20 PM, Roberto Jos? Etcheverry Romero wrote:
> > I assume the disk is provided by the VIOS, if that is the case you have
> to
> > check the VIOS's filesystems / file based disks / mappings to check what
> is
> > dead.
> > lsmap -all will tell you what is mapped to what and from there we can
> work
> > out what is going on. It is weird you say that there are different disks
> > mirrored and for only one disk to kill everything. I think that it might
> > not be the case and maybe VIOS was providing disk based disks. lsmap will
> > tell us.
> >
> >
> > On Tue, Oct 20, 2020 at 10:26 PM Pete Helgren <pete@xxxxxxxxxx> wrote:
> >
> > > Take a trip on the wayback....
> > >
> > > I have a JS12 Blade in a BC-S.  Two storage modules with 6 15k 300GB SAS
> > > drives each.  No RAID controller (standard SAS controller).  The JS12
> > > has VIOS which is mirrored in rootvg - he seems to be OK. For IBM i I
> > > have two LPARs  1 LPAR running 7.2 has 4 disks but they are "double
> > > mirrored"; that is I have two sets of mirrored drives (don't ask) and
> > > LPAR 2 has one drive.  I have a 3rd LPAR running SUSE
> > > on a single drive.  I cannot connect at the moment to anything but VIOS
> > > and the AMM. Using the 5250 console fails to connect to either LPAR.  I
> > > swapped out the bad drive and I have a vague feeling that was the wrong
> > > thing to do.  But the biggest issue issue I that I cannot connect to
> > > either IBM i LPAR.
> > >
> > > IVM shows that each LPAR has an SRC.  The 7.2 partition has SRC
> > > A6010255  and the 7.1 partition has SRC A6010255   When I looked up the
> > > 7.2 SRC it had this helpful note:
> > >
> > > Explanation
> > > Contact was lost with the device indicated.
> > > Response
> > > Do not power off the system.
> > > Perform the procedure indicated in the failing item list.
> > > Failing Item
> > > LICIP13
> > > FI00580
> > > FI00500
> > > FI00302
> > > FI00301
> > > AJDG301
> > >
> > > Nice...except how do I find out the "failing item"?  When I click on the
> > > SRC link in IVM it gives me this:
> > >
> > > Reference code:    A60C0255
> > > Description:    Contact was lost with the device indicated
> > > Time stamp (UTC):    10/21/20 12:05:18 AM
> > > Word 2:    0DB08062
> > > Word 3:    00010004
> > > Word 4:    00000027
> > > Word 5:    00000000
> > > Word 6:    000100FF
> > > Word 7:    00FF0280
> > > Word 8:    6B220050
> > > Word 9:    B6005120
> > >
> > > Nice again....but where is the failing item indicated?   I know it's a
> > > hard disk that failed because the AMM told me that.  But I am not 100%
> > > sure it failed on one of my IBM i partitions.  It failed in the storage
> > > module but I am not sure the lost drive was used by IBM i.  Plus, the
> > > drives are mirrored so they should be degraded, not inaccessible....
> > >
> > > Perhaps something else failed rather than only the drive....this guy is
> > > getting pretty long in the tooth.  So if someone could point me as to
> > > how to move forward on this adventure, I would appreciate it.
> > >
> > > --
> > > Pete Helgren
> > > www.petesworkshop.com
> > > GIAC Secure Software Programmer-Java
> > > AWS Certified Cloud Practitioner
> > > Twitter - Sys_i_Geek  IBM_i_Geek
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
>
>
> ------------------------------
>
> End of MIDRANGE-L Digest, Vol 19, Issue 1540
> ********************************************