Exit conversion for specific FTP matches

[misi01]

My apologies Aaron

I must have missed that note (or tried it and forgot to append the results).

Long and the short of it - it "didn't" work (I say that reservedly, based on a possible misunderstanding as detailed just below)

However ...... (not sure if there was a misunderstanding between us), but the following finally seemed to work.

Open the session with the following folder names

ftp://[email protected]/'qual1.qual2.name' (note the quotes surrounding the mainframe PDS filename)

Now change the file format to be

ftp://...\'qual1.qual2*\*

note the trailing *\* and the lack of a trailing closing quote.

[Aaron]

Hello,

I believe you received an earlier email on the 27th that suggested to "Try adding an extra "\*" to the end of your paths."

So you should end up with something like:
ftp://...\'misi01.boka*\*

How does that work for you?

[misi01]

Bump

Tried another user's machine. They are on 3.0.15, build 9758.

I'll attach screen captures showing exactly the same file format and masks and showing how their version of BC automatically chooses the correct file format whereas mine never does.

One small difference I can see between here layout and mine is that her "filename" (in the green area) is shown as 'misi01.boka.cobol.boka0010' whereas mine is shown as 'misi01.boka.cobol'/boka0010 - don't know if that's just a coincidence

[misi01]

Have zipped the directories from the stick

and sent them to you offline

[misi01]

Exporting

This is why I asked for exact instructions.

To repeat. I navigated to MY c:\program files\Beyond Compare 3 and exported this to the USB stick.
I then went to my colleague's machine and navigated to HIS %AppData% directory and exported 5-6 (?) xml files to the stick.

I then started BC from the Beyond Compare 3 folder on the stick and received the results I outlined above.

As mentioned earlier, my BC is 3.2.3, build 13046, his is 3.0.15 build 9758.

Is there anything else I should be doing ????

[Aaron]

Hello,

Which version of BC3 are you running on your machine, and which version is it working for your coworker on his machine?

When you "export", are you navigating to the %AppData% directory and copying all of the files out of that directory and placing them on your usb stick? You should see your BC3key.txt, BCState.xml, BCSessions.xml, BCCommands.xml, and various other BCSettingsfiles.xml files in the directory. Alternatively to navigating manually, you can use the Help menu -> Support; Export option to generate a Support.zip that contains all of these files. Then extract the zip into your portable install. This way, you can generate a Support.zip from his working setup and apply it to a Portable install (either your BC directory or his). If created correctly, if you make a Portable install of HIS directory and use his settings from the Support.zip, this Portable Install should function identically to normally running BC3 on his machine.

[misi01]

If I did everything correctly....

I exported my whole BC folder to the USB stick. Then I exported his files (various XML files) as well.

I then ran BC from this stick on his PC and the problem of the FTP formats not being recognized/chosen kicked in. Remove the stick and run BC from his C-drive, no problem.

It certainly seems like it's a problem with the latest build (or least some build after his one and before mine)

Experimented some more. Copied HIS BC directory to the stick and ran BC from there. Now it tries to apply the file format to both windows, even though one mask is specified as ftp://...\'sysabc* and the other is defined as ftp://...\'sysabc.proclib.* and the mainframe files are ftp://[email protected]/'sysabc.ft.proclib.member' and ftp://[email protected]/'sysabc.proclib.member'

[Zoë]

Copy your entire BC install directory and his entire %AppData%\Scooter Software\Beyond Compare folder. BCState.xml will be one of several files from his folder; you need them all.

[misi01]

I must be missing something here

You're saying that I should copy the BC folder to a USB stick as well as exporting all the settings to that same stick plus BCState.xml.

If this is correct, from where should these 3 items come - his or my PC ?

[Zoë]

Export all of your settings into that folder, not just BCState.xml. That's just the file that tells BC it's in portable mode.

[misi01]

Well - that didn't work too well

I did what you said. Exported MY BC folder to a USB stick and copied the "correct" user's BCSTATE.XML to the same directory on the stick.

Started BC from the stick, and of course (?), the file formats weren't available. Imported them and tried to open a folder on the mainframe. Instead of getting a list of all the members in each folder, I get a message stating

File not found (ftp.//[email protected]_site/'userid.boka.cobol')

Running from my C-drive, everything works fine (well, apart from BC not recognizing and using the correct file format)

[Zoë]

The portable install doesn't touch the registry or your existing settings and doesn't require administrative access. It's just a standalone version that sits in its own directory, and you can delete it by deleting the folder.

If you can't do that for some reason, you can get the same results just by copying files. Copy your BC v3.2.4 install directory somewhere, and copy their %AppData%\Scooter Software\Beyond Compare 3 contents into it (so BCState.xml is in the same folder as BCompare.exe). That's a portable install. Just launch the exe directly.

[misi01]

Portable install might be a problem

inasmuch as BC3 is "pushed" onto our machines at work by a central application - we don't install the code ourselves (apart from the updates)

[Zoë]

I was testing 3.2.4 when I originally responded, so I don't think anything changed that would have affected this. Have him do a portable install of 3.2.3 then copy the contents of his %AppData%\Scooter Software\Beyond Compare 3 directory into the install directory so they're using the same settings and see if he sees the same behavior you do.

[misi01]

Just been talking to an enthuiastic BC user

regarding BC and showed him the exit program I'd written.

To my surprise, when he selected the same mainframe members as I did, BC chose the "correct" file formats automatically for him.

My BC is 3.2.3, build 13046, his is 3.0.15 build 9758, so something's obviously (?) been corrupted between the 2 builds.