VSCODE encoding error IBM-1208 since 3.1.0 update #330

rsjrny · 2023-03-11T11:21:11Z

rsjrny
Mar 11, 2023

since the extension update 3.1.0 on 3/10/23 I have started receiving an encoding issue with CopyToPDS in groovy. If I initiate the same user build directly from USS the CopyToPDS works fine. I assume it has something to do with the transfer from windows to USS.

I am at a loss as to where to start looking for a possible setting change. any help would be appreciated

2023-03-11T11:06:46.416Z: Caught: com.ibm.dbb.build.BuildException: java.io.UnsupportedEncodingException: ibm-1208
2023-03-11T11:06:46.421Z: com.ibm.dbb.build.BuildException: java.io.UnsupportedEncodingException: ibm-1208
2023-03-11T11:06:46.426Z: at com.ibm.dbb.build.CopyToPDS.execute(CopyToPDS.java:89)
2023-03-11T11:06:46.429Z: at BuildUtilities.copySourceFiles(BuildUtilities.groovy:100)
2023-03-11T11:06:46.432Z: at Assembler$_run_closure1.doCall(Assembler.groovy:36)
2023-03-11T11:06:46.438Z: at Assembler.run(Assembler.groovy:28)
2023-03-11T11:06:46.443Z: at Assembler$run.callCurrent(Unknown Source)
2023-03-11T11:06:46.445Z: at com.ibm.dbb.groovy.ScriptLoader._run(ScriptLoader.groovy:124)
2023-03-11T11:06:46.448Z: at com.ibm.dbb.groovy.ScriptLoader$_run$0.call(Unknown Source)
2023-03-11T11:06:46.458Z: at com.ibm.dbb.groovy.ScriptLoader.runScript(ScriptLoader.groovy:81)
2023-03-11T11:06:46.461Z: at build$_run_closure1.doCall(build.groovy:63)
2023-03-11T11:06:46.464Z: at build.run(build.groovy:54)
2023-03-11T11:06:46.467Z: Caused by: java.io.UnsupportedEncodingException: ibm-1208
2023-03-11T11:06:46.472Z: at com.ibm.dbb.build.CopyToPDS.copyAsText(CopyToPDS.java:379)
2023-03-11T11:06:46.476Z: at com.ibm.dbb.build.CopyToPDS.copyAsText(CopyToPDS.java:306)
2023-03-11T11:06:46.478Z: at com.ibm.dbb.build.CopyToPDS.copyFile(CopyToPDS.java:232)
2023-03-11T11:06:46.481Z: at com.ibm.dbb.build.CopyToPDS.doCopy(CopyToPDS.java:179)
2023-03-11T11:06:46.490Z: at com.ibm.dbb.build.CopyToPDS.execute(CopyToPDS.java:85)

FALLAI-Denis · 2023-03-11T11:46:17Z

FALLAI-Denis
Mar 11, 2023

Hi @rsjrny

Zowe Explorer upgraded to 2.6.2 on March 8, roughly at the same time as Z Open Editor upgraded to 3.1.0 on March 10.

It seems to me that Z Open Editor uses the functions of Zowe Explorer for file transfers.
Have you tried downgrading Zowe Explorer to version 2.6.1 to see if that fixed the issue?

From the error message on the CopyToPds DBB function, I understand that zAppbuild is trying to copy a UTF-8 (IBM-1208) encoded file to a PDS.
UTF-8 is a multi-byte format and I think the PDS is déclare with RECFM=FB, which is not compatible with UTF-8 storage which requires RECFM=VB format.

Have you analyzed the code transferred by ZOE by viewing the file directly from z/OS (3.17) or from an SSH session on USS run the ls -alT command to see the file encoding on USS?
In my opinion the transferred file should be encoded in EBCDIC on z/OS-USS and not in UTF-8 (IBM-1208).

2 replies

rsjrny Mar 11, 2023
Author

I will try that. I also noticed this morning that quit a few of my 'favorites' in zowe were missing

FALLAI-Denis Mar 11, 2023

If you use z/OSMF, the encoding of the transfer is declared in the Zowe CLI z/OSMF profile used, and the profile is declared in the zowe.config.json file which is in the scope of the execution context of the transfer .

rsjrny · 2023-03-11T12:02:39Z

rsjrny
Mar 11, 2023
Author

@FALLAI-Denis ,

downgraded to zowe explorer 2.6.2 and have the same issue

2 replies

rsjrny Mar 11, 2023
Author

@FALLAI-Denis,
i issued the ls -alT on USS and it appears the files that I tried to build today from vscode are UTF-8 where all the files I previously built are IBM-1047

FALLAI-Denis Mar 11, 2023

IBM-1047 is the default encoding for USS...also default for Zowe CLI... not sure it's right for your programs.
If US site, then it is rather an IBM-037 encoding (z/OS default, assembler, rexx...) or IBM-1140 (COBOL compiler default).

FALLAI-Denis · 2023-03-11T12:47:24Z

FALLAI-Denis
Mar 11, 2023

I suggest to create an issue from this discussion.

0 replies

FALLAI-Denis · 2023-03-11T12:58:01Z

FALLAI-Denis
Mar 11, 2023

During my own tests with the IBM User Build function, I saw the commands passed by ZOE and in particular the transfer of the file to build:

Executing SSH command: 
Uploading file c:\Trv\DepotsGIT\environn-techleads-sandbox\src\COBOL\MINIMAL.cbl to /u/J070188/vscode/environn-techleads-sandbox/src/COBOL/MINIMAL.cbl with encoding ibm-1147
Using ssh profile TMVS-SSH
Executing SSH command: 
chtag -tc ibm-1147 /u/J070188/vscode/environn-techleads-sandbox/src/COBOL/MINIMAL.cbl

Do you have the same?
Is there a chtag command to specify the encoding of the file after transfer?

Have you checked your ssh profile at zowe.config.json?

0 replies

rsjrny · 2023-03-11T16:16:58Z

rsjrny
Mar 11, 2023
Author

I will turn this into an issue, thanks.

One other item I just now saw is log downs are seeing 0 logs but the log directory has quite a few logs

2023-03-11T16:13:22.358Z: Looking for user build logs in "/u/XXXXX/dbbuild/xxxv010/logs".
2023-03-11T16:13:22.359Z: Total log files found: 0
2023-03-11T16:13:22.360Z: Downloading logs to c:\Repos\XXXX\ISSUE-XXXX-nnn-xxxv010\logs
2023-03-11T16:13:22.362Z: Successfully finished downloading of 0 log files

Pathname . : /u/XXXXX/dbbuild/xxxxv010
EUID . . . : XXXX
Command Filename Message

     .                          
     ..                         
     build.20230303.            
     build.20230303.            
     build.20230303.            
     build.20230303.            
     build.20230303.            
     build.20230303.            
     build.20230303.            
     build.20230303.            
     build.20230303.            
     build.20230303.            
     build.20230303.            
     build.20230304.            
     build.20230304.            
     build.20230310.            
     build.20230310.            
     buildList.txt

4 replies

FALLAI-Denis Mar 11, 2023

I was speaking about log for IBM User Build in VS Code, not about log of zAppbuild.

rsjrny Mar 11, 2023
Author

Yes,

I was posting the zAppBuild log because it is very curious how the USS directory is full of logs but the download in vscode is reporting 0

Here is the userBuild log and the tagging

2023-03-11T20:23:41.969Z: Uploading file c:\RocketRepos\TMON\TMON-18926-tmhmv010\tmhmhsi.srclib to /u/ts4579/build/tmhmv010/tmhmhsi.srclib with encoding utf-8
2023-03-11T20:23:42.290Z: Using ssh profile rsi2ssh
2023-03-11T20:23:42.291Z: Executing SSH command:
chtag -tc utf-8 '/u/xxxxxx/build/xxxv010/tmhmhsi.srclib'
2023-03-11T20:23:42.714Z: $ chtag -tc utf-8 '/u/xxxx/build/xxxv010/tmhmhsi.srclib'
2023-03-11T20:23:42.724Z: $ exit $?

FALLAI-Denis Mar 13, 2023

Hi,
I think ZOE use z/OSMF (or RSE) profile to upload files to USS, and then use SSH profile to tag uploaded file according encoding defined in z/OSMF (or RSE) profile.
Do you check your z/OSMF (or RSE) profile ?

Look for similar informations in your IBM User Buiild log:

The default Zowe CLI profile specified as GMVS in zopeneditor.zowe setting. Will try loading that.
Using Zowe profile GMVS
Using SSH profile GMVS-SSH

Checking if SSH profile GMVS-SSH can connect:
Connected successfully.

Executing SSH command: 
mkdir -p '/u/J070188/vscode/environn-techleads-sandbox/src/S9T/COBOL'
@@START OF COMMAND@@
$ mkdir -p '/u/J070188/vscode/environn-techleads-sandbox/src/S9T/COBOL'
$ exit $?
Uploading file c:\Trv\DepotsGIT\environn-techleads-sandbox\src\S9T\COBOL\minimal.cbl to /u/J070188/vscode/environn-techleads-sandbox/src/S9T/COBOL/minimal.cbl with encoding ibm-1147

rsjrny Mar 13, 2023
Author

These are the same profiles I have used for months but I will check to see if something may have changed

2023-03-13T14:56:07.974Z: The default Zowe CLI profile specified as RSI2 in zopeneditor.zowe setting. Will try loading that.
2023-03-13T14:56:07.976Z: Using Zowe profile RSI2
2023-03-13T14:56:08.521Z: Using ssh profile rsi2ssh
2023-03-13T14:56:08.523Z: 
2023-03-13T14:56:08.523Z: Checking if SSH profile rsi2ssh can connect:
2023-03-13T14:56:09.080Z: Connected successfully.
2023-03-13T14:56:09.081Z: 
2023-03-13T14:56:09.425Z: Executing SSH command: 
mkdir -p '/u/ts4579/build/tmhmv010'
2023-03-13T14:56:09.894Z: $ mkdir -p '/u/ts4579/build/tmhmv010'
2023-03-13T14:56:09.904Z: $ exit $?
2023-03-13T14:56:09.909Z: No encoding found for *thma251.srclib. Assigning default encoding of utf-8

phaumer · 2023-03-13T15:51:08Z

phaumer
Mar 13, 2023
Maintainer

@rsjrny you can specify the target encoding for different file types by file extension or name pattern using a .gitattributes files: https://www.ibm.com/docs/en/cloud-paks/z-modernization-stack/2022.4?topic=code-setting-up-user-build.

We chose .gitattributes as we assumes that users with git would have such files already. At the moment we will take the .gitattributes file from the workspace's top-level directory.

1 reply

rsjrny Mar 13, 2023
Author

thanks,

same here.

.gitattributes zos-working-tree-encoding=iso8859-1
.gitignore     zos-working-tree-encoding=iso8859-1
*              zos-working-tree-encoding=ibm-1047

phaumer · 2023-03-13T19:19:21Z

phaumer
Mar 13, 2023
Maintainer

@rsjrny are you saying that you do have that .gitattributes file in your workspace and the files still get uploaded as utf-8?

4 replies

rsjrny Mar 13, 2023
Author

Yes, those are my settings.

As far as I can tell the only changes were the 3/10/23 updates to zowe explorer and z/is editor.
Prior to the update all was well.

I backed off the updates but still have the issue.

I did also receive a windows update right around the same time.

FALLAI-Denis Mar 13, 2023

I just tested: same problem for me...

rsjrny Mar 13, 2023
Author

So glad I am no alone and crazy in this new world.

Thanks for testing.

FALLAI-Denis Mar 13, 2023

Sorry, I made a typo in my .gitattributes file during my tests...
In fact IBM User Build works if you specify each file extension in the .gitattributes file.
What no longer works since ZOE 3.1.0 is the declaration of default values.
See my comment at the issue level.

phaumer · 2023-06-15T23:08:19Z

phaumer
Jun 15, 2023
Maintainer

We added the ability to utilize the git check-attr command in the background to evaluate .gitattributes in Z Open Editor 3.2.0. If our code can find the command in the path it will use it, otherwise fall back to our previous algorithm.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

VSCODE encoding error IBM-1208 since 3.1.0 update #330

{{title}}

Replies: 8 comments 13 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

VSCODE encoding error IBM-1208 since 3.1.0 update #330

Replies: 8 comments · 13 replies

rsjrny Mar 11, 2023 Author

rsjrny Mar 11, 2023 Author

rsjrny Mar 11, 2023 Author

rsjrny Mar 11, 2023 Author

Pathname . : /u/XXXXX/dbbuild/xxxxv010 EUID . . . : XXXX Command Filename Message

rsjrny Mar 11, 2023 Author

rsjrny Mar 13, 2023 Author

phaumer Mar 13, 2023 Maintainer

rsjrny Mar 13, 2023 Author

phaumer Mar 13, 2023 Maintainer

rsjrny Mar 13, 2023 Author

rsjrny Mar 13, 2023 Author

phaumer Jun 15, 2023 Maintainer

Replies: 8 comments 13 replies

rsjrny Mar 11, 2023
Author

rsjrny
Mar 11, 2023
Author

rsjrny Mar 11, 2023
Author

rsjrny
Mar 11, 2023
Author

Pathname . : /u/XXXXX/dbbuild/xxxxv010
EUID . . . : XXXX
Command Filename Message

rsjrny Mar 11, 2023
Author

rsjrny Mar 13, 2023
Author

phaumer
Mar 13, 2023
Maintainer

rsjrny Mar 13, 2023
Author

phaumer
Mar 13, 2023
Maintainer

rsjrny Mar 13, 2023
Author

rsjrny Mar 13, 2023
Author

phaumer
Jun 15, 2023
Maintainer