Troubleshooting Workflow Manager Messages and

Workflow Manager Messages andTroubleshooting

Micro FocusThe Lawn22-30 Old Bath RoadNewbury, Berkshire RG14 1QNUKhttp://www.microfocus.com

Copyright © Micro Focus . All rights reserved.

MICRO FOCUS, the Micro Focus logo and are trademarks or registered trademarks of MicroFocus IP Development Limited or its subsidiaries or affiliated companies in the UnitedStates, United Kingdom and other countries.

All other marks are the property of their respective owners.

2014-10-15

ii

Contents

Introduction ...................................................................................................... 14Error messages ................................................................................................ 17

TAURUS core (TSCOR) messages ...................................................................................17TSCOR0001 ...........................................................................................................17TSCOR0002 ...........................................................................................................17TSCOR0003 ...........................................................................................................17TSCOR0004 ...........................................................................................................18TSCOR0005 ...........................................................................................................18TSCOR0007 ...........................................................................................................18TSCOR0008 ...........................................................................................................18TSCOR0009 ...........................................................................................................19TSCOR0010 ...........................................................................................................19TSCOR0011 ...........................................................................................................19TSCOR0012 ...........................................................................................................19TSCOR0013 ...........................................................................................................19TSCOR0014 ...........................................................................................................20TSCOR0019 ...........................................................................................................20TSCOR0024 ...........................................................................................................20TSCOR0025 ...........................................................................................................20TSCOR0026 ...........................................................................................................20TSCOR0030 ...........................................................................................................21TSCOR0031 ...........................................................................................................21TSCOR0033 ...........................................................................................................21TSCOR0034 ...........................................................................................................21TSCOR0035 ...........................................................................................................22TSCOR0036 ...........................................................................................................22TSCOR0037 ...........................................................................................................22TSCOR0040 ...........................................................................................................22TSCOR0041 ...........................................................................................................22TSCOR0042 ...........................................................................................................23TSCOR0043 ...........................................................................................................23TSCOR0044 ...........................................................................................................23TSCOR0045 ...........................................................................................................23TSCOR0046 ...........................................................................................................23TSCOR0047 ...........................................................................................................24TSCOR0048 ...........................................................................................................24TSCOR0049 ...........................................................................................................24TSCOR0050 ...........................................................................................................24TSCOR0051 ...........................................................................................................24TSCOR0052 ...........................................................................................................25TSCOR0054 ...........................................................................................................25TSCOR0055 ...........................................................................................................25TSCOR0056 ...........................................................................................................25TSCOR0057 ...........................................................................................................25TSCOR0058 ...........................................................................................................26TSCOR0059 ...........................................................................................................26TSCOR0060 ...........................................................................................................26TSCOR0061 ...........................................................................................................26TSCOR0062 ...........................................................................................................26TSCOR0063 ...........................................................................................................27TSCOR0064 ...........................................................................................................27

Contents | 3

TSCOR0065 ...........................................................................................................27TSCOR0067 ...........................................................................................................27TSCOR0068 ...........................................................................................................28TSCOR0069 ...........................................................................................................28TSCOR0070 ...........................................................................................................28TSCOR0071 ...........................................................................................................28TSCOR0072 ...........................................................................................................28TSCOR0073 ...........................................................................................................28TSCOR0074 ...........................................................................................................29TSCOR0076 ...........................................................................................................29TSCOR0077 ...........................................................................................................29TSCOR0078 ...........................................................................................................29TSCOR0079 ...........................................................................................................29TSCOR0080 ...........................................................................................................29TSCOR0081 ...........................................................................................................30TSCOR0084 ...........................................................................................................30TSCOR0085 ...........................................................................................................30TSCOR0087 ...........................................................................................................30TSCOR0089 ...........................................................................................................30TSCOR0090 ...........................................................................................................31TSCOR0091 ...........................................................................................................31TSCOR0092 ...........................................................................................................31TSCOR0093 ...........................................................................................................31TSCOR0094 ...........................................................................................................31TSCOR0095 ...........................................................................................................31TSCOR0096 ...........................................................................................................32TSCOR0097 ...........................................................................................................32TSCOR0099 ...........................................................................................................32TSCOR0100 ...........................................................................................................32TSCOR0102 ...........................................................................................................32TSCOR0104 ...........................................................................................................33TSCOR0105 ...........................................................................................................33TSCOR0107 ...........................................................................................................33TSCOR0108 ...........................................................................................................33TSCOR0109 ...........................................................................................................33TSCOR0110 ...........................................................................................................34TSCOR0111 ...........................................................................................................34TSCOR0112 ...........................................................................................................34TSCOR0113 ...........................................................................................................34TSCOR0114 ...........................................................................................................35TSCOR0115 ...........................................................................................................35TSCOR0116 ...........................................................................................................35TSCOR0117 ...........................................................................................................35TSCOR0118 ...........................................................................................................35TSCOR0119 ...........................................................................................................36TSCOR0121 ...........................................................................................................36TSCOR0122 ...........................................................................................................36TSCOR0123 ...........................................................................................................36TSCOR0124 ...........................................................................................................36TSCOR0125 ...........................................................................................................37TSCOR0126 ...........................................................................................................37TSCOR0127 ...........................................................................................................37TSCOR0128 ...........................................................................................................37TSCOR0129 ...........................................................................................................37TSCOR0130 ...........................................................................................................38TSCOR0131 ...........................................................................................................38

4 | Contents

TSCOR0132 ...........................................................................................................38TSCOR0133 ...........................................................................................................38TSCOR0134 ...........................................................................................................38TSCOR0136 ...........................................................................................................39TSCOR0137 ...........................................................................................................39TSCOR0138 ...........................................................................................................39TSCOR0139 ...........................................................................................................39TSCOR0140 ...........................................................................................................39TSCOR0141 ...........................................................................................................40TSCOR0142 ...........................................................................................................40TSCOR0143 ...........................................................................................................40TSCOR0144 ...........................................................................................................40TSCOR0145 ...........................................................................................................41TSCOR0146 ...........................................................................................................41TSCOR0147 ...........................................................................................................41TSCOR0148 ...........................................................................................................41TSCOR0149 ...........................................................................................................41TSCOR0150 ...........................................................................................................42TSCOR0151 ...........................................................................................................42TSCOR0152 ...........................................................................................................42TSCOR0153 ...........................................................................................................42TSCOR0154 ...........................................................................................................43TSCOR0155 ...........................................................................................................43TSCOR0156 ...........................................................................................................43TSCOR0157 ...........................................................................................................43TSCOR0158 ...........................................................................................................43TSCOR0159 ...........................................................................................................44TSCOR0160 ...........................................................................................................44TSCOR0161 ...........................................................................................................44TSCOR0163 ...........................................................................................................44TSCOR0164 ...........................................................................................................44TSCOR0165 ...........................................................................................................45TSCOR0166 ...........................................................................................................45TSCOR0167 ...........................................................................................................45TSCOR0168 ...........................................................................................................45TSCOR0170 ...........................................................................................................45TSCOR0171 ...........................................................................................................46TSCOR0172 ...........................................................................................................46TSCOR0173 ...........................................................................................................46TSCOR0174 ...........................................................................................................46TSCOR0175 ...........................................................................................................46TSCOR0176 ...........................................................................................................46TSCOR0177 ...........................................................................................................47TSCOR0178 ...........................................................................................................47TSCOR0179 ...........................................................................................................47TSCOR0180 ...........................................................................................................47TSCOR0181 ...........................................................................................................48TSCOR0182 ...........................................................................................................48TSCOR0183 ...........................................................................................................48TSCOR0184 ...........................................................................................................48TSCOR0185 ...........................................................................................................48TSCOR0186 ...........................................................................................................48TSCOR0187 ...........................................................................................................49TSCOR0188 ...........................................................................................................49

TAURUS for RDz (TSRDZ) messages .............................................................................. 49TSRDZ0001 ........................................................................................................... 49

Contents | 5

TSRDZ0002 ........................................................................................................... 49TSRDZ0003 ........................................................................................................... 50TSRDZ0004 ........................................................................................................... 50TSRDZ0005 ........................................................................................................... 50TSRDZ0006 ........................................................................................................... 50TSRDZ0007 ........................................................................................................... 50TSRDZ0008 ........................................................................................................... 50TSRDZ0009 ........................................................................................................... 51TSRDZ0010 ........................................................................................................... 51TSRDZ0011 ........................................................................................................... 51TSRDZ0012 ........................................................................................................... 51TSRDZ0013 ........................................................................................................... 52TSRDZ0014 ........................................................................................................... 52TSRDZ0015 ........................................................................................................... 52TSRDZ0016 ........................................................................................................... 52TSRDZ0017 ........................................................................................................... 52TSRDZ0018 ........................................................................................................... 52TSRDZ0019 ........................................................................................................... 52TSRDZ0020 ........................................................................................................... 53TSRDZ0021 ........................................................................................................... 53TSRDZ0022 ........................................................................................................... 53TSRDZ0023 ........................................................................................................... 53TSRDZ0024 ........................................................................................................... 53TSRDZ0025 ........................................................................................................... 53TSRDZ0026 ........................................................................................................... 54TSRDZ0027 ........................................................................................................... 54TSRDZ0032 ........................................................................................................... 54TSRDZ0033 ........................................................................................................... 54TSRDZ0034 ........................................................................................................... 54TSRDZ0035 ........................................................................................................... 54TSRDZ0036 ........................................................................................................... 55TSRDZ0038 ........................................................................................................... 55TSRDZ0040 ........................................................................................................... 55TSRDZ0041 ........................................................................................................... 55TSRDZ0042 ........................................................................................................... 55TSRDZ0046 ........................................................................................................... 55TSRDZ0047 ........................................................................................................... 56TSRDZ0048 ........................................................................................................... 56TSRDZ0049 ........................................................................................................... 56TSRDZ0053 ........................................................................................................... 56TSRDZ0054 ........................................................................................................... 56

TAURUS for z/Server (TSZSV) messages ........................................................................ 57TSZSV0001 ............................................................................................................57TSZSV0002 ............................................................................................................57TSZSV0003 ............................................................................................................57TSZSV0004 ............................................................................................................57TSZSV0005 ............................................................................................................57TSZSV0006 ............................................................................................................57TSZSV0007 ............................................................................................................58TSZSV0008 ............................................................................................................58TSZSV0009 ............................................................................................................58TSZSV0010 ............................................................................................................58TSZSV0011 ............................................................................................................58TSZSV0012 ............................................................................................................59TSZSV0013 ............................................................................................................59TSZSV0014 ............................................................................................................59

6 | Contents

TSZSV0015 ............................................................................................................59TSZSV0016 ............................................................................................................60TSZSV0017 ............................................................................................................60TSZSV0018 ............................................................................................................60TSZSV0019 ............................................................................................................60TSZSV0020 ............................................................................................................60TSZSV0021 ............................................................................................................61TSZSV0022 ............................................................................................................61TSZSV0023 ............................................................................................................61TSZSV0025 ............................................................................................................61TSZSV0026 ............................................................................................................61TSZSV0027 ............................................................................................................61TSZSV0028 ............................................................................................................61TSZSV0029 ............................................................................................................62TSZSV0030 ............................................................................................................62TSZSV0031 ............................................................................................................62

TAURUS edit macro (TSMAC) messages ......................................................................... 62TSMAC0001 ...........................................................................................................62TSMAC0002 ...........................................................................................................62TSMAC0003 ...........................................................................................................62TSMAC0004 ...........................................................................................................63

TAURUS meta model (TSMDL) messages ....................................................................... 63TSMDL0002 ........................................................................................................... 63

TAURUS meta model editor (TSMET) messages ............................................................. 63TSMET0001 ........................................................................................................... 63TSMET0002 ........................................................................................................... 63TSMET0003 ........................................................................................................... 63TSMET0004 ........................................................................................................... 64TSMET0006 ........................................................................................................... 64

TAURUS subsystem MVS (TSMVS) messages ................................................................ 64TSMVS0001 ........................................................................................................... 64TSMVS0002 ........................................................................................................... 64TSMVS0003 ........................................................................................................... 64TSMVS0005 ........................................................................................................... 65TSMVS0006 ........................................................................................................... 65TSMVS0007 ........................................................................................................... 65TSMVS0008 ........................................................................................................... 65TSMVS0009 ........................................................................................................... 66TSMVS0010 ........................................................................................................... 66TSMVS0011 ........................................................................................................... 66TSMVS0012 ........................................................................................................... 66TSMVS0013 ........................................................................................................... 67TSMVS0014 ........................................................................................................... 67TSMVS0015 ........................................................................................................... 67TSMVS0016 ........................................................................................................... 67TSMVS0023 ........................................................................................................... 67TSMVS0024 ........................................................................................................... 68TSMVS0025 ........................................................................................................... 68TSMVS0026 ........................................................................................................... 68

TAURUS user interface (TSUIN) messages ......................................................................68TSUIN0001 .............................................................................................................68TSUIN0002 .............................................................................................................69TSUIN0003 .............................................................................................................69TSUIN0004 .............................................................................................................69TSUIN0005 .............................................................................................................69TSUIN0006 .............................................................................................................69

Contents | 7

TSUIN0007 .............................................................................................................69TSUIN0008 .............................................................................................................69TSUIN0009 .............................................................................................................70TSUIN0010 .............................................................................................................70TSUIN0011 .............................................................................................................70TSUIN0012 .............................................................................................................70TSUIN0013 .............................................................................................................70TSUIN0014 .............................................................................................................70TSUIN0016 .............................................................................................................71TSUIN0017 .............................................................................................................71TSUIN0018 .............................................................................................................71TSUIN0019 .............................................................................................................71TSUIN0021 .............................................................................................................71TSUIN0024 .............................................................................................................72TSUIN0025 .............................................................................................................72TSUIN0026 .............................................................................................................72TSUIN0027 .............................................................................................................72TSUIN0028 .............................................................................................................72TSUIN0029 .............................................................................................................72TSUIN0030 .............................................................................................................73TSUIN0031 .............................................................................................................73TSUIN0032 .............................................................................................................73TSUIN0033 .............................................................................................................73TSUIN0034 .............................................................................................................73TSUIN0036 .............................................................................................................74TSUIN0037 .............................................................................................................74TSUIN0038 .............................................................................................................74TSUIN0039 .............................................................................................................74TSUIN0040 .............................................................................................................74TSUIN0041 .............................................................................................................74TSUIN0042 .............................................................................................................75TSUIN0043 .............................................................................................................75TSUIN0044 .............................................................................................................75TSUIN0045 .............................................................................................................75TSUIN0047 .............................................................................................................75TSUIN0048 .............................................................................................................76TSUIN0049 .............................................................................................................76TSUIN0050 .............................................................................................................76TSUIN0051 .............................................................................................................76TSUIN0052 .............................................................................................................76TSUIN0053 .............................................................................................................77TSUIN0054 .............................................................................................................77TSUIN0055 .............................................................................................................77TSUIN0057 .............................................................................................................77TSUIN0058 .............................................................................................................77TSUIN0059 .............................................................................................................77TSUIN0060 .............................................................................................................78TSUIN0061 .............................................................................................................78TSUIN0062 .............................................................................................................78TSUIN0063 .............................................................................................................78TSUIN0064 .............................................................................................................78TSUIN0066 .............................................................................................................79TSUIN0067 .............................................................................................................79TSUIN0068 .............................................................................................................79TSUIN0069 .............................................................................................................79TSUIN0070 .............................................................................................................79

8 | Contents

TSUIN0071 .............................................................................................................80TSUIN0072 .............................................................................................................80TSUIN0073 .............................................................................................................80TSUIN0074 .............................................................................................................80TSUIN0077 .............................................................................................................80TSUIN0078 .............................................................................................................81TSUIN0079 .............................................................................................................81TSUIN0081 .............................................................................................................81TSUIN0082 .............................................................................................................81TSUIN0084 .............................................................................................................81TSUIN0085 .............................................................................................................82TSUIN0086 .............................................................................................................82TSUIN0087 .............................................................................................................82TSUIN0088 .............................................................................................................82TSUIN0089 .............................................................................................................82TSUIN0090 .............................................................................................................82TSUIN0091 .............................................................................................................83TSUIN0092 .............................................................................................................83TSUIN0093 .............................................................................................................83TSUIN0094 .............................................................................................................83TSUIN0095 .............................................................................................................83TSUIN0096 .............................................................................................................83TSUIN0098 .............................................................................................................84TSUIN0099 .............................................................................................................84TSUIN0100 .............................................................................................................84TSUIN0101 .............................................................................................................84TSUIN0102 .............................................................................................................85TSUIN0103 .............................................................................................................85TSUIN0104 .............................................................................................................85TSUIN0105 .............................................................................................................85TSUIN0106 .............................................................................................................86TSUIN0107 .............................................................................................................86TSUIN0108 .............................................................................................................86TSUIN0109 .............................................................................................................86TSUIN0110 .............................................................................................................86TSUIN0111 .............................................................................................................87TSUIN0112 .............................................................................................................87TSUIN0113 .............................................................................................................87TSUIN0114 .............................................................................................................87TSUIN0115 .............................................................................................................88TSUIN0116 .............................................................................................................88TSUIN0117 .............................................................................................................88TSUIN0118 .............................................................................................................88TSUIN0119 .............................................................................................................89TSUIN0120 .............................................................................................................89TSUIN0121 .............................................................................................................89TSUIN0122 .............................................................................................................89

TAURUS user interface views (TSUIV) messages ............................................................ 89TSUIV0002 .............................................................................................................89TSUIV0003 .............................................................................................................90TSUIV0004 .............................................................................................................90TSUIV0005 .............................................................................................................90TSUIV0006 .............................................................................................................90TSUIV0008 .............................................................................................................91TSUIV0009 .............................................................................................................91TSUIV0010 .............................................................................................................91

Contents | 9

TSUIV0011 .............................................................................................................91TSUIV0012 .............................................................................................................91TSUIV0013 .............................................................................................................92

zExplorer for z/Server (TSXZS) messages ....................................................................... 92TSXZS0001 ............................................................................................................92TSXZS0002 ............................................................................................................92TSXZS0003 ............................................................................................................93TSXZS0004 ............................................................................................................93TSXZS0005 ............................................................................................................93TSXZS0006 ............................................................................................................93TSXZS0011 ............................................................................................................94TSXZS0012 ............................................................................................................94TSXZS0018 ............................................................................................................94TSXZS0022 ............................................................................................................94TSXZS0023 ............................................................................................................94TSXZS0025 ............................................................................................................94TSXZS0026 ............................................................................................................95TSXZS0027 ............................................................................................................95TSXZS0028 ............................................................................................................95TSXZS0029 ............................................................................................................95TSXZS0030 ............................................................................................................96TSXZS0031 ............................................................................................................96TSXZS0032 ............................................................................................................96TSXZS0033 ............................................................................................................96TSXZS0034 ............................................................................................................96TSXZS0035 ............................................................................................................97TSXZS0036 ............................................................................................................97TSXZS0037 ............................................................................................................97TSXZS0042 ............................................................................................................97TSXZS0043 ............................................................................................................97TSXZS0044 ............................................................................................................97

zExplorer subsystem JES (TSXJE) messages ................................................................. 97TSXJE0001 ............................................................................................................ 98TSXJE0002 ............................................................................................................ 98TSXJE0003 ............................................................................................................ 98TSXJE0004 ............................................................................................................ 98TSXJE0005 ............................................................................................................ 98TSXJE0006 ............................................................................................................ 98TSXJE0007 ............................................................................................................ 98TSXJE0008 ............................................................................................................ 99TSXJE0009 ............................................................................................................ 99TSXJE0010 ............................................................................................................ 99TSXJE0011 ............................................................................................................ 99

zExplorer subsystem MVS (TSXMV) messages ...............................................................99TSXMV0001 ........................................................................................................... 99TSXMV0002 ........................................................................................................... 99TSXMV0003 ......................................................................................................... 100TSXMV0004 ......................................................................................................... 100TSXMV0005 ......................................................................................................... 100TSXMV0007 ......................................................................................................... 100TSXMV0008 ......................................................................................................... 100TSXMV0009 ......................................................................................................... 100TSXMV0010 ......................................................................................................... 101TSXMV0011 ......................................................................................................... 101TSXMV0012 ......................................................................................................... 101TSXMV0013 ......................................................................................................... 101

10 | Contents

TSXMV0014 ......................................................................................................... 101TSXMV0015 ......................................................................................................... 102TSXMV0018 ......................................................................................................... 102TSXMV0019 ......................................................................................................... 102TSXMV0020 ......................................................................................................... 102TSXMV0021 ......................................................................................................... 102TSXMV0022 ......................................................................................................... 102TSXMV0023 ......................................................................................................... 103TSXMV0024 ......................................................................................................... 103TSXMV0025 ......................................................................................................... 103TSXMV0026 ......................................................................................................... 103TSXMV0027 ......................................................................................................... 103TSXMV0029 ......................................................................................................... 103TSXMV0030 ......................................................................................................... 103TSXMV0031 ......................................................................................................... 104TSXMV0032 ......................................................................................................... 104TSXMV0035 ......................................................................................................... 104TSXMV0036 ......................................................................................................... 104TSXMV0037 ......................................................................................................... 104TSXMV0038 ......................................................................................................... 104TSXMV0040 ......................................................................................................... 104TSXMV0041 ......................................................................................................... 105TSXMV0042 ......................................................................................................... 105TSXMV0043 ......................................................................................................... 105TSXMV0044 ......................................................................................................... 105TSXMV0045 ......................................................................................................... 106TSXMV0046 ......................................................................................................... 106TSXMV0047 ......................................................................................................... 106TSXMV0048 ......................................................................................................... 106TSXMV0049 ......................................................................................................... 106TSXMV0050 ......................................................................................................... 106TSXMV0051 ......................................................................................................... 106TSXMV0052 ......................................................................................................... 107TSXMV0054 ......................................................................................................... 107TSXMV0055 ......................................................................................................... 107TSXMV0056 ......................................................................................................... 107TSXMV0057 ......................................................................................................... 107TSXMV0058 ......................................................................................................... 107TSXMV0059 ......................................................................................................... 107TSXMV0060 ......................................................................................................... 108TSXMV0061 ......................................................................................................... 108TSXMV0062 ......................................................................................................... 108TSXMV0063 ......................................................................................................... 108TSXMV0064 ......................................................................................................... 108TSXMV0065 ......................................................................................................... 108TSXMV0066 ......................................................................................................... 108TSXMV0067 ......................................................................................................... 109TSXMV0068 ......................................................................................................... 109TSXMV0069 ......................................................................................................... 109TSXMV0070 ......................................................................................................... 109TSXMV0071 ......................................................................................................... 109TSXMV0072 ......................................................................................................... 109TSXMV0073 ......................................................................................................... 109TSXMV0074 ......................................................................................................... 110TSXMV0075 ......................................................................................................... 110TSXMV0076 ......................................................................................................... 110

Contents | 11

z/Server communicator (SOZCM) messages ................................................................. 110SOZCM0001 ........................................................................................................ 110SOZCM0002 ........................................................................................................ 110SOZCM0003 ........................................................................................................ 111SOZCM0004 ........................................................................................................ 111SOZCM0005 ........................................................................................................ 111SOZCM0006 ........................................................................................................ 111SOZCM0007 ........................................................................................................ 111SOZCM0008 ........................................................................................................ 111SOZCM0009 ........................................................................................................ 111SOZCM0010 ........................................................................................................ 112SOZCM0011 ........................................................................................................ 112SOZCM0012 ........................................................................................................ 112SOZCM0013 ........................................................................................................ 112SOZCM0014 ........................................................................................................ 112SOZCM0015 ........................................................................................................ 112SOZCM0016 ........................................................................................................ 112SOZCM0017 ........................................................................................................ 112SOZCM0018 ........................................................................................................ 113SOZCM0019 ........................................................................................................ 113SOZCM0020 ........................................................................................................ 113SOZCM0021 ........................................................................................................ 113SOZCM0022 ........................................................................................................ 113SOZCM0023 ........................................................................................................ 113SOZCM0024 ........................................................................................................ 113SOZCM0025 ........................................................................................................ 113SOZCM0026 ........................................................................................................ 113SOZCM0027 ........................................................................................................ 114SOZCM0028 ........................................................................................................ 114SOZCM0029 ........................................................................................................ 114

z/Server ISPF panel support (TSIPS) messages ............................................................114TSIPS0001 ........................................................................................................... 114TSIPS0002 ........................................................................................................... 114TSIPS0003 ........................................................................................................... 115TSIPS0004 ........................................................................................................... 115TSIPS0005 ........................................................................................................... 115TSIPS0006 ........................................................................................................... 115TSIPS0007 ........................................................................................................... 115TSIPS0008 ........................................................................................................... 115TSIPS0009 ........................................................................................................... 116TSIPS0010 ........................................................................................................... 116TSIPS0011 ........................................................................................................... 116TSIPS0012 ........................................................................................................... 116TSIPS0015 ........................................................................................................... 116TSIPS0016 ........................................................................................................... 116TSIPS0017 ........................................................................................................... 117TSIPS0018 ........................................................................................................... 117TSIPS0019 ........................................................................................................... 117TSIPS0020 ........................................................................................................... 117TSIPS0021 ........................................................................................................... 117

z/Server meta model (SOMDL) messages ..................................................................... 118SOMDL0001 Invalid License Checker extension. The referenced class is incompatible with ILicenseChecker: {0}

............................................................................................................................. 118Troubleshooting ............................................................................................. 119

General Problem Determination ......................................................................................119Determine the original exception ..........................................................................120

12 | Contents

Clear the persistent cache in the workspace ........................................................120Deal with code page problems ............................................................................. 120Workspace out of sync ......................................................................................... 121

z/Explorer Problem Determination .................................................................................. 121Determine the original exception ..........................................................................121Clear the persistent cache in the workspace ........................................................121Deal with code page problems ............................................................................. 122Workspace out of sync ......................................................................................... 122

Application Workflow Manager Problem Determination .................................................122Modeled Action does not work ............................................................................. 123Element List is not created ................................................................................... 124Tree View is not expandable .................................................................................124Tree View Elements do not have a correct label .................................................. 124Edit Action (Simple Remote Edit or Browse) does not work properly ................. 124

General Problem Solving Suggestions ........................................................................... 125Determine the original exception ..........................................................................125Clear the persistent cache in the workspace ........................................................125Deal with code page problems ............................................................................. 126Workspace out of sync ......................................................................................... 126

Gathering information for Micro Focus SupportLine ....................................................... 126Sample error situations ................................................................................. 129

z/Server is not active ......................................................................................................129Connection to z/Server is interrupted ..............................................................................129Connection problem when connection is active .............................................................. 130No RACF OMVS segment .............................................................................................. 130Model error: wrong Program ID .......................................................................................131Model error: wrong Panel Name ..................................................................................... 131Error situations in an attached tool ..................................................................................132

Known issues ................................................................................................. 135

Contents | 13

IntroductionThis guide is meant as a help for error situations that can be traced back to the Workflow Manager.

Generally, we distinguish between expected and unexpected error situations. For example, an expectederror situation would be one when the user enters an incorrect connection password.

Unexpected error situations can further be grouped into situations that were foreseen by the software andthose that were not. For example, a foreseen error situation would be that the connection to the remotesystem is broken, and an example of an unforeseen error situation would be a programming error in thesoftware.

Depending on the type of error, the user or system administrator has different sources for help to deal withthe situation.

For expected and unexpected but foreseen error situations, an error dialog in the Eclipse Workbench isdisplayed. For example:

The information in the dialog box should enable a user to handle this type of problem.

If the error was reported by the underlying z/Server software, a z/Server message ID is displayed in thedialog (in the example above this would be SLR0071E). The first three alphabetic characters of themessage ID define the z/Server facility that detected the error. The facility’s acronym is followed by fourdigits which represent the sequential message number within the messages for this z/Server facility. A z/Server message ID ends with a character stating the severity of the message (I: informational, W: warning,E: error, S: severe error).

In some situations, the XML error message is returned in the original XML format, for example:

14 | Introduction

The values of the XML tags FACID, MSGNO and SEVERITY have to be concatenated to give the z/Servermessage ID, in this case SLR0131E.

The mapping between message prefix and z/Server facility is as follows:

Message Prefix z/Server Facility

API Application programming interface (TCPIP)

BND IEWBND (Binder) interface

CSI Catalog search interface

DSC Holder task configuration

EMC Extended MCS interface

HLD Holder task interface

IPC Command task

JES Job entry subsystem interface

LIC License interface

MAL Email interface

REC Recovery exception handler

REX REXX command environment

SJB Started job interface

SLR TSO scheduler interface

SPR Standard pool routine

SRV Server interface

SSI Interface to z/OS SSI

STA Started task interface

TAU Eclipse client interface

UNI Unicode conversion services

XML XML system parser interface

Detailed information about z/Server messages and how to handle them can be found in z/ServerMessages and Diagnostics.

For unexpected but foreseen error situations, the exception caught is displayed in the text area shownwhen the Details >> button is pressed.

Introduction | 15

The exception type often gives a hint as to what caused the problem. In the example above, there is somekind of network connection problem, which could for example mean that the connection to the network wasinterrupted or that z/Server is not up and running.

If the information found in the error dialog is not sufficient to solve the problem, view the error log for furtherinformation. See Troubleshooting for details on how to access the error log, how to enrich it with debuginformation, and how to send that information to Micro Focus SupportLine.

Unexpected and unforeseen error situations will not normally produce an error dialog, but in some cases,information related to a software exception not caught is recorded in the error log.

Error messages lists all messages and describes the user, workflow modeler or server administratorresponse.

Troubleshooting contains instructions for the Application Workflow Modeler (the administrator) on how tofind the cause of problems that may stem from Application Workflow Modeler, and offers solutions. It alsodescribes the information that Micro Focus SupportLine needs when the Application Workflow Modelercannot solve the problem.

Sample error situations is designed for support engineers to become accustomed to the way the softwarereacts during selected error situations.

Known issues shows currently known software errors, including tips on how to deal with them.

16 | Introduction

Error messagesThe following user roles are used in this documentation:

User Person who works with the Application Workflow Manager (AWM) software.

Model administrator Person who maintains the Application Workflow model and develops tools for it.

Server administrator Person who administers the server which provides the services requested by theApplication Workflow Manager client.

Error messages have an ID consisting of nine alphanumeric characters. The first five alphabetic charactersdetermine the internal package in which the error has arisen. The following four digits represent asequential numbering of the messages within the corresponding package.

Numbers in curly brackets within the message text represent placeholders, which are substituted byvariables during execution time, e.g. {0}.

Failed to read the parameter file {0} .

TAURUS core (TSCOR) messages

TSCOR0001 An error occurred during execution of tool{0} or reading its output.This exception can occur if a "job after action" encounters a problem while reading the tool output from theexecuted job. This is a top-level exception which usually contains more information in the error details.

User Response: Refresh the Job View to see if the corresponding job still exists. If it disappearsafter refreshing, the tool output has probably been deleted already.

Model AdministratorResponse:

• Verify that the executed tool returns correct output.• Verify that the tool output has been created properly (done by the REXX

procedure TAUTOIFA).

TSCOR0002 Failed to read the parameter file {0} .This exception can occur if a "job after action" fails to read the tool output from the executed job.

User Response: Refresh the Job View to see if the corresponding job still exists. If it disappearsafter refreshing, the tool output has probably been deleted already.


Verify that the tool output has been created properly (done by the REXXprocedure TAUTOIFA).

TSCOR0003 Error during execution of tool {0} .This is a top-level exception that occurs if any executed tool (defined by a Tool Descriptor) encounters aproblem. A more detailed message can usually be found in the error details (usually a message created bythe executed tool). Possible causes:

• An individual error message was created by the executed tool. This depends on the tool type.

Error messages | 17

• An integrated tool encountered a problem.• The modeled tool type could not be resolved.• An executed tool did not return a valid tool execution status.


Solve the cause of the exception if a detailed message can be found in theerror details. If necessary contact SupportLine.

TSCOR0004 The tool {0} exceeded the maximum returncode of {1} .This is a very common top-level exception. It occurs if any modeled tool returns a return code which ishigher than the modeled "Max_RC", which is an attribute of the "Application Options" ("4" by default). A toolwhich returned a high return code most probably also returned a reason message. The reason messageshould be visible under "Reason" in the error dialog or can be found in the error details.

User Response: Contact the model administrator if the reason given by the executed tool is not clear orif there is no reason message at all.

TSCOR0005 Failed to create the elementlist {0} .An Action Descriptor with a reference to an Element List Structure (attribute "Has_Elementlist") wasexecuted but the creation of the Element list failed. This is a top-level exception, and a more detailedmessage can usually be found in the error details. Possible causes:

• The action was not intended to create an Element list.• The Element list cache cannot be saved in the workspace.• Modeling errors.

ModelAdministratorResponse:

• If no Element list should be created by the corresponding action, remove thevalue of the "Has_Elementlist" attribute from the Action Descriptor.

• See Element List is Not Created to fix possible model problems.

TSCOR0007 A resource with the logical name {0} wasnot found.An "Action Descriptor has Tool" relationship was defined with an "Affected_Resource" name, but nopreviously executed tool returned a logical resource name within a tool-defined resource operation.


• Correct the affected resource name in the "Action Descriptor has Tool"relationship or in the output of the executed tool. Remove the attribute from therelationship if it was not intended to be used.

• Verify that a tool which returns the logical resource name is executed before thetool which returns the error message.

TSCOR0008 A tool type is missing for tool descriptor{0} .A tool descriptor was defined without a "Tool_Type" attribute.


Define a "Tool_Type" or "Integrated_Tool" attribute for the correspondingtool descriptor.

18 | Error messages

TSCOR0009 The tool {0} did not return a tool executionstatus.An executed tool did not return a "Tool Execution Status" which is a Java class that belongs to the API.


If a tool was executed by a custom-created tool executor by using the productAPI, contact the corresponding programmer. If necessary, contact SupportLine.

TSCOR0010 Tool Descriptor {0} needs an ISAPlugInattribute, because its tool-type attribute was set to {1} .A tool descriptor was modeled with a certain tool type which requires an "ISA_Plug-In" attribute but it ismissing. This is a modeling error.


Add an "ISA_Plug-In" attribute to the tool descriptor ("New Child" -> "ISA Plug-In")and define the missing attributes. Example: If an input dialog was modeled (tooltype "SWTDIALOG") you must specify a plug-in ID in the ISA Plug-In attribute.

TSCOR0011 A bundle (Plug-In) with the ID {0} was notfound.A tool descriptor was modeled with an "ISA_Plug-In" attribute where a certain plug-in ID was defined butno plug-in with the specified ID was found. Either the plug-in ID is not correct or the plug-in is not installedin the Eclipse environment.


Correct the plug-in ID in the "ISA_Plug-In" attribute of the tool descriptor or installthe required plug-in. The "Plug-In Registry" Eclipse View is useful to find installedplug-ins.

TSCOR0012 Activator for Plug-In {0} not found.A tool descriptor was modeled with the tool type "PLUGIN" but the referenced plug-in does not have anactivator. This problem can only occur if additional plug-ins were implemented by using the product API.


Declare the class which implements the "IToolExecutor" interface to be theactivator of the plug-in.

TSCOR0013 No extension was found for the tool-type{0} .The tool type of a modeled tool descriptor could not be resolved. Either the "Tool_Type" attribute of the tooldescriptor is incorrect or the plug-in which can execute the specified tool type is not installed properly.


Correct the "Tool_Type" attribute of the corresponding tool descriptor or installthe required plug-in which contains a tool executor for the specified tool type.

Error messages | 19

TSCOR0014 Tool {0} returns fewer parameters thanexpected. {1} parameters were parsed while {2}parameters were specified for this tool!The number of parameters an executed tool returned was lower than the number of output parametersmodeled in its corresponding tool descriptor.


• Remove output parameters from the tool descriptor or let the tool return fewervalues.

• If the number of returned values seems to be correct, verify that the outputparameter separator does not occur within the output values. Change theseparator if necessary.

TSCOR0019 The FileDescriptor parameter pFDSourcemust not be null.The input file parameter for a tool creating a temporary file (remote edit, remote browse...) could not befound. This can be caused by a modeling error or incorrect usage of the API.


If the problem is caused by a modeled integrated tool, verify that the inputparameters are correctly modeled.

TSCOR0024 Failed to execute local syntax checkbecause the element cannot be determined.A local syntax check could not be performed because no element was found within the execution context ofthe action.


Verify that actions containing a local syntax check integrated tool can only beexecuted on elements (no global actions).

TSCOR0025 Failed to execute local syntax check.There may be no property group associated with theelement.A local syntax check failed because no property with the attribute "Special_Property = Property_Group"was associated with the selected element.


Verify that a property with the attribute "Special_Property" set to"Property_Group" is defined and associated with the corresponding elementtype.

TSCOR0026 The local syntax check could not beperformed because a local copy of the element was notfound.A local syntax check can only be perfomed if a local copy of an element exists. The local copy must becreated by the integrated tool "LocalFileCreator".

20 | Error messages

User Response: If a local copy of the element must be created in a separate action (e.g. a modeled"Check-Out" action), execute the action and retry the local syntax check. If you areworking with different workspaces, verify that the local copy was not created in adifferent workspace.


Define the integrated tool "LocalFileCreator" in the model and verify that the localsyntax check cannot be executed without the local file creator running beforehand.

TSCOR0030 Failed to receive an element with ID {0} .An error occurred trying to get an element with its ID due to:

• The internal application folder not being found or created, or being out of synchronisation.• The element XML file being damaged or not being able to be parsed.

User Response: • Refresh the internal project folder.• Restart the client.• Clear the element and elementlist cache.

TSCOR0031 Failed to load a cached element list.An error occurred when parsing the XML file containing the elementlist. Therefore an element could not bedetermined with its ID.

• The internal application folder cannot be found or created or is out of synchronisation.• The element XML file is damaged or cannot be parsed.

User Response: • Refresh the internal project folder.• Restart the client.• Clear the element and elementlist cache.

TSCOR0033 Failed to determine element types forElementlist creation. {0}{1}When trying to fill the element list, its element types could not be determined in the file descriptorproperties.


Verify that the element types are configured under the properties of the filedescriptor that creates the element list.

TSCOR0034 Failed to generate an element ID forelement type {0} . Available properties: {1}{2}When filling the element list, an element ID could not be generated.


Ensure that all the ID definitions and element type properties are returnedfrom the file descriptor that creates the element list.

Error messages | 21

TSCOR0035 The element type {0} is not defined in themodel.When trying to fill the element list, an element type could not be determined.


• Verify that the element types are configured under the file descriptionproperties.

• Ensure that the element list file returns the element type at the correctposition.

TSCOR0036 Failed to determine an element type.Empty set of properties was given.This is a client code error.

User Response: Contact SupportLine.

TSCOR0037 Failed to load a cached filter.The cached filters in the XML file cannot be read or the application folder is asynchronous.

User Response: • Refresh the internal application folder.• Restart the client.• Clear the filter cache.

TSCOR0040 Failed to get file contents for job submit.File: {0}The integrated tool "SubmitJCL" could not submit a job because the input JCL which is passed by a filedescriptor could not be read. The file path that was used is returned at the end of this message.


• Verify why the file was not found under the given path or could not be read.• If the submit tool was modeled within an editor action (global action), remove the

file input parameter from the corresponding tool descriptor. This will cause the toolto use the editor's contents as JCL input.

• See Troubleshooting if the returned path appears to be empty.

TSCOR0041 Failed to retrieve a data stream for the jobsubmit. Either a file input parameter was notconfigured, or a valid editor was not opened in theforeground.No JCL input was found, to submit a job.


Define the integrated tool "SubmitJCL" in one of two ways:

• Model a file input parameter which defines the JCL that should be submitted.

22 | Error messages

• Define an editor action (global action) for the submit action. The job can then besubmitted from an opened editor containing JCL.

TSCOR0042 Could not perform error feedback. Thecorresponding element could not be retrieved.The integrated tool "ErrorFeedback" was executed without an element in the execution context. This canoccur if the tool is modeled within a global action.


Ensure that the integrated tool "ErrorFeedback" is not used in a global action.Model "Element Type has Action" relationships as an alternative.

TSCOR0043 Invalid configuration of integrated toolRefreshDependencies: The integrated tool needs 2 fileinput parameters. 1) Error Feedback XML. 2)Copybooks XML.The integrated tool "RefreshDependencies" was not modeled properly. Two file input parameters arerequired.


Ensure that two file input parameters are modeled properly. The first referencedfile must contain compile errors and the second must contain all requiredcopybook entries.

TSCOR0044 Context missing for execution ofintegrated tool RefreshDependencies.This is an internal client error that occurred during execution of the integrated tool "RefreshDependencies".

Model Administrator Response: Contact SupportLine.

TSCOR0045 Element missing for execution ofintegrated tool RefreshDependencies.This is an internal client error that occurred during execution of the integrated tool "RefreshDependencies".


TSCOR0046 Failed to refresh dependencies because alocal copy of the element was not found.The "RefreshDependencies" tool can only be executed successfully if a local copy of an element exists.The local copy must be created by the integrated tool "LocalFileCreator".

User Response: If a local copy of the element must be created in a separate action (e.g. a modeled"Check-Out" action), execute and retry the action. If you are working with differentworkspaces, verify that the local copy was not created in a different workspace.

Error messages | 23


Define the integrated tool "LocalFileCreator" in the model and verify that the"RefreshDependencies" tool cannot be executed without the local file creatorrunning beforehand.

TSCOR0047 The configuration of integrated tool {0}must contain a file output parameter.The integrated tool "LocalTempFileCreator" was not properly modeled. It requires a file output parameterwhich will be used to set the name of the created file for other tools to use.


Add a file output parameter to the tool descriptor of the integrated tool"LocalTempFileCreator".

TSCOR0048 Property sets are not supported by thisproduct variant.Property sets are currently only supported in combination with other products and reserved for future use.


Contact SupportLine for more information about property sets and futureplans.

TSCOR0049 At least three input parameters must bedefined for the Integrated Tool Property Group Creator:{0} 1) Property Set Name{0} 2) Language{0} 3) SYSLIBPathThe integrated tool "PropertySetCreator" was not properly modeled (parameters missing). It requires atleast three input parameters: 1. Property Set name 2. Programming language 3. Library path


Correct any modeling errors concerning the tool descriptor for the integrated tool"PropertySetCreator". Valid parameter options are documented in theAdministration Guide.

TSCOR0050 {0} resource operation failed due to anexception.This is a top-level exception that will be printed into the error log if any exception occurs during a resourceoperation. A more detailed error message can usually be found in the error details.

Model Administrator Response: Check the error details for more information.

TSCOR0051 The input file descriptor must have thetype MVSPO_MEMBER,MVSSEQ or WORKSPACE_FILEThe integrated tool "PropertySetAssociator" was not properly modeled. The "Type" attribute of the FileDescriptor which is referenced by a file input parameter must have one of the following values:

• MVS_PO_Member• MVS_SEQ

24 | Error messages

• Workspace_File


Change the "Type" attribute of the referenced file descriptor to one of thesupported values (see description).

TSCOR0052 At least two input parameters must bedefined for the Integrated Tool Property GroupAssociator: {0} 1) Property Set Name{0} 2) (File) DataSet / MemberThe integrated tool "PropertySetAssociator" was not properly modeled (missing parameters).


Correct any modeling errors concerning the tool descriptor for the"PropertySetAssociator" integrated tool. Valid parameter options aredocumented in the Administration Guide.

TSCOR0054 At least one input parameter must bespecified for the Integrated Tool Property GroupRemover.The integrated tool "PropertySetRemover" was not properly modeled (parameter missing).


Correct any modeling errors concerning the tool descriptor for the"PropertySetRemover" integrated tool. Valid parameter options are documentedin the Administration Guide.

TSCOR0055 The parameter {0} does not have aboolean value: {1} .An integrated tool descriptor was modeled with a boolean input parameter but the parameter value was notboolean.


Correct the parameter value or change the attributes "True_value" and"False_value" of the corresponding property.

TSCOR0056 Invalid master configuration formatparameter: {0} .This is an internal error. It occurs when the master configuration reader is called with an invalid formatparameter.


TSCOR0057 Failed to parse a system from the givenmaster configuration file: {0}{1} .The given master configuration (printed at the end of this message) was invalid.

Error messages | 25


• Validate your master configuration and correct any errors. The syntax isdocumented in the Administration Guide.

• If another error message, rather than the master configuration, is printed at theend of the message, correct any errors that prevent the master configurationfrom being returned.

TSCOR0058 Internal master configuration parser error.The line {0} does not contain the {1} -tag.This error is caused if a line in a master configuration in FLAT format does not contain an expectedkeyword.

Model Administrator Response: Correct the corresponding line in the master configuration.

TSCOR0059 Exception occurred while executing OScommand: {0} .This is a top-level message which covers several exceptions that can occur while an operating systemcommand is executed:

• Operating system error messages (e.g. "Invalid command 'XYZ'").• I/O exceptions while sending the command or reading the output.


• Enable the client trace and verify that the sent commands are valid.• Check the error details and fix any operating system-dependent problems.

TSCOR0060 Failed to parse the return code {0} .The return code of the executed tool did not contain a valid numeric value.

Model Administrator Response: Correct the return code output in the called tool.

TSCOR0061 Tool {0} returns fewer parameters thanexpected. {1} parameters were detected whereas {2}parameters were specified for this tool.An executed tool returned fewer parameters than modeled output parameters in the corresponding tooldescriptor.


Either correct the tool output or the tool descriptor definition in the model so thatthe modeled output parameters match the actual tool output.

TSCOR0062 UPDATE resource operation failed. NoProperties found for updating.The UPDATE resource operation failed because no property values were returned by the correspondingtool. If no property values are returned, there is nothing to update.

26 | Error messages


• If the "Resource_Processing" attribute of the tool descriptor was set to UPDATEverify that the called tool returns the values that should be updated and that the tooldescriptor has modeled output parameters matching those values.

• If the "Resource_Processing" attribute of the tool descriptor was set toTOOL_DEFINED, verify that the output parameters with the type "Element" aremodeled.

• If the tool was not intended to update properties, change the"Resource_Processing" attribute of the tool descriptor to READ.

TSCOR0063 Failed to determine a target element listfor INSERT operation.An INSERT resource operation could not be executed because no element list was found in the executioncontext. This can be caused by the tool being executed from a global action.


If the corresponding tool descriptor is referenced by a global action but also anElement-/Elementlist action, create a copy of the tool descriptor, set the"Resource_Processing" attribute of the copy to READ and use it for global actions.

TSCOR0064 INSERT operation failed. No element typecould be determined for the new element.This is caused either a property with the "Special_Property" attribute set to "Element_Type" was notreturned by the INSERT tool or an element was not selected when the action was executed.


Return the match name of the element type in the INSERT tool and model it asan output parameter referencing an "Element_Type" property.

TSCOR0065 INSERT-CHILD operation failed. Selectedresource does not have a children-list or -action.An INSERT-CHILD resource operation could not be executed because no child element can be associatedwith the selected element. Child elements can only be added for element types that have an associated"Get_Children" action descriptor.


Verify that the INSERT-CHILD tool descriptor can only be executed on elementtypes which have a "Get_Children" action associated.

TSCOR0067 Failed to restore the system reference {0}because the remote system {1} was not found.A system reference which is associated with a remote system could not be restored, because theassociated remote system could not be determined.

UserResponse:

• Verify that the associated remote system still exists and has not been renamed inthe Remote System View.

• Delete the system reference and let it be re-created by connecting to the remotesystem.

Error messages | 27

TSCOR0068 Failed to load the application.An exception occurred when loading an application from the local copy. The local copy of the application isprobably corrupted.

User Response: Open the application file from the internal project folder with the model editor andvalidate it. If it is corrupted, remove it from the internal project folder. Then theapplication model will be loaded from the remote system again. If necessary,contact the model administrator.


Contact SupportLine.

TSCOR0069 Invalid extension for extension point {0}The zOS functionality is integrated by the Eclipse extension point de.soforte.taurus.zconnector. Anexception occurred when searching for an extension for this Eclipse extension point.


TSCOR0070 No ZConnector Extension was found.The zOS functionality is integrated by the Eclipse extension point de.soforte.taurus.zconnector. No plug-inwhich extends this extension point could be found in the workbench.


If the extension point de.soforte.taurus.zconnector is extended by a customer'sown extension, verify that the extension point name is spelled correctly in theplugin.xml. Otherwise contact SupportLine.

TSCOR0071 Cannot write on file descriptor of typeInputStream.The setContents method was called with a parameter of type input stream. It is not possible to write on aninput stream.


Verify your tool output parameters of type file descriptor. The type of a filedescriptor that is a tool output parameter may not be of type "InputStream".

TSCOR0072 The file {0} does not exist.The file specified by the given path could not be found.


If the file path originates from a modeled file descriptor, verify that the value underthe attribute "Name Physical" is correct. If the file path is a tool result, verify thatthe tool returns the correct file path.

TSCOR0073 {0} is not a valid format for a masterconfiguration parser.{1}The function to parse a master configuration file is integrated by an Eclipse extension point. The parserwas initialized with an invalid file format. Supported file formats are XML or flat file.

28 | Error messages


If the master configuration parser is implemented by a customer's own plug-in,verify that the parser is initialized by one of the valid file formats. Otherwisecontact SupportLine.

TSCOR0074 A newer workflow model version isavailable. {0} The application will now be updated.The model administrator has delivered a newer model version of the application than the version which isloaded locally in the user's workspace. This is a message informing the user that the newer version of themodel is loaded in the workspace.

User Response: This is an informational message; no user action necessary.

TSCOR0076 Pre-init failed.An internal plug-in initialization error occurred.


TSCOR0077 System name missing.The creation of a system reference failed because no name for the system was given.

User Response: Verify that a name was specified under the field "Connection name" in the NewConnection dialog.

TSCOR0078 ISystemImage missing.An internal exception occurred because no instance of the ISystemImage type was passed to the method.


TSCOR0079 The resource with the ID {0} could not befound.The persistent cache in the user's workspace seems to be inconsistent. There is a reference in one of thecache files to a resource which has not been reloaded from the element's cache file.

User Response: Use the "Clear cache..." dialog to re-initialize the persistent cache in the Eclipseworkspace.

TSCOR0080 Failed to create an ID for element type {0} .The key property {1} is missing.The creation of an internal AWM element failed because at least one of the configured key properties of theelement's element type could not be determined.


• Verify that the corresponding file descriptor is modeled correctly. The filedescriptor must contain all key properties of the returned element type as aminimum.

Error messages | 29

• Verify that the corresponding tool correctly returns values for all modeled keyproperties.

TSCOR0081 Missing property value ( {0} ) for resourceoperation.The creation of an internal AWM element ID failed because no property value was provided for at least oneof the configured key properties of the element's element type.


• Verify that the corresponding file descriptor is modeled correctly. The filedescriptor must contain all key properties of the returned element type as aminimum.

• Verify that the corresponding tool correctly returns values for all modeled keyproperties.

TSCOR0084 No valid extension found for the localsyntax check extension point.The integrated "Local Syntax Check" tool is not supported by the product variant.


TSCOR0085 No valid extension found for the propertygroup manager extension pointThis is an internal program exception. The "Property Group Manager" interface did not find a validimplementation.


TSCOR0087 No valid extension found for the errorfeedback parser extension pointThis is an internal program exception. The "Error Feedback" interface did not find a valid implementation.


TSCOR0089 An I/O error occurred while reading a fileinput stream.An exception occurred during the attempt to read and parse a tool response. Possible reasons are:

• Network problems.• Invalid API usage by third party plug-ins.• An internal program exception.

User Response: Check your network connection.


30 | Error messages

TSCOR0090 An error occurred while creating/openingthe Eclipse project {0} .The internal project could not be created/opened because the project/workspace is damaged.

User Response: If the project is already created, refresh it. If this does not solve the problem, close yourworkbench and try again or clear your workspace.

TSCOR0091 Failed to create the internal systems folderin the workspace.The system folder could not be created in the internal project because the project/workspace is damaged.


TSCOR0092 Failed to create the internal project folderin the workspace.The application folder could not be created in the internal project because the project/workspace isdamaged.


TSCOR0093 Error when parsing input for table. Valuefor property {0} not found.There is a file input parameter declared as input for a dialog table. At least one line of the file content doesnot deliver a value for every property associated with the file descriptor.


Verify the output file of the tool delivering the content for the dialog table. Ensurethat the tool delivers at least as many values as properties are configured for thefile descriptor.

TSCOR0094 File {0} does not exist.The local file with the given path could not be found on the user's workspace.


• If the file's path was derived from a file descriptor in the model, verify that thevalue in the attribute "Name_Physical" is correct.

• If the file path is returned by a modeled tool, verify that the tool returns thecorrect path name.

TSCOR0095 The file {0} does not exist.No file was found based on a File Descriptor with the attribute "Type" set to "Workspace_File". Typicalreasons are:

• The file is not located in the workspace ("Type" attribute is incorrect).

Error messages | 31

• The "Name_Physical" attribute value was not entered correctly.• The file path is returned incorrectly by another tool.• The file path is correct but the file simply does not exist.

Model Administrator Response: Correct any errors that might cause the problem.

TSCOR0096 The master configuration file was notfound. It must either be located in: {0}{1} .xml or {2} .txtor a master configuration provider must beimplemented (Eclipse Extension Point).This is an internal program exception that can be caused by an attempt to read a local master configurationfile which cannot be located.


TSCOR0097 Invalid argument. Element type must notbe null.The element type of an element could not be resolved by filling the element list or by performing a resourceprocessing "tool defined " (insert, update).


• Verify that the element types of the element list are configured in the properties ofthe file descriptor that creates the element list.

• Verify that the tool descriptors ('TOOL_DEFINED' Resource Processing) thatinsert/update elements with new element types have an element type outputparameter (Property with element type as special parameter).

TSCOR0099 Wrong parameters for integrated toolFileUploader. Two file input parameters were expected.The integrated tool "FileUploader" was not modeled properly. It requires two file input parameters.


Verify that two file input parameters are modeled for the "FileUploader" tooldescriptor. The first one will be used as the source file while the second one will bethe target for the transfer operation.

TSCOR0100 Failed to create the temp file. Inputparameters missing.The integrated tool "LocalTempFileCreator" was not properly modeled (input parameters missing).


Correct the modeling errors concerning the tool descriptor for the"LocalTempFileCreator" integrated tool. Valid parameter options are documentedin the Administration Guide.

TSCOR0102 Bad extension for extension point {0} .The functionality to provide a system reference is integrated by an Eclipse extension point. An exceptionoccurred when determining the Java class which extends this extension point.

32 | Error messages


TSCOR0104 Cached elements (et_elements.xml) couldnot be recovered.Failed to load the cached elements in the element XML file. Maybe the internal application folder isasynchronous or does not exist or the element XML file is damaged.

User Response: • Refresh the internal application folder.• Clear the element list and element caches.• Delete the internal application folder and load the application again.

TSCOR0105 Elements could not be cached. Failed tosave et_elements.xml.Failed to save the elements in the element XML file. Maybe the internal application folder is asynchronousor does not exist or the element XML file is damaged.

User Response: • Refresh the internal application folder.• Clear the element list and element caches.• Delete the internal application folder and load the application again.

TSCOR0107 Failed to save the element list into cache.The element list could not be saved in the elementlist XML file. Maybe the internal application folder isasynchronous or does not exist or the element list XML file is damaged.

User Response: • Refresh the internal application folder.• Clear all the element list cache.• Delete the internal application folder and restart the client.

TSCOR0108 The local Workflow Manager applicationfolder could not be located.The internal application folder does not exist in the workspace. Maybe the internal project folder isasynchronous or damaged.

User Response: • Refresh the internal project folder.• Restart the workbench.• Delete the internal project if it exists and load the application again.

TSCOR0109 Failed to store the Element list in file li_{0} .xml.An element list could not be saved in its corresponding XML file. Maybe the internal application folder isasynchronous or does not exist or the element list XML file is damaged.

User Response: • Refresh the internal application folder.

Error messages | 33

• Clear all the element list cache.• Delete the internal application folder and load the application again.

TSCOR0110 An element list could not be restored: li_{0} .xml.An element list could not be loaded from its corresponding XML file. Maybe the internal application folder isasynchronous or does not exist or the element list XML file is damaged.

User Response: • Refresh the internal application folder.• Clear all the element list cache.• Delete the internal application folder and load the application again.

TSCOR0111 Cached element lists(lm_elementlists.xml) could not be recovered.An element list dependency could not be loaded from the element list XML file. Maybe the internalapplication folder is asynchronous or does not exist or the element list XML file is damaged.


TSCOR0112 An error occurred when trying to save thefile lm_elementlists.xml.An element list dependency could not be saved in the element list XML file. Maybe the internal applicationfolder is asynchronous or does not exist or the element list xml file is damaged.


TSCOR0113 File lm_elementlists.xml could not bedeleted.The element list file could not be deleted. This can have the following cause:

• The internal application folder is asynchronous, non-existent or damaged.• The element list XML file does not exist or is damaged.


34 | Error messages

TSCOR0114 Failed to delete a cached element list (li_{0} .xml).An element list file could not be deleted. This can have the following cause:



TSCOR0115 Failed to delete unreferenced Elementlists.Some element list files for which no references exist in the element list XML file could not be deleted. Thiscan have the following cause:



TSCOR0116 A thread was interrupted while initializingthe element lists.This is an internal program exception that can occur while a cached element list is loaded.


TSCOR0117 Invalid argument. Element type must notbe null.The element type is needed to create an element list entry. It can fail for the following reasons:

• The output file parameter configured by the tool that creates the element list does not return the value ofthe element type property, or the element type property is not configured as an output file parameter.

• A tool defined resource processing that creates/updates elements does not return the value of theconfigured element type.


• Verify that the output file parameter configured by the tool that creates theelement list is configured correctly and returns the element type for each entry.

• Verify that tool defined resource processing that creates/updates elementsreturns the value of the configured element type.

TSCOR0118 Failed to interpret the selection count {0} .The "Selection_Count" attribute of a modeled enabled condition does not contain a valid value.

Error messages | 35


Change the "Selection_Count" attribute value to be either numeric or "*" whichmeans that the action is enabled no matter how many elements are selected.

TSCOR0119 {0} is not a valid file name.During the parsing of the Error Feedback XML file, it was noticed that some error file references do nothave the structure of a z/OS partitioned data set name.


Verify that error file references contained in the Error Feedback XML file havethe structure of a z/OS partitioned data set name.

TSCOR0121 Failed to load error entries from cache(er_errorFeedback.xml).The error entries cannot be loaded from cache (er_errorFeedback.xml). Maybe the internal applicationfolder is asynchronous, non-existent or the er_errorFeedback.xml is damaged.

User Response: • Refresh the internal application folder.• Manually delete the file er_errorFeedback.xml while the application is not loaded.• Delete the internal application folder and restart the client.

TSCOR0122 Failed to store error entries into cache(er_errorFeedback.xml).The error entries cannot be saved in cache (er_errorFeedback.xml). Maybe the internal application folder isasynchronous, non-existent or the er_errorFeedback.xml is damaged.

User Response: • Refresh the internal application folder.• Manually delete the file er_errorFeedback.xml while the application is not loaded.• Delete the internal application folder and restart the client.

TSCOR0123 The file descriptor with the ID {0} couldnot be found among previous output parameters.A file input parameter was modeled with the attribute "Parameter_From" set to "Previous_Tool" but the filedescriptor was never returned as an output parameter by a previous executed tool in this action.


Either set the "Parameter_From" value of the file input parameter to "Context" ormake sure that the file descriptor is returned as an output parameter by a previoustool in the action sequence. Setting the "Parameter_From" attribute to "Context"requires the file descriptor to have a valid "Name_Physical" attribute value.

TSCOR0124 The property {0} was not found within theexecution context.A tool descriptor was modeled with an input parameter with the "Parameter_From" attribute set to"Context", but the referenced property is not available in the execution context.

36 | Error messages


Either change the model so that the property will be in the execution context or setthe "Parameter_From" attribute of the input parameter to "Context". To see if aproperty is in the execution context, open the Properties View while an element isselected.

TSCOR0125 The property {0} was not found amongprevious output parameters.An input parameter was modeled with the attribute "Parameter_From" set to "Previous_Tool", but theproperty was never returned as an output parameter by a previously executed tool in this action.


Either set the "Parameter_From" value of the input parameter to "Context" or makesure that the property is returned as an output parameter by a previous tool in theaction sequence.

TSCOR0126 An error occurred while loading a filter.An exception occurred when loading the file with the persistently cached filter data from the internal projectfolder in the workspace of the user.

User Response: See the message under "Reason:" in the message dialog. If necessary,contact the Administrator.


Check the error log for more information.

TSCOR0127 An error occurred when trying to create aSAX parser instanceAn internal XML parser problem occurred when loading the filter data from the persistent cache in theinternal project folder of the user's workspace.


TSCOR0128 An error occurred while parsingft_filters.xml.An internal XML parser problem occurred when loading the filter data from the persistent cache in theinternal project folder of the user's workspace.


TSCOR0129 An error occurred when trying to save thefile filters.xml.Each time a filter is created, deleted or changed, the file which contains the filter data is written to thepersistent cache in the internal project folder of the user's workspace. This write action failed.


• Verify that the user has the authority to write to the internal project folder.• Check the error log for more information.

Error messages | 37

TSCOR0130 Exception occurred when trying to deleteft_filters.xml.The deletion of the cached filter data in the internal project folder failed when requested within the contextof the Clear Cache dialog.


• Verify that the user has the authority to delete files from the internal projectfolder.

• Check the error log for more information.

TSCOR0131 An error occurred when trying to load thefile jt_jobs.xml.When an application is loaded, the job information of the application is reloaded from the persistent cachein the internal project folder of the user's workspace. This reload failed.




TSCOR0132 Failed to load opened files.The local cache for opened editor sessions could not be read. This is either caused by a corrupt cache orthe Eclipse workspace being out of synchronization.


• Refresh the internal project folder (see Workspace out of sync).• Clear the persistent cache (see Clear the persistent cache in the

workspace ).

TSCOR0133 Failed to load error entries.The local cache for error feedback entries could not be read. This is either caused by a corrupt cache orthe Eclipse workspace being out of synchronization.



workspace ).

TSCOR0134 Failed to load Jobs.The local cache for executed jobs could not be read. This is either caused by a corrupt cache or theEclipse workspace being out of synchronization.



workspace ).

38 | Error messages

TSCOR0136 Failed to remove cached elements.The persistent cache for modeled elements could not be deleted. This is probably caused by the Eclipseworkspace being out of synchronization.


• Refresh the internal project folder (see Workspace out of sync).• Clear the cache manually (see Clear the persistent cache in the

workspace ).

TSCOR0137 Failed to remove cached filters.The persistent cache for created filters could not be deleted. This is probably caused by the Eclipseworkspace being out of synchronization.


• Refresh the internal project folder (see Workspace out of sync).• Clear the cache manually (see Clear the persistent cache in the

workspace ).

TSCOR0138 Failed to {0} .The cache could not be saved persistently in the workspace. This is most probably caused by the Eclipseworkspace being out of synchronization with the file system.


• Refresh the internal project folder and restart the client (see Workspaceout of sync).

TSCOR0139 Backup folder could not be created.The first step of the application update is to back up the files which contain the persistently cached data inthe workspace. In this step the creation of the backup folder failed. This means the complete applicationupdate action failed.


• Verify that the user has the authority to create a folder in the internal projectfolder.

• Refresh the internal project folder (see Workspace out of sync).

TSCOR0140 Failed to copy the backup folder. {0} .The first step of the application update is to back up the files which contain the persistently cached data inthe workspace. In this step the copy of the files to the backup folder failed. This means the completeapplication update action failed.


• Verify that the user has the authority to write to the backup folder in theinternal project folder.


Error messages | 39

TSCOR0141 Converting an outdated application modelfailed.This is an internal program exception. An attempt to convert a possibly outdated model failed. A model willbe treated as outdated if syntax errors were detected while loading it.

Model Administrator Response: Please contact SupportLine.

TSCOR0142 An error occurred while trying to read theconfiguration file: {0} .This error occurs if a model could not be read. It can be for the following reasons:

• Network problems.• Model does not exist under the configured path from the master configuration.• User is not authorized to read the model file.



• Make sure that the Properties View is opened and select the application in theTree View. The Properties View now shows configured attributes of theapplication (defined in the master configuration). Verify that the "ModelLocation" property has a correct value.

• Verify that the user has read access to the model file.

TSCOR0143 The configuration file {0} could not befound.This error occurs if a model file could not be found locally (or in the local network).



• Make sure that the Properties View is opened and select the application in theTree View. The Properties View now shows configured attributes of the application(defined in the master configuration). Verify that the "Model Location" property hasa correct value.

• If the model file is located on the mainframe, use the prefix "mvs:" for the modelpath definition (attribute "conf:") in the master configuration (e.g."mvs:hlq.models(mymodel)").

• Verify that the user has read access to the model file.

TSCOR0144 System could not create configurationdataset {0} .This is an internal program exception that occurs when a downloaded model could not be saved in theworkspace.

Model Administrator Response: Refresh your internal project folder (see Workspace out of sync).

40 | Error messages

TSCOR0145 An exception occurred while trying toclose the configuration file {0} .This is an internal program exception that occurs when a downloaded model could not be saved in theworkspace.

Model Administrator Response: Refresh your internal project folder (see Workspace out of sync).

TSCOR0146 The given input stream is null. Possiblereason: The model configuration file from the masterconfiguration does not exist.This is an internal program exception. It can occur if a model could not be loaded correctly.


• Make sure that the Properties View is opened and select the application in theTree View. The Properties View now shows configured attributes of the application(defined in the master configuration). Verify that the "Model Location" property hasa correct value.

• Verify that the user has read access to the model file.• Contact Customer Support.

TSCOR0147 A system reference for connection {0}already exists!This is an internal program exception. It is caused by an attempt to create a system reference that conflictswith an existing one.


TSCOR0148 Failed to add the system referencebecause no ISystemImage (remote system) given.This is an internal program exception. It is caused when a system reference is registered without a systemreference (ISystemImage interface).


TSCOR0149 Failed to load system references.This error occurs if a cached system reference cannot be recovered after a client restart. Possible reasonsare:

• A remote system connection associated with a system reference cannot be found. This is caused if theremote system connection was renamed or deleted.

• The cache is corrupt.

User Response: • Execute the "Add System" function in the Tree View to recreate the systemreference.

Error messages | 41

TSCOR0150 An error occurred when trying to create aSAX parser instanceThis is an internal program exception. It is caused by a failed attempt to instantiate a Java XML parser.


TSCOR0151 Failed to recover cached systems(st_systems.xml).This exception is caused by a corrupt system reference cache file (bad XML syntax). A detailed errormessage can usually be found in the error details.


Open the cache file in a text- or XML editor to determine and correct the error. Thefile is named "st_systems.xml" and is located in the internal project. If necessary,contact SupportLine.

TSCOR0152 An error occurred when trying to save thefile st_systems.xml.This is an internal program exception that occurs when a system reference cannot be saved into the cache.This can be caused when the Eclipse workspace is out of synchronization.

User Response: Refresh the internal project folder (see Workspace out of sync).

TSCOR0153 Model update check failed. Either themaster configuration could not be read or the updateitself failed.This is a top-level exception which occurs if updating the model or checking for a new model version fails. Itcan fail for several reasons, including:

• The master configuration, containing information about the newest model version, could not be read.• The user cancelled an "Enter Password" dialog which was required for reading the master configuration.• Loading a new model version failed. A more detailed message can usually be found in the error details.

Note that the update-check will only happen once per application and Eclipse session.

User Response: • Fix any problems which might prevent the master configuration from being read.• The application can be updated manually by refreshing the corresponding

system reference in the Tree View and selecting the "Update Application" actionin the context menu of the application. If no "Update Application" action isdisplayed, then there is no newer version available.


Check the error details for the cause of this message and resolve the problem.

42 | Error messages

TSCOR0154 Failed to check for model update. Theapplication does not seem to be loaded.This is an internal program exception. An attempt to update an application was made but the applicationdoes not seem to be loaded correctly.


TSCOR0155 The model update was performed but theversion numbers still do not match: {0} MasterConfiguration version number: {1}{0} Model versionnumber: {3}This problem is caused by an invalid configuration of model version numbers. The version number of anapplication defined in a master configuration is not equal to the version number of the model it refers to.The version number of a model must be set under "Application Options" in the "Version" attribute.


Correct the version numbers of the application in the master configurationand the model.

TSCOR0156 Missing location keyword in model path:{0} . {1} .A model location path ("conf" attribute in master configuration) did not contain a location keyword. Thelocation keyword is used to determine on which platform a model is stored (e.g. "local:", "mvs:").


Add a location keyword in front of the model location. Valid keywords aredocumented in the Administration Guide. Example: "Conf: local:C:\myModel.xml"

TSCOR0157 Wrong location keyword in model path:{0} . {1}The location keyword of a configured model path in a master configuration is invalid.


Correct the location keyword in the master configuration. Valid keywords aredocumented in the Administration Guide.

TSCOR0158 A file input parameter must be defined forthe integrated tool LocalSyntaxCheck (the programsource that should be checked).A file input parameter for a "LocalSyntaxCheck" integrated tool is missing.


Ensure that a file input parameter is modeled for the integrated tool"LocalSyntaxCheck".

Error messages | 43

TSCOR0159 A file output parameter (type = WorkspaceFile) must be defined for the integrated tool file locator.The integrated tool "LocalFileLocator" requires a file output parameter which is missing in the tooldescriptor definition.


Add a file output parameter to the "LocalFileLocator" tool descriptor whichreferences a file descriptor of the type "Workspace_File".

TSCOR0160 A file input parameter must be defined forthe integrated tool EDIT_CLEANUP.The integrated tool "Edit_Cleanup" was not properly modeled. It requires a file input parameter whichpoints to the file that should be deleted.

Model Administrator Response: Add a file input parameter to the "Edit_Cleanup" tool descriptor.

TSCOR0161 A file input parameter (describing theerror XML input) must be defined for the integrated toolErrorFeedback.The integrated tool "ErrorFeedback" was not properly modeled. It requires a file input parameter.


Add a file input parameter to the "ErrorFeedback" integrated tool. The referencedfile descriptor must point to a file which contains compiling errors in XML format.

TSCOR0163 No input parameters configured for theintegrated tool Local File Creator.The integrated tool "LocalFileCreator" was not modeled properly (parameters are missing).


Correct the modeling errors concerning the tool descriptor for the"LocalFileCreator" integrated tool. Valid parameter options are documented inthe Administration Guide.

TSCOR0164 LocalFileCreator: Failed to create a localfile because no element type could be determined fromthe given parameters.The integrated tool "LocalFileCreator" was not modeled properly. No required element type for the filecreation could be determined based on the modeled parameters.


Correct the modeling errors concerning the tool descriptor for the"LocalFileCreator" integrated tool. Valid parameter options are documented inthe Administration Guide.

44 | Error messages

TSCOR0165 Physical name of file descriptor {0}missing.A file descriptor, to which content should be written, has no value declared in the attribute "Name Physical".


Add a valid value to the attribute "Name Physical" of the given file descriptorin the model file.

TSCOR0166 Could not find a property with the ID {0} .This is normal when the model has been changed andan old cache is loaded.Self-explanatory.

User Response: Clear the persistent cache with the Clear Cache... dialog and refresh the wholeelement list in the table view.

TSCOR0167 No ZConnector Extension was found for aremote system with the name {0} .Cached system references could not be loaded. As a result no application was loaded. Possible reasonsare:

• Corrupt cache files.• Asynchronous Eclipse workspace.• Internal problems (e.g. XML parser exceptions).

User Response: Recreate the system references manually in the Tree View. Refresh yourEclipse workspace if necessary.



TSCOR0168 Illegal character # by applications name.The application name must not contain the character '#'.


Change the application name in the master configuration file (seedescription).

TSCOR0170 Missing input parameter target ID of tool{0} .The file target ID of a input parameter in tool {0} is not configured.

Model Administrator Response: Verify your model configuration (see description).

Error messages | 45

TSCOR0171 The action descriptor {0} contains a tooldescriptor relationship without a target ID.Some tool descriptors defined in the action {0} do not have a target ID.

Model Administrator Response: Check the model configuration (see description).

TSCOR0172 No element type was found for the matchname {0} which is part of the compounded match name{1} .A compounded match name could not be completely resolved.


• Verify that the correct value of the element list was defined as "Element Type".• Correct the match name returned by the tool or the "Matchname" attribute of

the corresponding element type.

TSCOR0173 No extension found for job utility.No plug-in extension was found for the job utilities in the user's AWM installation.


TSCOR0174 Validate message parsing error: Thevalidate message cannot be empty.Self-explanatory.


Make sure that the validate tool does not return empty validate messages. If noerror(s), warning(s) and/or information message(s) occurred, don't return the key"VAL_MSG". See Relationship: Tool has Validate Action in the Workflow ManagerConfiguration Guide for more information.

TSCOR0175 Validate message parsing error: Key {0}must be closed.The keywords of validation messages have to be returned in parentheses.


Self-explanatory. See Relationship: Tool has Validate Action in the WorkflowManager Configuration Guide for more information.

TSCOR0176 Validate message parsing error: MSGTEXTis mandatory.The keyword MSGTEXT is mandatory for validation messages.


Self-explanatory. See Relationship: Tool has Validate Action in the WorkflowManager Configuration Guide for more information.

46 | Error messages

TSCOR0177 UPDATE resource operation failed. Noreference element was found for updating.The UPDATE resource operation failed because no element was found for updating.


Either make sure to return a complete element ID (including the matchname) withthe resource operation or do not enable the tool in actions which are not elementactions. Note that properties returned by resource operation must be modeled asoutput parameters with the type "ELEMENT".

TSCOR0178 Parameter from USER_INPUT are notallowed for mass processing tools. Please change theparameter from attribute of parameter # {0} either toContext or Previous Tool.A tool descriptor was modeled within a mass processing action descriptor which contains an inputparameter with the attribute "Parameter From = User_Input". This is a non-supported combination.


Change the "Parameter From" attribute of the input parameter either to"Context" or "Previous Tool".

TSCOR0179 Different Parameter from attributes are notallowed for mass processing tools. All massprocessing parameters must either come from thecontext (e.g. selected elements) or previous toolresources (e.g. selected table rows from an inputdialog).A tool descriptor which was called within a mass processing action contains mass processing inputparameters with different "Parameter From" attribute values. This is invalid, because the number ofselected resources can differ from the number of resources created during the action.


Change the "Parameter From" attribute values of all mass processing inputparameters of the tool descriptor either to "Context" or "Previous Tool".

TSCOR0180 Failed to find the workspace file for filedescriptor {0} because the physical name is null orempty.A workspace file could not be found because the file descriptor did not have a physical name at runtime.


Either specify a "Name Physical" attribute in the file descriptor or, if the file name isreturned by a tool, set the "Parameter From" attribute of the input parameter usingthe file descriptor to "Previous Tool".

Error messages | 47

TSCOR0181 The file {0} already exists.A file could not be created by the integrated tool "Local File Creator" because it already existed. This erroronly occurs if no user interface is available.

User Response: Delete the file manually and try again.

TSCOR0182 The execution of an action failedAn error occurred during the execution of an action descriptor. This is an internal exception.


TSCOR0183 An error occurred while executing theaction {0} .This is a very common top-level exception. It usually occurs if a tool within the action returns a high returncode or encounters a problem. A tool which returned a high return code most probably also returned areason message. The reason message should be visible under "Reason" in the error dialog or can befound in the error details.

User Response: Contact the model administrator if the reason given by the executed tool is not clear orif there is no reason message at all.

TSCOR0184 The cached information for {0} seems tobe incompatible with the loaded model.The cached information to load seems to be incompatible with the load model and there is no UI to ask toreset the corresponding cache files.

User Response: Delete the corresponding cached file and try the action again.

TSCOR0185 Failed to aquire a file descriptor from thegiven input.A file descriptor could not be acquired from the given input. This can be caused by a modeled inputparameter which has the type "File" but no file descriptor associated under the "Target ID File" attribute. Itcan also be caused by an internal issue (context parameter is null).

Model Administrator Response: Verify that the corresponding input parameter is correctly modeled.

TSCOR0186 The integrated tool ChildrenRefresher canonly refresh files of the type Workspace_File, but a {0}file input parameter was modelled.A wrong file input parameter type was modeled for the integrated tool "Children Refresher". Only file inputparameters of the type "Workspace_File" are permitted. See Children Refresher in the Workflow ManagerConfiguration Guide for other valid tool configurations.

48 | Error messages


Change the input file descriptor to be a "Workspace File" or use a different toolconfiguration (see Children Refresher in the Workflow Manager ConfigurationGuide).

TSCOR0187 Failed to create an element ID. Either theinput parameters do not contain an element type or allkey properties.The integrated tool "ChildrenRefresher" failed to refresh the children of an element because no element IDcould be created from the modeled input parameters.


• Verify that the integrated tool ChildrenRefresher contains modeled inputparameters which include an element type property and ID properties of theelement that should be refreshed.

• Verify that the integrated tool ChildrenRefresher was called with the correctparameter values.

TSCOR0188 Unable to get property value for parameter# {0} . No target ID property found.A "Target ID Parm" attribute was expected from a modeled input parameter but is missing.


• Add a value for the "Target ID Parm" attribute of the specific input parameter.• Check if the "Type" attribute of the input parameter is correct.

TAURUS for RDz (TSRDZ) messages

TSRDZ0001 The remote resource {0} was not found.The remote resource {0} could not be retrieved. This may be a general connection problem, or the data setcould not be found in the host system, or a modeled integrated tool is not correctly modeled.

User Response: Verify that there is a connection to z/OS.


• If the problem is caused by a modeled integrated tool, verify that the inputparameters are correctly modeled.


Server AdministratorResponse:

Check the server logs and z/OS hardcopy log for more information

TSRDZ0002 An error occurred while trying to open thefile {0}This is an internal program exception.


Error messages | 49

TSRDZ0003 Connection failed when trying to reach theremote system job utility.The connection to the remote system could not be established.

Server Administrator Response: • Check if there are any network problems.• Verify that the server is up and running.• Check the server logs and z/OS SYSLOG for more information.

TSRDZ0004 Failed to initialize the RDz Job Utility.The creation of an instance of the JesJobUtil class failed.


TSRDZ0005 The job with the ID {0} could not be read.The given job's contents could not be read from the remote system.


• Verify that the server is up and running (especially the JMON started task).• Check if there are any network problems.• Check the server logs and z/OS SYSLOG for more information.• Check if the job still exists.

TSRDZ0006 DD {0} of job {1} could not be read.The given DD contents of the given job could not be read from the remote system.



TSRDZ0007 DDs of the job with the ID {0} could not bedetermined.The DD statements of the given job could not be determined.



TSRDZ0008 The return code of the job with the ID {0}could not be determined.The return code of the given job could not be determined.

50 | Error messages



TSRDZ0009 Invalid resource during association ofproperty group.This is an internal program exception.


TSRDZ0010 A local property group with name {0} doesnot exist.The property group to be associated with the element could not be found in the local system.


Make sure that the element special property "Property Group" exists in thelocal user system.

TSRDZ0011 The error feedback XML file could not beread during the execution of the integrated toolRefreshDependencies.The input file parameter for a tool refreshing the copybooks could not be read. It may not be modeledcorrectly or could not be accessed (insufficient RACF authority).


Verify that the input file parameter of the integrated tool"RefreshDependencies" is modeled correctly.


Check the server logs and z/OS hardcopy log for more information.

TSRDZ0012 The folder {0} could not be created duringexecution of the integrated tool Refresh Dependencies.Failed to execute the integrated tool "Refresh Dependencies" because the folder could not be createdwhere the copybooks should be copied to. The internal application folder is either out of synchronization orit could not be accessed.

User Response: • Refresh the internal application folder.• Restart the client.• Make sure that you have write access to the internal application folder.• See the log file for more information.

Error messages | 51

TSRDZ0013 An error occurred while parsing the errorfeedback XML file.The input file parameter of the tool refreshing the copybooks cannot be parsed. It may be not modeledcorrectly or the file syntax was incorrect.


• Verify that the input file parameter of the integrated tool"RefreshDependencies" is correctly modeled.

• Verify the syntax of the XML file.

TSRDZ0014 Could not find category for COBOL on thesystem.This is an internal program exception.


TSRDZ0015 Could not find category for PLI on thesystem.This is an internal program exception.


TSRDZ0016 Could not find category for ASSEMBLERon the remote system.This is an internal program exception.


TSRDZ0017 Could not find category for C_CPP on theremote system.This is an internal program exception.


TSRDZ0018 Duplicate instance of category: {0} .This is an internal program exception.


TSRDZ0019 The language: {0} is not supported.The language {0} (second input parameter to integrated tool "PropertySetCreator") is not supported.

52 | Error messages


Change the language to (COBOL, PLI, PL1, ASM, ASSEMBLER, C, CPP,C_CPP, C/CPP).

TSRDZ0020 SYSLIB parsing error.An error occurred when parsing the SYSLIB configured in the integrated tool "PropertySetCreator". This isa modeling error.


See Defining the SYSLIB attribute to resolve COBOL copybooks in the WorkflowManager Configuration Guide for how to configure the integrated tool"PropertySetCreator".

TSRDZ0021 No container for system: {0} .This is an internal program exception.


TSRDZ0022 Parameter property group name ismissing.The name of the property group which is to be associated with the element is missing. This is a modelingerror.


Make sure that the configured property group name will be found in thecontext.

TSRDZ0023 The resource {0} was not found.The physical resource of the element whose property group should have been associated was not foundon the host during execution of the integrated tool "PropertySetAssociator". This may be a modeling error.


Ensure that the integrated tool "PropertySetAssociator" is modeledcorrectly.

TSRDZ0024 The property group {0} does not exist.The property group to be associated with the element could not be found in the system. This may be amodeling error.


Ensure that the property group exists on the user system or modify the toolconfiguration.

TSRDZ0025 The property group {0} already exists.Parameter Replace was {1} .The property group to be created could not be replaced because the integrated tool"PropertyGroupCreator" is configured in such a way that replacements are not allowed. This propertygroup was already defined in the system.


Change the first input parameter of 'PropertySetCreator' or delete the existingproperty group on the user system.

Error messages | 53

TSRDZ0026 The name of existing property group {0} tobe copied was not found in the system.The integrated tool "PropertySetCreator" is configured in such a way that an existing property group to becopied. But this property group was not found in the system.


Ensure that the property group to be copied exists in the user system ormodify the tool configuration.

TSRDZ0027 The Property Group {0} already exists inthe systemThe integrated tool "PropertySetCreator" failed during its execution because the property group to becreated already exists in the system.


Change the first input parameter of "PropertySetCreator" or delete the existingproperty group in the user system.

TSRDZ0032 {0} is neither a sequential data set nor amember of a partitioned data set.Failed to get the content of the data set that corresponds to the file descriptor of the tool because it isneither a sequential data set nor a member of a partitioned data set.


Ensure that the remote resource of the file descriptor is a sequential data setor a member of a partitioned data set.

TSRDZ0033 Failed to get contents of file {0} .Failed to get the content of the remote file. This can have several reasons:

• General connection problem.• Modeling errors.• RACF access problem.

User Response: Verify that you have a connection to z/OS.

Model Administrator Response: • If the file is from a modeled tool, verify that it is modeled correctly.• Check the error log for more information.

Server Administrator Response: Check the server logs and z/OS hardcopy log for more information.

TSRDZ0034 Recall for data set {0} failed.When attempting to get the contents of a migrated data set {0}, the data set could not be recalled.


TSRDZ0035 Failed to retrieve data set named {0} .The data set {0} could not be found in the remote system. This may be a general connection problem or amodeling error.

54 | Error messages



TSRDZ0036 Operation cancelled by user.Self-explanatory.

User Response: Retry the action.

TSRDZ0038 Failed to set contents for data set {0} .Failed to set the content of a remote data set. This can have several reasons:

• General connection problem.• Modeling errors.• RACF access problem.

User Response: Check that you have a connection to z/OS.



TSRDZ0040 Failed to allocate the data set {0} .Data set {0} cannot be allocated.

User Response: Verify that you have a connection to z/OS.


TSRDZ0041 Deletion of data set failed: {0} .Data set {0} cannot be deleted.

User Response: Check that you have a connection to z/OS.


TSRDZ0042 Failed to connect to {0} .The connection to z/OS cannot be established

User Response: • Verify the network connection to the server.• Verify the server definition in the client (host name, port).

TSRDZ0046 Failed to wait for RSE initialization.This is an internal program exception.


Error messages | 55

TSRDZ0047 {0} is not a partitioned data set.Failed to get the members of data set {0} because it is not a partitioned data set. This may be a modelingerror.


If this error occurs during the execution of a modeled tool, verify that the tooldescription and file descriptor are correctly modeled.

TSRDZ0048 {0} does not exist on System {1}The client failed to receive attributes of a file because it does not seem to exist on the target system.

Model Administrator Response: Verify that the file name is correct.

TSRDZ0049 {0} is not a valid ZOSDataset, could notretrieve FileAttributesFailed to receive the attributes of a z/OS data set because the file name does not seem to be valid.

Model Administrator Response: Verify that the file name is correct.

TSRDZ0053 The remote resources {0} and/or {1} werenot found.At least one remote resource could not be retrieved for opening a compare editor. Possible reasons are:

• One or both files do not exist.• The integrated tool "File Compare" is not properly modeled.• Connection problems to the remote system.

User Response: Verify that there is a connection to z/OS.


• If the problem is caused by a modeled integrated tool, verify that the inputparameters are correctly modeled.



Check the server logs and z/OS hardcopy log for more information.

TSRDZ0054 The first and second file descriptor tocompare must be of type MVSPO_Member orMVS_SEQThe execution of the integrated tool FileCompare failed because the first and/or second file descriptor werenot declared as type MVSPO_Member or MVSSEQ file descriptor.


Verify the type of the first and second file descriptor associated as inputparameter with the integrated tool FileCompare. The file descriptors must be oftype MVSPO_Member or MVSSEQ.

56 | Error messages

TAURUS for z/Server (TSZSV) messages

TSZSV0001 The data set is migrated. Do you wish torecall it?This is an informational message indicating that the selected data set is in migrated status on the remotesystem. It has to be recalled before it can be used.

User Response: Respond to the dialog.

TSZSV0002 Data set is migrated.The selected data set is migrated. The requested action cannot be performed.

User Response: Use the context menu action Recall to recall the data set. Then repeat the requestedaction.

TSZSV0003 Exception when allocating data set: {0} .A tool execution needs a parameter file to be allocated on the remote system with the given name. Thisallocation failed.

Server Administrator Response: Check the z/Server logs and z/OS SYSLOG for more information.

TSZSV0004 IO exception during dialog processing.An I/O exception occurred during the execution of an ISPF dialog process.

Model Administrator Response: Check the error log for more information.

Server Administrator Response: Check the z/Server logs for more information.

TSZSV0005 z/Server exception during dialogprocessing.A z/Server exception occurred during the execution of an ISPF dialog process.



TSZSV0006 Data set migration exception during dialogprocessing.An exception occurred during the execution of an ISPF dialog process because a requested data set wasmigrated.

User Response: Recall the requested data set and retry the ISPF dialog execution.

Error messages | 57

TSZSV0007 XML parse exception during dialogprocessing.An XML response from the z/Server could not be interpreted.



TSZSV0008 No UI Tool configured for {0} .The ISPF dialog process called a panel for which no tool was configured in the corresponding model file.Each panel called in the ISPF application must have a tool with an ISA_ISPF_Panel relation with attributePanel Name set to the name of the ISPF panel.

Model Administrator Response: Correct the tool definition in the model file.

TSZSV0009 z/Server parameter error: Parameter {0} notfound in parameter memory.A parameter which was expected to be found in the parameter memory was not found.


Verify the model file. Verify if the attribute "Parameter From" is setcorrectly.

TSZSV0010 Invalid parameter string received from z/Server: {0} .An unexpected message format was send from the z/Server to the client during the execution of an ISPFdialog process.



TSZSV0011 z/Server parameter error: Value lengthmissing for {0} .An unexpected message format was sent from z/Server to the client during the execution of an ISPF dialogprocess.


• Check the error log for more information.• Verify that the extension of the corresponding ISPF panel is correct

(TAUPARMS entry).• Verify that the panel field parameters of the corresponding tool are modeled

correctly.


Check the z/Server logs for more information.

58 | Error messages

TSZSV0012 z/Server parameter error: Value length for{0} is not numeric.An unexpected message format was send from z/Server to the client during the execution of an ISPFdialog process.




correctly.



TSZSV0013 z/Server parameter error: Value length tooshort for {0} .An unexpected message format was sent from z/Server to the client during the execution of an ISPF dialogprocess.




correctly.



TSZSV0014 Error when parsing input for table. Moretable properties configured than delivered by theremote tool (file descriptor: {0} ).An unexpected message format was sent from z/Server to the client during the execution of an ISPF dialogprocess with an ISPF table. The remote tool sent fewer values than properties were configured for thecorresponding file descriptor.


• Verify that the extension of the corresponding ISPF panel is correct(TAUTABV entry).

• Verify that the properties of the corresponding file descriptor are modeledcorrectly.

TSZSV0015 Error when parsing input for table. Valuefor property {0} not found.An unexpected message format was sent from z/Server to the client during the execution of an ISPF dialogprocess with an ISPF table. The value of a property was not sent in the expected length.

Error messages | 59




TSZSV0016 Error when parsing input for table.An unexpected message format was sent from z/Server to the client during the execution of an ISPF dialogprocess with an ISPF table.




TSZSV0017 Failed to parse the response: {0} .An unexpected message format was sent from z/Server to the client during the execution of an ISPF dialogprocess. An expected tool parameter could not be found in the response.




correctly.



TSZSV0018 IO Exception during ISPF dialogprocessing.An I/O exception occurred during the execution of an ISPF dialog process.



TSZSV0019 Exception during ISPF dialog processing.An exception occurred during the execution of an ISPF dialog process.



TSZSV0020 Port {0} freed.This is an informational message indicating that the given port is released at the end of an ISPF dialogprocess.

User Response: This is an informational message.

60 | Error messages

TSZSV0021 There are no z/OS systems defined. Pleasedefine a new connection first.A z/OS connection must be defined before a system reference can be defined.

User Response: Define a z/OS connection in the Remote System View first.

TSZSV0022 Target Management initializationinterrupted.The initialization of the target management which is a prerequisite for AWM was interrupted during Eclipsestart up.

User Response: If there are consecutive error situations, restart Eclipse.

TSZSV0023 {0} is incompatible with {1} .An ISystemImage instance was loaded which is not compatible with the zSystemUtilities class.


If this is a customer-own implementation of the ISystemImage, ensure that thisimplementation complies with the IConnectorService interface. Otherwisecontact SupportLine.

TSZSV0025 The file type {0} is not supported by {1} .A file descriptor with a file type which is not supported by the zServer edit class was passed to theintegrated tool RemoteEdit.

Server Administrator Response: Contact SupportLine.

TSZSV0026 Exception when calling the edit interfaceduring dialog processing.An exception occurred when the ISPF edit interface was called within an ISPF dialog process.


Verify if there is additional information in the user server's SYSTSPRT output. Ifnecessary repeat the action with the dialog debug option set on.

TSZSV0027 Failed to get enqueue info for resource{0} .A z/OS resource was locked by another user and the GETENQI z/Server command caused an exception.This is either caused by a z/Server issue or an internal client exception.


Check the z/Server scheduler trace for correctly receiving the GETENQImessage.

TSZSV0028 The resource is locked by another user.A resource was locked by another user and the z/Server GETENQI command was scheduled to retrievedetailed enqueue information. The command was successfully executed but returned an empty response.

Error messages | 61

This can occur if the enqueue was made by another z/Server scheduler which was managed by a differentz/Server holder task.

ServerAdministratorResponse:

Verify that the users are not working with different z/Server scheduler tasks whichare managed by different holder tasks. If that is the case, consider reconfiguringthe z/Server tasks.

TSZSV0029 Action cancelled by user.Self-explanatory.


TSZSV0030 The file {0} already exists.A file could not be created by the integrated tool "File Compare" because it already existed. This error onlyoccurs if no user interface is available.

User Response: Delete the file manually and try again.

TSZSV0031 The first file type {0} is not supported forthe FileCompareRemoteThe execution of the integrated tool FileCompare failed because the first file descriptor was not declared astype MVSPO_Member or MVSSEQ file descriptor.


Verify the type of the first file descriptor associated as input parameter with theintegrated tool FileCompare. The file descriptor must be of typeMVSPO_Member or MVSSEQ.

TAURUS edit macro (TSMAC) messages

TSMAC0001 The edit macro name must not be anempty string.An edit macro tool descriptor was executed with an empty edit macro name parameter.


Verify in the model that the edit macro tool descriptor cannot be executed withan empty edit macro name parameter.

TSMAC0002 Not a remote edit session.An edit macro tool descriptor was called within a non-remote edit session.

User Response: Close the editor and open the same file using the MVS Explorer or a "remote edit"action from a modeled application.

TSMAC0003 An error occurred while sending the hostcommand: {0} .The host command for a edit macro was not sent successfully.

62 | Error messages


TSMAC0004 The file descriptor {0} is not a member orsequential data set.A edit macro tool descriptor was executed within an editor which was opened with an invalid file descriptor.


Verify that modeled edit actions with edit macro support use the integrated tools"RemoteEdit" or "RemoteBrowse" which accept the correct file descriptors only. Ifother edit actions exist (like local edit), consider adding enabled conditions to theedit macro editor actions.

TAURUS meta model (TSMDL) messages

TSMDL0002 The converter could not detect the reasonfor the model incompatibility. Please check the Detailsarea after closing this message.AWM was trying to convert a model that seems to be incompatible with the current version but failed sinceno repairable incompatibilities were detected.


Open the model in the model editor and click the Details button in the editor. A listwill open up within the editor containing detailed messages about why the model isincompatible with AWM. Send this information to SupportLine if necessary.

TAURUS meta model editor (TSMET) messages

TSMET0001 Model import failed.The model import action could not be executed. Possible reasons are:

• At least one of the two models is inconsistent.• An internal error occurred during the import process.

User Response: Use the validate function to find out if both models on their own are consistent. Fix themodels if validation errors occur. If both models seem to be valid, contact SupportLine.

TSMET0002 At least one given object must not be null.This is an internal program exception which is not supposed to occur under any circumstances.


TSMET0003 An error occured during the drag and dropoperation.The model import action could not be executed. Possible reasons are:

Error messages | 63


User Response: Use the validate function to find out if both models on their own are consistent. Fix themodels if validation errors occur. If both models seem to be valid, contact SupportLine.

TSMET0004 Unable to execute {0} command.The model import action could not be executed. Possible reasons are:


User Response: Use the validate function to find out if both models are consistent. Fix the models ifvalidation errors occur. If both models seems to be valid, contact SupportLine.

TSMET0006 Error creating nested text editor.The model editor could not be opened and initiated properly. This is an internal program exception.


TAURUS subsystem MVS (TSMVS) messages

TSMVS0001 The parameter file {0} could not becreated.The MVS parameter file used to pass long parameters between client and mainframe could not beallocated.


• Check if the user has write authority to the parameter file.• Delete the parameter file if it already exists, and ask the user to retry the action.

It is possible that the parameter file was allocated incorrectly.

TSMVS0002 A file input parameter must be set.An integrated tool descriptor for edit or browse was modeled without a file input parameter (which isrequired).


Add a file input parameter to the corresponding tool descriptor. Verify that a filedescriptor is referenced by the "Target_ID_File" attribute of the input parameterand that the "Type" attribute is set to "File".

TSMVS0003 File input parameters are not yetsupported by the ISPF tool executor.An ISPFCOMMAND tool descriptor was modeled with a file input parameter, which is currently notsupported.

64 | Error messages


Remove the corresponding file input parameter from the tool descriptor or checkwhether the "Type" attribute of the parameter was accidentally set to "File".

TSMVS0005 Could not connect to z/OS.An ISPFCOMMAND tool could not be executed because a z/OS connection could not be establishedcompletely. (XXXX) this is either caused by a network problem or an issue while loading a model whileconnecting.

User Response: • Check your network connection to the server.• Check your server definition in the client (host name, port).


• Verify that the host server is up and running correctly.• Check the error details. If the underlying error message correlates to an issue

while loading a model, please verify that the model under the specified location ofthe "zExpConf" attribute of the master configuration exists, is accessible andvalid. If no "zExpConf" attribute is defined in the master configuration, an internalclient error occurred.

TSMVS0006 The command \ {0} \ could not be sent.An ISPFCOMMAND tool failed executing a TSO or server command. This can either be caused byexecuting a REXX procedure, communicating with an ISPF panel (XXXX) or an inconsistent clientinstallation.



Check the error details to see whether the error was caused by an inconsistentclient installation. If that is the case, re-install the client on the correspondingmachine.


Check whether the error message was caused while an ISPF dialog wasexecuted.

TSMVS0007 Could not write on file: {0} .An ISPFCOMMAND tool failed to write input parameters into the parameter file.



• Check whether the user has write rights on the parameter file.• Delete the parameter file if it already exists and ask the user to retry the action.

It is possible that the parameter file was allocated incorrectly.

TSMVS0008 The parameter file {0} could not be read.An ISPFCOMMAND tool failed to receive parameters from the parameter file after the remote function wasexecuted.

User Response: Check your network connection to the server.

Error messages | 65


• Check if the parameter data set exists and can be read.• Check if the user has RACF authority to read the parameter file data set.

TSMVS0009 Invalid input parameter configuration:Parameter From = {0} .The "Parameter_From" attribute of an input parameter of a ISPFCOMMAND tool descriptor was set to anunsupported value.


Change the "Parameter_From" attribute of the corresponding inputparameter either to "Context" or "Previous_Tool".

TSMVS0010 Wrong format for return code of tool {0}{1}{2} .The called ISPFCOMMAND tool did not return a return code in the expected format. In most cases, the toolreturns an (error) message instead, which will then be printed at the end of the message.


• Check whether the corresponding tool received the correct parameters from theclient. This can be done by debugging the remote tool itself or enabling the clienttrace. If the parameter values are not as expected, correct both action descriptorand tool descriptor definitions in the model.

• Debug the corresponding tool on the z/OS.

TSMVS0011 The return code {0} of tool {1} exceeds themaximum return code of {2} .An ISPFCOMMAND tool returned a return code that is higher than the configured maximum return code(Max_RC) configured in the model. In most cases, the corresponding tool also returns a more specific errormessage that is shown beneath this error message. This can be an expected error situation depending onthe called tool.


• Verify that the action executed by the user was valid. This depends on theapplication modeled. Example: The attempt to delete a data set member that is inexclusive use by another user counts as an invalid action.

• Check if the specific tool received the correct input parameters. If not, check boththe action and tool descriptor definition in the model.

• Debug the ISPFCOMMAND tool.

TSMVS0012 Unexpected return code of tool {0} . Thereturn code was {1} .The return code value of the executed ISPFCOMMAND tool was not numeric.


Verify that the return code values of the specific tool are always numeric andare not led or followed by any other characters.

66 | Error messages

TSMVS0013 Tool {0} returns fewer parameters thanexpected. {1} parameters were detected while {2}parameters were specified for this tool.An ISPFCOMMAND tool returned fewer parameters than defined in its corresponding tool descriptor.


Either correct to tool output or the tool descriptor definition in the model so thatthe modeled output parameters match the actual tool output.

TSMVS0014 Failed to create the job. The {0} statementis expected before line {1} .The client failed to parse the output of an ISPFCOMMAND tool which submitted a job or was executed inbatch because the "JOBPARM: {jobid} {jobname}" statement was missing or in the wrong position.


The JOBPARM statement should be created by the TAUTOIFA REXX procedureshipped with the product. If no customizations were made to that procedure, aninternal error has occurred. Contact SupportLine.

TSMVS0015 Failed to parse the out parameter DSN forjob {0} : {1} .The client failed to parse the output of an ISPFCOMMAND tool which submitted a job or was executed inbatch because the JOBOUTPARMDSN statement was missing.


The JOBOUTPARMDSN statement should be created by the TAUTOIFA REXXprocedure shipped with the product. If no customizations were made to thatprocedure, an internal error has occurred. Contact SupportLine.

TSMVS0016 Failed to parse Job ID and name: {0} .The client failed to parse the output of an ISPFCOMMAND tool which submitted a job or was executed inbatch because the "JOBPARM: {jobid} {jobname}" statement was either missing or invalid.


The JOBPARM statement should be created by the TAUTOIFA REXX procedureshipped with the product. If no customizations were made to that procedure, aninternal error has occurred. Contact SupportLine.

TSMVS0023 An error occurred while parsing the errorfeedback file.A general error occurred when the integrated tool "ErrorFeedback" tried to parse the error feedback XMLfile. This can have several reasons:

• General connection problem.• The given file is not a valid XML file.• The Java XML parser encountered an internal problem.

User Response: Check your connection to the remote system (if available). Note that the errorfeedback XML file is not necessarily located on a remote system.

Error messages | 67


Verify that the file input parameter of the corresponding tool descriptor points tothe correct XML file.


Determine why the XML file seems to be invalid by debugging the tool whichshould create the XML file.

TSMVS0024 Missing file name for file descriptor {0} .A remote file could not be read because no file name was found for a modeled file descriptor.


If the file name should be returned from a modeled tool, check why the file name wasfound in the tool which caused the error message. In this case the "Parameter_From"attribute of the file input parameter must be set to "Previous_Tool". The tool whichreturns the file name must be called before the tool which requires the file name. If thefile name should not have been returned by a tool, the "Name_Physical" attribute ofthe file descriptor needs to be defined in the model.

TSMVS0025 The file {0} contains fewer values thanconfigured properties.The parsed file contains fewer values per line than Properties defined in the corresponding file descriptor.


Either change the creation of the file (or the file itself if it is not created dynamically)or the corresponding file descriptor in the model so that the number of values perline match the modeled properties of the file descriptor.

TSMVS0026 The given error feedback XML file couldnot be parsed because the PACKAGE element was notfound.The given error feedback XML file for the integrated tool "ErrorFeedback" was invalid because no"PACKAGE" element was found.


• Verify that the file input parameter of the corresponding tool descriptor points tothe correct XML file.

• Check why the XML file seems to be invalid, by debugging the tool whichcreates the XML file.

TAURUS user interface (TSUIN) messages

TSUIN0001 The file {0} has been changed\n\nDo youwant to save your changes before performing a localsyntax check?This is a confirmation dialog message.

User Response: Reply OK or Cancel.

68 | Error messages

TSUIN0002 Exception when trying to add a new filter.The new filter action failed with an exception.


TSUIN0003 Error opening view {0} .The filter view could not be opened.

User Response: Open the filter view from the Eclipse Menu Bar: Window --> Show View --> Other... -->Micro Focus Team Developer --> Team Developer Filter View and retry.

TSUIN0004 Error resolving filter.The filter action failed with an exception.



TSUIN0005 Interruption resolving filter.The filter action was interrupted.


TSUIN0006 Exception when trying to get resource {0} .When an application is loaded, all files which were open at the time when the application was unloaded willbe re-opened in the editor based on the information in the cache. For the given element, the re-open failedbecause no entry could be found in the cache. Most probably the cached information is inconsistent.

User Response: Remove the file ft_openfiles.xml from the application folder in the internal project folder.See Troubleshooting for more information on how to remove the cached information.

TSUIN0007 Failed to re-open an editor from theresource: {0} .When an application is loaded, all files which were open at the time when the application was unloaded willbe re-opened in the editor based on the information in the cache. For the given element, the re-open failedbecause no entry could be found in the cache. Most probably the cached information is inconsistent. Theworkspace may have been switched between unload and load of the application.

User Response: Remove the file ft_openfiles.xml from the application folder in the internal project folder.See Troubleshooting for more information on how to remove the cached information.

TSUIN0008 The output file {0} could not be opened.Opening the given file in the editor failed.

User Response: See the message under "Reason:" in the message dialog.

Error messages | 69

TSUIN0009 Opening editor for file {0} was interrupted.Opening the given file in the editor was interrupted.


TSUIN0010 No application active. Please load one.An attempt was made to open an output file when no AWM application was loaded.

User Response: Load the corresponding AWM application and try the action again.

TSUIN0011 Failed to open the internal project whileallocating the output file.The internal project folder could not be opened for the creation of an output file.



Check the error log for more information. If necessary, contact SupportLine.

TSUIN0012 Could not open the editor.An attempt was made to open an output file in the editor; but the editor cannot be opened.

User Response: See the message under "Reason:" in the message dialog. If necessarycontact the administrator.



TSUIN0013 Compare failed while trying to get the filecontent.An I/O exception occurred during the compare action reading the files to be compared.

User Response: See the message under "Reason:" in the message dialog. If necessary,contact the administrator.



TSUIN0014 Compare failed due to an I/O error.An I/O exception occurred during the compare action reading the files to be compared.




70 | Error messages

TSUIN0016 Failed to execute the integrated toolEditOpener. The file descriptor {0} must be aworkspace file descriptor.The execution of the integrated tool EditOpener failed because the file descriptor was not declared as typeworkspace file descriptor.


Verify the type of the file descriptor associated as input parameter with theintegrated tool EditOpener. The file descriptor must be of type Workspace_File.

TSUIN0017 File does not exist.The file to be opened in the editor could not be found in the workspace on the expected path. A possiblecause is that the workspace was switched since the last edit of the file.


TSUIN0018 Failed to retrieve the editor (IEditorPart) forthe opened file. Save- and close-operations will notwork properly. {0} If an external editor was opened, youshould check your file associations (Eclipsepreferences).The editor which should be used to open the selected file could not be determined. The consequence isthat save and close actions won't work properly. Probably there is a file association missing for this file'sextension in the Eclipse preferences.

User Response: Verify that the file association is set correctly for the file's extension in the Eclipsepreferences. If not, add a file association for the extension. Otherwise see themessage under "Reason:" in the message dialog. If necessary contact theadministrator.



TSUIN0019 Interrupted exception while waiting forplatform UI initialization.The platform UI initialization process was interrupted.


TSUIN0021 Failed to find the local file for Element {0} .The file for the given element to be opened in the editor could not be found in the workspace at theexpected path. The workspace may have been switched since the last edit of the file.


Error messages | 71

TSUIN0024 An error occurred when trying to load thefile ft_openfiles.xml.Files which are open locally when an application is unloaded are persistently stored in the workspace fileft_openfiles.xml. This file could not be loaded when the application is loaded again. The workspace mayhave been switched between unload and reload of the application.

User Response: If the files need not be opened again, ignore the message. Otherwise, if the causeis a workspace switch, change the workspace back. If this does not help, see themessage under "Reason:" in the message dialog. If this does not help either,contact the administrator.



TSUIN0025 An error occurred when trying to save thefile ft_openfiles.xml.All files which are open locally when an application is unloaded are persistently stored in the workspace fileft_openfiles.xml. This file could not be saved in the workspace.




TSUIN0026 CoreException during save action.A modeled save action was executed when a file was saved. This save action failed.



TSUIN0027 Failed to open the view with the ID {0} .The opening of one of the Team Developer views failed.


TSUIN0028 Active editor contents can only be obtainedfrom ITextEditors.An action tried to read the content of the active editor (e.g. an action using the editor content to submit it asa job). This is only possible if the editor is a text editor.

User Response: If possible, change the type of the edited file to a type which is opened with a texteditor.

TSUIN0029 Failed to close open editors.When the workbench is shut down, all open remote AWM files are closed. This close failed.

72 | Error messages

User Response: Determine why the close of the files failed. Ensure that close actions which were notexecuted are processed manually (e.g. unlock a member in the SCM system).

TSUIN0030 Exception occurred when saving theelement information.When an application is unloaded or the Eclipse workbench is closed, the AWM elements are storedpermanently in the workspace. This element's save action has failed. When the element information cannotbe saved, no element lists for this application can be restored in the next Eclipse session.

User Response: See the message under "Reason:" in the message dialog. If this doesn'thelp, contact the administrator.



TSUIN0031 Configuration error: The tool descriptor {0}needs a ISA PlugIn attribute, because its tool type is{1} .The given tool which is configured as a UI tool (SWTDIALOG) doesn't have an ISA_PlugIn relationattribute.


Add the required ISA_PlugIn relation attribute to the given tool in themodel file.

TSUIN0032 The plug-in ID {0} for tool descriptor {1} isinvalid for the tool type {2} .The given tool descriptor contains an invalid plug-in ID for the given tool type in the ISA_PlugIn relationattribute. Permitted plugin IDs for tools of tool type SWTDIALOG are "de.soforte.taurus.inputdialog" or"de.soforte.taurus.outputdialog".


Correct the plug-in ID for the given tool in its ISA_PlugIn relation attribute.

TSUIN0033 Missing file input parameter for integratedtool EditOpener.The integrated tool EditOpener needs an input parameter of type file. This input parameter is missing.

Model Administrator Response: Add the missing file input parameter to the integrated tool EditOpener.

TSUIN0034 The file input parameter for the EditOpenercontains no physical name.In the file input parameter for the integrated tool EditOpener, the value for the attribute "physical name" ismissing.

Error messages | 73


Add the physical name in the file input parameter of the integrated toolEditOpener in the model file.

TSUIN0036 The action has been interrupted.The current action has been interrupted by the user.

User Response: Try the action again.

TSUIN0037 Failed to delete cached files.The deletion of the file cache failed during the execution of the Clear Cache action for an application.

User Response: • See the message under "Reason:" in the message dialog.• See Troubleshooting for more information on how to delete the cache.

TSUIN0038 Exception when trying to get the value forproperty {0} .The value for a property which is part of a table within a dialog could not be determined.


TSUIN0039 Please insert a filter name.A filter definition always needs a filter name. The filter name is empty.

User Response: Enter a name for the filter.

TSUIN0040 Exception when trying to get theapplication folder.The application folder within the internal project folder could not be determined.

User Response: See the message under "Reason:" in the message dialog. SeeTroubleshooting for more help. If necessary, contact the administrator.



TSUIN0041 Core Exception when trying to read the jobcard file.The file which contains the user specific job card settings could not be read from the internal project folderin the workspace.




74 | Error messages

TSUIN0042 IO Exception when trying to read the jobcard file.The file which contains the user specific job card settings could not be read from the internal project folderin the workspace.




TSUIN0043 Exception when trying to write the job cardfile.The values obtained from the job card dialog could not be written to the file which contains the user specificjob card settings in the internal project folder in the workspace.




TSUIN0044 Core Exception when trying to write the jobcard file.The values obtained from the job card dialog could not be written to the file which contains the user specificjob card settings in the internal project folder in the workspace.




TSUIN0045 IO Exception when trying to write the jobcard file.The values obtained from the job card dialog could not be written to the file which contains the user specificjob card settings in the internal project folder in the workspace.




TSUIN0047 Failed to retrieve values for Property {0} .The retrieve tool for the given property failed.

Error messages | 75



Verify that the retrieve tool is correctly implemented and configured in themodel file. Check the error log for more information.

TSUIN0048 Failed to resolve dependent valuereferences.Property dependent values were modeled in the "Value_Keys" attribute of a Select_Value Property butcould not be resolved.


Verify that the Value_Keys of the corresponding property are modeledcorrectly.

TSUIN0049 Error while reading the output file {0} .A file destined for an output dialog could not be read.


• Verify that the corresponding tool executed before the output dialog returns thefile name correctly.

• Enable the client trace and verify that the returned file name is mapped to thecorrect file output parameter.

• Verify that the user has read access to the file.

TSUIN0050 Output file not found in parameter memory:{0} .A file descriptor for a file output field (output dialog) was not found. This may be caused by a tool executorwhich did not save an output parameter correctly into the parameter memory. This is an internal problem ifno custom tool executor (tool type) was used.


TSUIN0051 Unable to set a value for output field {0} .A property for an output field (output dialog) was not found. This may be caused by a tool executor whichdid not save an output parameter correctly into the parameter memory. This is an internal problem if nocustom tool executor (tool type) was used.


TSUIN0052 Input file for parameter {0} could not beretrieved.A file input parameter with the attribute "Parameter_From = Previous_Tool" was modeled for an InputDialog but the file descriptor was not found in the parameter memory.

Model Administrator Response: Verify that the action is modeled correctly (see Troubleshooting).

76 | Error messages

TSUIN0053 No properties defined for file descriptor{0} .A file input parameter was modeled for an input dialog which refers to a file descriptor with the attribute"Structure = Table". There are no properties defined for the file descriptor.


Add "has Property" relationships to the corresponding file descriptor or setits "Structure" attribute to "Unstructured".

TSUIN0054 Input file for selection table was not found.There is a file input parameter declared as input for a dialog table. The file with the content for the tablecould not be determined. This is probably a modeling error.


Verify that the corresponding file descriptor has the correct type and optionally thecorrect physical name. See the information about modeling problems inApplication Workflow Manager Problem Determination for further helpful hints.

TSUIN0055 Input file for selection table could not beread.There is a file input parameter declared as input for a dialog table. The file with the content for the tablecould not be read. This might be a modeling error.


Verify that the corresponding file descriptor has the correct type and optionally thecorrect physical name. See the information about modeling problems inApplication Workflow Manager Problem Determination for further helpful hints.

TSUIN0057 Value for property {0} not found.There is a file input parameter declared as input for a dialog table. At least one line of the file content doesnot deliver a value for every property associated with the file descriptor.


Verify the output file of the tool delivering the content for the dialog table. Ensurethat the tool delivers at least as many values as properties are configured for thefile descriptor.

TSUIN0058 Missing attribute in global editor action:Keyword.A global action with an ISA_Editor_Action relation defined in the model file has aSelectionProppertyMapping relation assigned with ValueFrom set to SelectedKeyword. But the value of thekeyword is not set.


Set the value of the attribute Keyword in the global editor action'sSelectionPropertyMapping relation (e.g. COBOL-COPYBOOK).

TSUIN0059 Failed to parse key word for editor action.There is a global action with an ISA_Editor_Action relation defined in the model file. ASelectionPropertyMapping relation is assigned to this editor action with ValueFrom set to

Error messages | 77

SelectedKeyword. The value under the Keyword attribute in the SelectionPropertyMapping relation doesnot have the expected format.


Correct the value in the Keyword attribute of the SelectionPropertyMappingrelation. Correct values are: COBOL-COPYBOOK, COBOL-INCLUDE or PLI-INCLUDE.

TSUIN0060 Failed to save the column configurations.When an application is unloaded or the Eclipse workbench is closed, the column settings for the TableView are stored in the local workspace. This save action failed.




TSUIN0061 Failed to save the column configurations.When an application is unloaded or the Eclipse workbench is closed, the column settings for the TableView are stored in the local workspace. This save action failed.




TSUIN0062 Failed to load the column user settings.When an application is unloaded or the Eclipse workbench is closed, the column settings for the TableView are stored in the local workspace. When the application is loaded again, the column settings arerestored from this saved file. The restore of the column settings failed.




TSUIN0063 Error resolving filter.The refresh button was pressed in the Table View on an element list created by a filter. This caused thefilter action to be called. The filter action failed.

User Response: Verify if there is a network problem. See the message under "Reason:" in the messagedialog. If this doesn't help, contact the administrator.

TSUIN0064 Interruption exception while resolving filter.The refresh button was pressed in the Table View on an element list created by a filter. This caused thefilter action to be called, which was interrupted by the user.


78 | Error messages

TSUIN0066 Failed to open the file {0} .When an entry in the Team Developer Error List View is double-clicked, the corresponding source membershould be opened in the editor. The open of the file failed.

User Response: Verify that the Location and Resource entry in the Error List View point to thelocation of the source member. If this is not the case, it might be an error in theerror feedback tool. In this case, contact the administrator.


Verify that the error feedback tool returns the correct location of the sourcemember. Check the error log for more information.

TSUIN0067 Found a matching editor ( {0} ) but failed toopen it.When an error feedback entry is double-clicked, the editor for the corresponding source file should beopened. The editor associated with the file type could be determined, but the open failed.

User Response: Verify if the correct file association is defined for the source member in theEclipse preferences. See the message under "Reason:" in the message dialog.If necessary, contact the administrator.



TSUIN0068 Failed to retrieve the physical file of editor{0} .When an error feedback entry is double-clicked, the editor for the corresponding source file should beopened. Opening of the editor failed.




TSUIN0069 Failed to set markers for the file {0} .When an error feedback entry is double-clicked, the editor for the corresponding source file should beopened and the syntax errors marked with editor markers. The setting of the editor markers failed.




TSUIN0070 An error occurred while trying to reload thefilters.When an application is loaded, the filter information of the application is reloaded from the cache in theworkspace. This reload failed.

Error messages | 79




TSUIN0071 Exception when trying to remove a filter.The remove action on a filter failed with an exception.




TSUIN0072 Error opening view {0} .When a filter is executed, the Element Table View is opened to display the result of the filter action. Theopening of the Element Table View failed.


TSUIN0073 Exception when trying to add a new filter.A filter which is defined by the user is added to the internal filter list. The new filter list is stored into theuser's cache in the workspace. This add filter action ended with an exception.




TSUIN0074 An error occurred while trying to save thefilters.When an application is unloaded or the Eclipse workbench is closed the filter information is stored into theuser's workspace. The save of the filters failed.




TSUIN0077 Exception when trying to load the job list.When the Job View is initiated, the job list input is loaded from the cache in the workspace. This load failed.




80 | Error messages

TSUIN0078 Exception when trying to get the job parts.When the Go Into action is selected on a job in the Job View, the parts of the job (DDs) are retrieved fromthe remote system. This retrieve failed.

User Response: See the message under "Reason:" in the message dialog. Check if the jobstill exists on the remote system. If necessary, contact the administrator.



TSUIN0079 No extension found for job utility.The job utility is integrated by the Eclipse extension point de.soforte.taurus.jobutil. No extension for thisextension point could be found.


If the job utilities are integrated by a customer extension, verify that theextension point id is spelled correctly in the plugin.xml. Otherwise contactSupportLine.

TSUIN0081 Exception when trying to save the jobinformation.When an application is unloaded or the Eclipse workbench is closed, the job information is stored into theuser's workspace. The save of the job information failed.




TSUIN0082 Exception when trying to load the job list.When an application is loaded, the job information of the application is reloaded from the cache in theworkspace. This reload failed.




TSUIN0084 Exception when trying to synchronize thejob information.The refresh action in the Team Developer Job View failed with an exception.

User Response: Verify if there is a network problem. See the message under "Reason:" inthe message dialog. If necessary, contact the administrator.



Error messages | 81

TSUIN0085 Exception when trying to browse a job withthe ID {0} .The browse of the given job failed.




TSUIN0086 Invalid object given: {0} .This is an internal exception. A message has been called with an object with an invalid type.


TSUIN0087 Failed to get children for {0} .An exception occurred when a branch was expanded in the Tree View.



Check the server logs for more information. Validate that the modeledGetChildren action for the corresponding element type works correctly.

TSUIN0088 An error occurred while searching forWorkflow Manager applications.An exception occurred when a system reference was expanded in the Tree View.



Check the server logs for more information. Validate that the REXXTAULAPPL and TAUZCAPP respectively work correctly.

TSUIN0089 The following tool messages were returnedduring the action:This is a summary of all tool messages which were issued by one of the tools which were executed whenthe last action was performed.

User Response: Check the tool responses.

TSUIN0090 No extension found for job utility.The job utility is integrated via an Eclipse extension point. No extension for this extension point was foundin the workbench.


If the job utility is integrated using a customer written extension, verify that theextension point ID (de.soforte.taurus.jobutil) is correctly spelled in the extensiondefinition. Otherwise contact SupportLine.

82 | Error messages

TSUIN0091 Failed to delete cached jobs.During the execution of the Clear Cache action for an application, the deletion of the job cache failed.

User Response: • See the message under "Reason:" in the message dialog.• See Troubleshooting for more information on how to delete the cache.

TSUIN0092 Failed to reset the dirty flag of the editor.The save of an edited file failed, as did the reset of the dirty flag of the editor.

UserResponse:

Temporarily save the changes in the editor so that they are not lost (e.g. by cutting/pasting the editor contents into a temporary local file). Determine why the edited filecould not be saved.

TSUIN0093 Failed to create a backup for file {0} .The save of an edited file failed, as did the backup of the recovery file.

UserResponse:

Temporarily save the changes in the editor so that they are not lost (e.g. by cutting/pasting the editor contents into a temporary local file). Determine why the edited filecould not be saved.

TSUIN0094 Failed to save the member: {0} . A backupwas made at: {1} .Saving an edited file failed. Therefore a backup of the file was written to the named path.

User Response: Determine why the save of the file failed.

TSUIN0095 The date format {0} of property {1} isinvalid.A date format attribute of a property in the model contains an invalid value.

Model Administrator Response: Correct the date format attribute of the property in the model.

TSUIN0096 No target ID for the validate actiondescription of tool {0} .The validation action which is associated with the tool descriptor {0} does not have a target ID.

Model Administrator Response: Check the model configuration (see description).

Error messages | 83

TSUIN0098 The first file input parameter of theintegrated tool FileCompare with the ID {0} must be oftype MVSSEQ or MVSPO_MEMBER orWORKSPACE_FILE.Self-explanatory.

Model Administrator Response: Check the model configuration (see Message).

TSUIN0099 Failed to execute the integrated toolFileCompare. The first file descriptor {0} must be aworkspace file descriptor or the EDIT flag must be setto false.The execution of the integrated tool FileCompare failed because the file descriptor was not declared astype workspace file descriptor.


Verify the type of the file descriptor associated as input parameter with theintegrated tool FileCompare. The file descriptor must be of typeWorkspace_File.

TSUIN0100 The integrated tool FileCompare with the ID{0} must have exactly two file input parameter but only{1} were found.The integrated tool FileCompare must be modeled with exactly two file input parameters. There were moreor fewer file input parameters found for the integrated tool FileCompare.


Correct the input parameters for the integrated tool FileCompare in themodel file.

TSUIN0101 The integrated tool FileCompare with the ID{0} must have two modelled file input parametersunless it is modelled within a mass processing actionwith two selected elements, in which case one fileinput parameter is required.A "FileCompare" integrated tool was not properly modeled.


Either model the "FileCompare" tool descriptor with two file input parameters anduse it within a single processing action descriptor ("MassProcessing = false"), ormodel a single file input parameter and use the tool in a mass processing actiondescriptor ("MassProcessing = true").

84 | Error messages

TSUIN0102 The integrated file compare tool {0}requires two selected resources in order to work in amass processing action, while only {1} resources werefound in the context.A FileCompare tool descriptor was modeled for a multi selection (e.g. "Compare With Each Other") but onlyone resource was selected during execution.


Add a enabled condition to the "Element has Action" relationship in which the tooldescriptor is being called and set the "Selection Count" attribute of the conditionto "2".

TSUIN0103 The integrated tool FileCompare wasmodelled incorrectly. Either two file input parametersmust be modelled or the tool must be called within amass processing action with exactly one modelled fileinput parameter. {0} Modelled file input parameters: {1}{0} Mass processing: {3}A "FileCompare" integrated tool was not properly modeled.


Either model the "FileCompare" tool descriptor with two file input parameters anduse it within a single processing action descriptor ("MassProcessing = false"), ormodel a single file input parameter and use the tool in a mass processing actiondescriptor ("MassProcessing = true").

TSUIN0104 Failed to restore the {0} . viewA Team Developer view could not be restored. This is most probably caused by an internal exception.

User Response: Try to open the view manually (Window -> Show View...). If this does nothelp clear your cache and restart the client.


Contact SupportLine.

TSUIN0105 Execution of save action {0} failed with anexception.The execution of a modeled save action (action descriptor attribute) failed with an exception. This is a toplevel exception, additional information (exceptions) should be printed

Model Administrator Response: Check the error log for a more specific error message.

Error messages | 85

TSUIN0106 Table views could not be cached. Failed tosave tv_tableviewlists.xml.The state of opened AWM table views could not be saved. This can be caused by an asynchronous Eclipsework space.

User Response: Refresh the internal application folder.

TSUIN0107 Cached table views (tv_tableviewlists.xml)could not be recovered.Failed to load the cached state of AWM table views. This can be caused by an asynchronous Eclipse workspace.

User Response: • Refresh the internal application folder.• Delete the tv_tableviewlists.xml cache file manually from the internal application

folder.

TSUIN0108 A thread was interrupted while initializingthe element lists.This is an internal program exception which can occur while the cached state of AWM table views is beingloaded.


TSUIN0109 Failed to expand the system reference {0} .The expand state of a cached system reference could not be restored after the client was restarted. Thiswas most probably caused by a model update or an inconsistent model.

User Response: Restart the client to see if the error occurs a second time. If it does, delete and re-addthe system from the tree view.

TSUIN0110 Failed to update the application {0} .This is a high level exception which occurs if updating the model of an application fails. Possible reasonsinclude:

• The application could not be loaded with the new model (e.g. the model is invalid).• The application could not be unloaded (e.g. cache could not be saved). A more detailed exception

should be found in the error log.

User Response: • Check the error log for a more detailed exception.• Clear your cache and try to update your model manually (both context menu

functions of the application in the Tree View).


• Verify that the new model is valid and can be loaded by clients.• Verify that the model is compatible with the Workflow Manager version of the

client.

86 | Error messages

TSUIN0111 Failed to create a system reference.An exception occurred during the creation of a system reference. Since this is a top-level exception, moredetails are usually to be found in the error details. Possible reasons are:

• The internal project has become asynchronous to Eclipse.• The client installation is inconsistent (conflicting plug-ins).• A master configuration could not be received or parsed.

User Response: • Open the Navigator view and refresh the internal project (right click -> Refresh)and retry the action.

• If the problem appears to be related to the remote system connection, verify yournetwork connection to the specific system and check your connection definition(host name, port). Model administrator response: If the problem appears to havebeing caused while the Master Configuration was been parsed, verify theconfiguration itself and correct any inconsistencies. Usually a more detailedmessage can be found among the error details.


If the master configuration file is provided by a remote system, verify that the server isup and running correctly. Verify that all customization steps in the server InstallationGuide concerning the location and customization of the Master Configuration file aredone correctly.

TSUIN0112 Exception when trying to refresh thesystem.The system reference could not be refreshed properly, meaning that the underlying applications could notbe updated by reading the corresponding master configuration. A more detailed exception can usually befound in the error details.

User Response: If the target system is remote, check your network connection and configurationin the client (host name, port).


Verify that the master configuration for the corresponding system is valid.


If the master configuration file is provided by a remote system, verify that theserver is up and running correctly. Verify that all customization steps in theserver Installation Guide concerning the location and customization of theMaster Configuration file are done correctly.

TSUIN0113 Failed to associate a remote system.Associating a remote system to a local system reference failed. This is most probably caused by a corruptclient installation (Eclipse plug-in problems).

User Response: Restart the client with the -clean option and retry the action.


TSUIN0114 An error occurred while storing thecontainers.The current state of the Tree View could not be saved into the cache. The reason for this is most likelyEclipse being out of sync with the local file system.

Error messages | 87


Refresh the internal project from the Navigator View and restart the client. Ifthe problem still occurs, contact SupportLine.

TSUIN0115 Failed to expand the Tree View to itsprevious state.The Tree View could not be expanded to its previous state after Eclipse was restarted. Possible reasonsare:

• Corrupt cache files.• Inconsistent model.• Asynchronous Eclipse workspace.• Internal exceptions.

User Response: Expand the Tree View elements manually.


• Check the error log for more information.• Verify that all Element Types and ID definitions in your models are

consistent.• Contact Customer Support.

TSUIN0116 Failed to expand the system {0} .An internal error occurred while the Tree View was being refreshed.


TSUIN0117 Following z/Server processes are stillrunning: {0}{1}{0} Please close these processes first.Loading an application failed because certain processes are still being executed in the active application.

User Response: Close the cited processes and retry loading the application.

TSUIN0118 Exception occurred when trying to load theapplication.The selected application could not be loaded. A more accurate message can usually be found in the errordetails.

User Response: If the model for the application is located on a remote system:

• Check your network connection.• Check the settings of the remote system connection (host name, port).• Check if your code page settings (including file mappings) for the remote

system connection are correct.


• Verify that the application was defined correctly in the master configuration.• Verify that the model for the application is located on the defined path in the

master configuration.

88 | Error messages


If the model for the application is located on the remote system, verify that the userhas read access for that file.

TSUIN0119 The local file {0} doesnt exist.The local file with the given path could not be found on the system.


• If the file's path was derived from a file descriptor in the model, verify that thevalue in the attribute "Name_Physical" is correct.

• If the file path is returned by a modeled tool, verify that the tool returns thecorrect path name.

TSUIN0120 Compare failed while trying to set the filecontentAn I/O exception occurred during the compare action setting the content of the files to be compared.




TSUIN0121 Failed to delete the element list {0} .This is a top-level exception that will be printed into the error log if any exception occurs during delete of aelement list. A more detailed error message can usually be found in the error details.

Model Administrator Response: Check the error details for more information.

TSUIN0122 Failed to get children forAn error occurred during the execution of a "get children" action. The ID of the parent resource of theaction will be dynamically added to the message at runtime. This is a top level exception, more details aremost probably provided in the error dialog.


TAURUS user interface views (TSUIV) messages

TSUIV0002 Failed to expand the system reference {0} .The expand state of a cached system reference could not be restored after the client was restarted. Thiswas most probably caused by a model update or an inconsistent model.

User Response: Restart the client to see if the error occurs a second time. If it does, delete and re-addthe system from the tree view.

Error messages | 89

TSUIV0003 Exception during back up of application{0} .The backup action of your active application failed.

User Response: Backup the files of your active application manually.

TSUIV0004 Failed to create a system reference.An exception occurred during the creation of a system reference. Since this is a top-level exception, moredetails are usually to be found in the error details. Possible reasons are:

• The internal project has become asynchronous to Eclipse.• The client installation is inconsistent (conflicting plug-ins).• A master configuration could not be received or parsed.

User Response: • Open the Navigator view and refresh the internal project (right click -> Refresh)and retry the action.

• If the problem appears to be related to the remote system connection, verify yournetwork connection to the specific system and check your connection definition(host name, port).


If the problem appears to have been caused while the Master Configuration wasbeing parsed, verify the configuration itself and correct any inconsistencies. Usuallya more detailed message can be found among the error details.


If the master configuration file is provided by a remote system, verify that the serveris up and running correctly. Verify that all customization steps in the serverInstallation Guide concerning the location and customization of the MasterConfiguration file are done correctly.

TSUIV0005 Exception when trying to refresh thesystem.The system reference could not be refreshed properly, meaning that the underlying applications could notbe updated by reading the corresponding master configuration. A more detailed exception can usually befound in the error details.

User Response: If the target system is remote, check your network connection and configurationin the client (host name, port).


Verify that the master configuration for the corresponding system is valid.


If the master configuration file is provided by a remote system, verify that theserver is up and running correctly. Verify that all customization steps in theserver Installation Guide concerning the location and customization of theMaster Configuration file are done correctly.

TSUIV0006 Failed to associate a remote system.Associating a remote system to a local system reference failed. This is most probably caused by a corruptclient installation (Eclipse plug-in problems).

90 | Error messages

User Response: Restart the client with the -clean option and retry the action.


TSUIV0008 An error occurred while storing thecontainers.The current state of the Tree View could not be saved into the cache. The reason for this is most likelyEclipse being out of sync with the local file system.


Refresh the internal project from the Navigator View and restart the client. Ifthe problem still occurs, contact SupportLine.

TSUIV0009 Failed to expand the system {0} .An internal error occurred while the Tree View was being refreshed.


TSUIV0010 Following z/Server processes are stillrunning: {0}{1}{0} Please close these processes first.Loading an application failed because certain processes are still being executed in the active application.

User Response: Close the cited processes and retry loading the application.

TSUIV0011 Exception occurred when trying to load theapplication.The selected application could not be loaded. A more accurate message can usually be found in the errordetails.

User Response: If the model for the application is located on a remote system:

• Check your network connection.• Check the settings of the remote system connection (host name, port).• Check if your code page settings (including file mappings) for the remote

system connection are correct.


• Verify that the application was defined correctly in the master configuration.• Verify that the model for the application is located on the defined path in the

master configuration.


If the model for the application is located on the remote system, verify that the userhas read access for that file.

TSUIV0012 Failed to expand the Tree View to itsprevious state.The Tree View could not be expanded to its previous state after Eclipse was restarted. Possible reasonsare:

Error messages | 91

• Corrupt cache files.• Inconsistent model.• Asynchronous Eclipse workspace.• Internal exceptions.

User Response: Expand the Tree View elements manually.


• Check the error log for more information.• Verify that all Element Types and ID definitions in your models are

consistent.• Contact Customer Support.

TSUIV0013 Failed to update the application {0} .This is a high level exception which occurs if updating the model of an application fails. Possible reasonsinclude:

• The application could not be loaded with the new model (e.g. the model is invalid).• The application could not be unloaded (e.g. cache could not be saved). A more detailed exception

should be found in the error log.

User Response: • Check the error log for a more detailed exception.• Clear your cache and try to update your model manually (both context menu

functions of the application in the Tree View).


• Verify that the new model is valid and can be loaded by clients.• Verify that the model is compatible with the Workflow Manager version of the

client.

zExplorer for z/Server (TSXZS) messages

TSXZS0001 Failed to load XML file containing defaultconnections.The XML file containing default z/Server connection definitions could not be loaded properly. The file isnamed "defaultZConnections.XML" and is located in the Eclipse root folder.

Model Administrator Response: • Verify that the file can be read by the user.• Open the file in an (XML) editor and correct any syntax errors.• Delete the file if it is not required.

TSXZS0002 {0} is not a valid MVS resource name.Failed to parse a data set name from the passed MVS resource name. This is an internal problem.


92 | Error messages

TSXZS0003 No file descriptor found for data set list.A data set list could not be created because the file descriptor defining the list was not found. This is aninternal error that may have been caused by the zExplorer model not being loaded correctly.

User Response: • Retry the action.• Reconnect and retry the action

.


• Verify that the z/Server EXEC library (containing the TAUZCAPP procedure) isin the SYSEXEC concatenation of the user server.

• If the zExplorer model was customized, determine the problem in thecustomized model. Contact Customer Support if necessary.

TSXZS0004 Failed to decrypt the saved password foruser {0} .Failed to decrypt a stored password. The password was stored, because the user checked the "Savepassword" check-box in the "Enter password" dialog.


TSXZS0005 Failed to save the password (encryptionproblem).Failed to encrypt and save a password. The password was supposed to be saved because the user hadchecked the "Save password" check-box in the "Enter password" dialog.


TSXZS0006 Connect to {0} :{1} was not successful.The connection to the z/Server could not be established. This is a top-level exception, which means that amore detailed error message can usually be found in the error details. Possible reasons are:

• Network problems (the host cannot be reached).• RACF error (wrong password, user not authorized, etc.).• User cancelled the "Enter password" dialog. - z/Server problems.• Problems while calling the TAUZCAPP procedure.

User Response: • Check your network connection.• Verify that a valid user name and password were entered.


• Verify that the TAUZCAPP REXX procedure returns a master configurationproperly.

• Verify that the returned master configuration file is valid.


• Verify that the z/Server is up and running.• Check the z/Server log for more information.

Error messages | 93

TSXZS0011 User selected Cancel on disconnectdialog.If a user tries to disconnect from the z/Server while MVS edit sessions are still open in the client, aconfirmation dialog will come up to warn the user that the editor(s) will be closed before disconnecting. If auser selects "Cancel" in this dialog, the disconnect action will be aborted and this message written into theerror log.

UserResponse:

No user action is required since cancelling the disconnect action was probably intended.If not, close any open (non-local) editor or disconnect again and press "OK" in theconfirmation dialog. Unsaved changes can still be changed (individual confirmationdialogs will open).

TSXZS0012 Failed to properly log off from {0} :{1} . Youare now disconnected.The client failed to properly disconnect from the z/Server. Possible reasons are:

• The network connection was interrupted.• The user server ended abnormally and did not shut down.• Open edit sessions could not be properly ended. The connection is shown as "disconnected" in the

Remote Systems View. It is possible to (re)connect normally afterwards.


Determine what causes the problem. Check the z/Server logs for moreinformation. Contact SupportLine if necessary.

TSXZS0018 Failed to parse attributes of resource {0} .A z/Server LIST response (LISTDSI for data sets or LISTMEM for members) could not be parsed properly.This message is issued for every data set or member that could not be created.


Look for distinctive features of the resources that could not be parsed orcreated (special characters, attributes, etc.) and contact SupportLine.

TSXZS0022 Directory blocks not numeric for {0} .Failed to determine the number of directory blocks for a data set. This is an internal problem involvingREXX procedure TAUZCLDS.


TSXZS0023 List data set error.An internal error occurred while executing the REXX procedure TAUZCLDS or parsing its results.


TSXZS0025 Element name property missing forelement type {0} .No element name property was modeled for the element type in a zExplorer model. Either the model isincomplete or it was not loaded correctly.

94 | Error messages

User Response: Reconnect to the z/Server and retry the action. Contact the model administrator ifthe problem still occurs.


• Verify that the master configuration for the system contains the "zExpConf"statement. If it does, verify that the referenced model is valid, and configure an"Element_Name" Property for the Element Type.

• If no customized zExplorer model is supposed to be used, remove the attribute"zExpConf" from the master configuration (it is commented out by default).

TSXZS0026 Failed to generate an element ID forelement {0} .An element ID for a zExplorer element type could not be generated successfully. Either the model isincomplete or it was not loaded properly.

User Response: Reconnect to the z/Server and retry the action. Contact the model administrator ifthe problem still occurs.


• Verify that the master configuration for the specific system contains the"zExpConf" statement. If it does, correct any problems concerning the IDdefinitions of the element types.

• If no customized zExplorer model should be used, remove or comment out the"zExpConf" attribute from the master configuration (commented out by default).

TSXZS0027 Only subclasses of MvsResource(MvsDataset, MvsDatasetMember) can be renamed.This problem occurs if the zExplorer API was used incorrectly and should not occur unless the zExplorerwas customized by third party plug-ins.


TSXZS0028 Only subclasses of MvsResource(MvsDataset, MvsDatasetMember) can be refreshed.This problem occurs if the zExplorer API was used incorrectly, and should not occur unless the zExplorerwas customized by third party plug-ins.


TSXZS0029 Converting an outdated application modelfailed.An internal error occurred while a possibly outdated model was being converted. The conversion will beinitiated as soon as the model loader detects syntax errors in the model.


Error messages | 95

TSXZS0030 Failed to load the model configuration file:{0} because it seems to be incompatible with yourclient version.A model could not be loaded or opened completely because it contains syntax errors. Even the modelconversion was not successful.

User Response: Verify that all code page settings are correct (connection properties and filemappings).


Open the model in the model editor and click the Details button next to the textbox containing an error message. All syntax problems for the loaded model arethen listed, including where they occur. Correct the problems manually by editingthe model with a text- or XML editor.

TSXZS0031 Missing type in zExplorer model: {0} .An explicitly required object from the internal z/Explorer model was not found. This may be caused byincorrect customization of the internal model or by a failure to load the model.


If the zExplorer model was customized, determine the problem in thecustomized model. Contact SupportLine if necessary.

TSXZS0032 {0} will be opened in read-only modebecause non-displayable characters were detected.The file to be opened in the editor contains characters that cannot be converted properly using theindicated code page. Write protection is automatically enabled since saving the file back to the mainframewould corrupt its contents.

User Response: Verify that your code page settings (including file mappings) are correct, change them ifnecessary and re-open the file in the editor.

TSXZS0033 File {0} does not exist.An internal problem occurred while opening an MVS file in the editor. The file location is within theworkspace since a temporary copy of the host resource should have been copied there.

Model Administrator Response: Contact SupportLine

TSXZS0034 User selected Cancel on save editordialog.If a user tries to disconnect from the z/Server while MVS edit sessions are still open in the client, aconfirmation dialog will warn the user that the editor(s) will be closed before disconnecting. If the userselects 'OK' in this dialog and the editor(s) contain unsaved changes, individual dialogs will appear for eacheditor, asking whether to save the changes or cancel the disconnect action. If a user selects "Cancel" inone of these dialogs, this message is written to the error log.

User Response: No response required. If selecting 'Cancel' was not intended, the action (disconnectingfrom the z/Server or closing Eclipse) can simply be repeated.

96 | Error messages

TSXZS0035 The file {0} could not be deleted.This is an internal problem. It occurs if the temporary copy of the remote file could not be deleted after theeditor was closed.


TSXZS0036 Failed to save file mappings.An internal error occurred while saving the file mappings into the local cache. This is most likely caused byEclipse being out of sync with the local file system.


Refresh the internal project from the Navigator View and restart the client. Ifthe problem recurs, contact SupportLine.

TSXZS0037 Failed to reload file mappings.An internal error occurred while loading the file mappings from the local cache. This is most likely causedby Eclipse being out of sync with the local file system.


Refresh the internal project from the Navigator View and restart the client. Ifthe problem recurs, contact SupportLine.

TSXZS0042 Failed to create a member list.Failed to create a list of members for an MVS data set. This is an internal error which usually containsmore information in the error details.


If the zExplorer model was customized, determine the problem in thecustomized model. Contact SupportLine if necessary.

TSXZS0043 Changing expired password failed.An attempt to change a user password failed. Reasons could be one of the following:

• Two different passwords were given in the change password dialog.• Invalid characters were used in the new password.• The old password was re-entered instead of a new password.

User Response: Start the dialog again and enter a new valid password.

TSXZS0044 The file {0} could not be unlocked.This problem occurs if a remote file opened in edit mode could not be unlocked after the editor was closed.Typical reasons are network or server problems.

User Response: Check your network and server connection.

Server Administrator Response: Check the server logs for possible problems.

zExplorer subsystem JES (TSXJE) messages

Error messages | 97

TSXJE0001 Job name is missing.The job name is missing for at least one job in the XML response of z/Server for a job list request.


TSXJE0002 Job ID is missing.The job ID is missing for at least one job in the XML response of z/Server for a job list request.


TSXJE0003 An error occured while searching for acustom JesAdapterFactory.This is a top level exception that will be printed into the error log. A more detailed error message canusually be found in the error details.




TSXJE0004 Failed to cancel job {0} .The job with the given ID could not be canceled on the remote z/OS system.

User Response: Verify that the user has the authority to cancel this job.


TSXJE0005 Failed get contents of job {0} .The contents of the given job could not be read from the remote z/OS system.

User Response: Verify that the user has the authority to read this job's contents. If yes,contact the administrator.


Check the z/Server logs and z/OS SYSLOG for more information.

TSXJE0006 Failed to browse job {0} .The given job could not be read from the remote system.

User Response: Verify that the user has the authority to read this job's contents. If yes,contact the administrator.



TSXJE0007 Failed to cancel the job {0} .The given job could not be canceled on the remote system.

98 | Error messages

User Response: Verify that the user has the right to cancel this job.

TSXJE0008 Failed to get job parts.The selected job's parts could not be read from the remote system.

User Response: Verify that the user has the authority to read this job's parts' content. If yes,contact the administrator.



TSXJE0009 Failed to browse job {0} .The given job part's content could not be read from the remote system.

User Response: Verify that the user has the authority to read this job part's content. If yes,contact the administrator.



TSXJE0010 Unexpected return value null fromIJobFacility {0} .A NullPointer exception occurred when determining the job facility class. This is an internal error.


TSXJE0011 Retrieving job information encountered aproblem.The job's meta information could not be read from the remote system.

User Response: Contact the administrator.


zExplorer subsystem MVS (TSXMV) messages

TSXMV0001 An error occurred while searching for acustom MvsAdapterFactory.The extension which extends the extension pointde.soforte.zexplorer.subsystem.mvs.CustomMvsAdapterFactory could not be loaded.


TSXMV0002 Changing password failed.During the change password dialog, an I/O exception occurred. It might be caused by an encryptionproblem (might be a code page problem).

Error messages | 99

Model Administrator Response: • Verify that a valid code page is set for the MVS Explorer settings.• Verify that there is no network problem.• Check the error log for more information.


TSXMV0003 RECALL failed. The data set was notcreated.The creation of a new MVS data set was executed on an existing data set. In this case, the attributes of thenew data set are taken from the attributes of the selected data set. As the selected data set was migrated,it has to be recalled first. This recall failed. Which means that the new data set is not allocated.

User Response: If possible, select another data set as the model data set for the dataset creation.





TSXMV0004 Logoff failed.Logging off the user from z/Server using the hidden command !LOGOFF failed.


TSXMV0005 Failed to set the debug parameter.The call to the REXX TAUZCDBG to set the debug parameter resulted in an I/O exception.


Verify that the z/Server EXEC library is in the SYSEXEC concatenation of theuser server. Check the z/Server logs for more information.

TSXMV0007 Failed to send the following HEXCharacters: {0}{1} .A list of characters is shown that could not be sent to z/Server using the hidden command !SENDHEX.


TSXMV0008 Sending hexes cancelled by user.The hidden action !SENDHEX was canceled by the user.


TSXMV0009 Paste error.The paste action for a z/OS data set failed.


100 | Error messages

TSXMV0010 Severe paste error.The paste action for a z/OS data set resulted in a severe error.






TSXMV0011 Severe error when trying to paste memberlist {0} from {1} .Pasting a list of z/OS partitioned members failed.






TSXMV0012 Severe error when trying to paste member{0} from {1} .Pasting a list of partitioned data set members failed.






TSXMV0013 Severe error when checking memberexistence of {0} in {1} .Pasting a member of a partitioned data set failed.



TSXMV0014 Severe error when trying to paste memberlist {0} from {1} .Pasting a list of z/OS partitioned members failed.

Error messages | 101



TSXMV0015 Data set allocation error.The allocation of a z/OS data set failed.


TSXMV0018 Could not find any z/Server tool with ID{0} .There is no z/Server tool defined for the given tool ID.


If this is a custom z/Explorer model, check the model definition and the plug-incode for the given tool ID. Otherwise contact SupportLine.

TSXMV0019 The z/Server tool {0} needs at least oneinput parameter (data set name).There was no input parameter defined for the tool but it needs at least one.


If this is a custom z/Explorer model, check the model definition and the plug-incode for the given tool ID. Otherwise contact SupportLine.

TSXMV0020 The tool {0} needs exactly one inputparameter (fully qualified data set or member name).It was expected that exactly one input parameter was declared for the tool. The parameter was missing ormore than one input parameter was declared for the tool.


If this is a custom z/Explorer model, check the model and the plug-in code forthe given tool ID. Otherwise contact SupportLine.

TSXMV0021 The z/Server tool {0} needs exactly twoinput parameters (DSN, member filter).It was expected that exactly one input parameter was declared for the tool. The parameter was missing ormore than one input parameter was declared for the tool.



TSXMV0022 The z/Server tool {0} needs exactly one fileoutput parameter ({1} ).It was expected that exactly one file output parameter was declared for the tool. The parameter wasmissing or more than one output parameter was declared for the tool.




TSXMV0023 Getting members of data set {0} failed withmessage: {1}{2} .The members of the given data set could not be retrieved from the remote z/OS system.

User Response: See the included z/Server messages for more details.

TSXMV0024 Invalid filter string.An unsupported filter string was used. Unsupported filter strings are *, % or filter strings starting with *.

User Response: Use a qualifying filter string.

TSXMV0025 Failed to receive files for filter request:{0} .The filter request for the given filter string failed.



TSXMV0026 Getting data sets for filter string {0} failedwith message: {1}{2} .The filter request for the given filter string failed.


TSXMV0027 At least one LISTDSI parser erroroccurred.The parser analysing the response of the LISTDSI request to z/Server detected at least one error in theresponse.


TSXMV0029 Insert of member {0} failed.Adding a member to a z/OS partitioned data set failed.


TSXMV0030 Failed to submit job. No z/OS job supportwas found (implementation of extension point {0} ).The submit of a job failed. Most likely there was no extension for the extension pointde.soforte.zos.JobFacility found.



TSXMV0031 Failed to submit job.The submit of a job failed.

User Response: See the message under "Reason:" in the message dialog. If necessary,contact the model administrator.



TSXMV0032 RECALL failed.The recall of a migrated data set failed.


TSXMV0035 Job submit failed. Failed to find a jobsupport extension.Submit of a job failed. Most likely there was no extension for the extension point de.soforte.zos.JobFacilityfound.


TSXMV0036 Job submit failed.The submit of a job failed.

User Response: See the message under "Reason:" in the message dialog. If necessary,contact the model administrator.



TSXMV0037 Delete error.Deletion of a member of a z/OS partitioned data set failed.


TSXMV0038 Severe error when trying to duplicate a POmember {0} .The duplicate action for a member in a z/OS partitioned data set failed.


TSXMV0040 Failed to dequeue the resource {0} .The dequeue action for a z/OS data set failed.







TSXMV0041 Severe error when trying to paste memberlist {0} from {1} .The paste action for a z/OS partitioned data set member list failed.


TSXMV0042 Severe error when checking for existenceof member {0} in {1} .An exception occurred when checking if the given member exists in the given data set.






TSXMV0043 Severe error when trying to paste memberlist {0} from {1} .The paste action of a list of z/OS partitioned data set members failed.






TSXMV0044 Exception when trying to connect to {0} .The connection to the remote system did not work when the search action was called.

User Response: Check if there are any network problems. See the message under"Reason:" in the message dialog. If necessary, contact the administrator.






TSXMV0045 There is no z connection defined. Pleasedefine a new connection first.The z/Server search action was called without a z/Server connection defined in the Remote Systems View.

User Response: Define a z/Server connection in the Remote System View, then repeat the searchaction.

TSXMV0046 Invalid begin column specified.The parameter "Begin column" for the search has an invalid format. It must have a numeric format.

User Response: Enter a numeric value in the input field "Begin column" or leave it empty.

TSXMV0047 Invalid end column specified.The parameter "End column" for the search has an invalid format. It must have a numeric format.

User Response: Enter a numeric value in the input field "End column" or leave it empty.

TSXMV0048 No system was specified.Access to the remote z/Server connection caused a NullPointer exception.


TSXMV0049 Error when setting markers for file {0} .The search markers could not be set in the editor when a file was opened from the search result view.

User Response: See the message under "Reason:" in the message dialog. Ifnecessary, contact the administrator.


TSXMV0050 Failed to browse the file.Browsing a file from the Search Result View failed.

User Response: See the message under "Reason:" in the message dialog. Ifnecessary, contact the administrator.


TSXMV0051 Remote code page does not contain avalid code page.The code page entered under "Remote Code page" in the z/Server connection definition is not a valid codepage ID.

User Response: Choose a valid code page for the remote code page.


TSXMV0052 Local code page does not contain a validcode page.The code page entered under "Local Code page" in the z/Server connection definition is not a valid codepage ID.

User Response: Choose a valid code page for the local code page (typically UTF-8).

TSXMV0054 Exception occurred during data setDragAndDrop action.The drag/drop action of a z/OS data set failed.


TSXMV0055 The source data set is migrated.A drag/drop could not be executed because the source data set is migrated.

User Response: Recall the migrated data set and retry the action.

TSXMV0056 Exception occurred during memberDragAndDrop action.The drag/drop action of a member of a z/OS partitioned data set failed.


TSXMV0057 Get bind data failed.The binder information for a z/OS load module could not be retrieved.

User Response: See the message under "Reason:" in the message dialog. If necessary,contact the server administrator.



TSXMV0058 Failed to browse the member {0} .Browsing of the given member of a z/OS data set failed.






TSXMV0059 The source data set is migrated.The source data set of a drag/drop action is migrated.


User Response: Recall the migrated data set. Retry the drag/drop action.

TSXMV0060 Delete error.Deletion of a z/OS data set failed.


TSXMV0061 Exception occurred when calling searchREXX TAUZCSRC.The call to the REXX TAUZCSRC failed.



Verify that the z/Server EXEC library is defined in the SYSEXEC concatenationof the z/Server user server. Verify that the z/Server EXEC library contains theREXX TAUZCSRC. Check the z/Server logs for more information.

TSXMV0062 Dataset Migrated/Exception when callingsearch REXX TAUZCSRC.The data set to which the search was applied is migrated.

User Response: Recall the migrated data set and retry the search action.

TSXMV0063 Unexpected response from LOGOFF.The logoff from the z/Server using the hidden command !LOGOFF results in a response from the serverthat cannot be parsed.


TSXMV0064 CALLREXX failed.The hidden command !CALLREXX results in a response from the server that cannot be parsed.


TSXMV0065 Target member name must be differentfrom source member name.The name chosen for the target member is identical to the name of the source member in the duplicateaction.

User Response: Choose a name for the target member which is different from the name of the sourcemember.

TSXMV0066 Data set name must not contain blanks.In the data set allocation dialog, a data set name was entered which contains blanks. This is not allowedfor z/OS data sets.


User Response: Enter a data set name without blanks.

TSXMV0067 Please enter a value greater than zero asprimary space amount.In the data set allocation dialog, a value of zero was entered for the primary space allocation.

User Response: Enter a value greater than zero as the primary space allocation.

TSXMV0068 Please enter a numeric value as primaryspace amount.In the data set allocation dialog, a non-numeric value was entered as the primary space allocation.

User Response: Enter a numeric value greater than zero as the primary space allocation.

TSXMV0069 Please enter a numeric value assecondary space amount.In the data set allocation dialog, a non-numeric value was entered as the secondary space allocation.

User Response: Enter a numeric value as secondary space allocation.

TSXMV0070 Please enter a numeric value for directoryblocks.In the data set allocation dialog, a non-numeric value was entered as the directory block amount.

User Response: Enter a numeric value for directory blocks.

TSXMV0071 Please enter a numeric value as recordlength.In the data set allocation dialog, a non-numeric value was entered as the record length.

User Response: Enter a numeric value as the record length.

TSXMV0072 Please enter a numeric value as blocksize.In the data set allocation dialog, a non-numeric value was entered as the block size.

User Response: Enter a numeric value as the block size.

TSXMV0073 Failed to get members of data set {0} .A top-level exception occurred when determining the members of a z/OS partitioned data set.


User Response: See the message under "Reason:" in the message dialog. Maybe the user does nothave the authority to list the members of the partitioned data set. If necessary, contactthe administrator.

TSXMV0074 Calling zServer info command failed.A error occurred calling the zServer info command.

User Response: • See the message under "Reason:" in the message dialog.• Verify that there is no network problem.• Verify that a valid code page is set for the MVS Explorer settings.



TSXMV0075 The zServer info command is not availablebefore the zServer version 2.2.02.Self-explanatory.

User Response: Self-explanatory.

TSXMV0076 A data set can only be created from adataset or from a MVS subsystem.Self-explanatory.

User Response: Create the data set from the context menu of a data set or of the MVS subsystem.

z/Server communicator (SOZCM) messages

SOZCM0001 Internal file mappings error. The filemapping {0} was not found in the index.The given file mapping could not be found in the internal file mapping cache.

UserResponse:

If the file mapping is missing in the File Mappings View, add it and retry the action. Verifythat the file_mapping.xml file exists in the internal project folder in the user's workspace.Restart Eclipse to see if the file mapping is restored from the local cache.

SOZCM0002 Failed to restore file mappings.The file mappings could not be restored from the cached data in the Eclipse workspace.

UserResponse:

Verify that the file_mapping.xml file exists in the internal project folder in the user'sworkspace and is accessible. Verify that the file_mapping.xml file is a valid XML file. Ifnot, try to repair it. If not possible, remove the file from the internal project folder and buildup the file mappings from scratch.


SOZCM0003 The number of the given values does notmatch the number of the given attributes.This is an internal program exception. An API method was called which generates XML attributes frompassed keywords and values but the number of keywords and values were not equal.


If the call was made from a custom plug-in, correct the passed parameters.Otherwise contact SupportLine.

SOZCM0004 Password is invalid.An invalid host password was specified.

User Response: Use the correct password.

SOZCM0005 The entered password is too long.The password entered by the user is too long.


SOZCM0006 The password is too long. Max. length is 8characters.The password entered by the user is too long.


SOZCM0007 Error from z/Server ADDUSRV command:{0} .The ADDUSRV command to start another z/Server user server failed.


SOZCM0008 Action cancelled by user.Self-explanatory.


SOZCM0009 Data set allocation error: {0} .An error occurred during the allocation of a z/OS data set.





SOZCM0010 {0} is not a fully qualified member name(DSN member name).The data set name passed to the routine to browse a load module does not have the expected format.


SOZCM0011 Failed to get contents for data set {0} .The content of the given z/OS data set could not be read.



SOZCM0012 pMsg must not be null.The message parameter passed to the routine which sends messages to the server is null, which is notvalid.


SOZCM0013 User not defined to RACF.The user ID specified is not defined to RACF on the remote z/OS system.

User Response: Verify that the user specified the correct user ID.

SOZCM0014 Password not authorized.The given password is incorrect.

User Response: Retry with the correct password.

SOZCM0015 The password has expired.The given password has expired.

User Response: Use the change password dialog to get a new password. The change password dialogmust be called while not disconnected from z/Server.

SOZCM0016 The new password is invalid.The new password specified in the Change Password dialog is not valid.

User Response: Enter a valid password in the Change Password dialog.

SOZCM0017 User not defined to group.The user is not defined to a RACF group.

User Response: Contact the z/OS RACF administrator.


SOZCM0018 User access revoked.The user ID is revoked in RACF.


SOZCM0019 RACF is not active.The z/OS RACF facility is not active.


SOZCM0020 User access to group revoked.The user's access to the requested RACF group is revoked.


SOZCM0021 OID REQD not supplied.The RACF OID REQD was not supplied.


SOZCM0022 OID CARD invalid for user.The RACF OID CARD was not valid for the user.


SOZCM0023 User not authorized to terminal.The user is not authorized by RACF to use a terminal.


SOZCM0024 User not authorized to APPL.The user is not authorized in the RACF class APPL.


SOZCM0025 RACF verification for user ID notsuccessful.The given user ID did not pass the RACF user ID validation.

User Response: Retry with the correct password. Contact the z/OS RACF administrator.

SOZCM0026 Access to data set {0} denied.The user does not have access to the given data set.



SOZCM0027 Unexpected length field: {0} .A non-numeric field was detected when reading a file that is encrypted using BASE64. A numeric lengthfield was expected.

Model Administrator Response: Check the error log for more information. If necessary, contactSupportLine.



SOZCM0028 Parsing of GETDATA response failed.Warning Message(s) from server: {0}An error occurred when the response from the remote system was parsed.

User Response: Check the subsequent message from the z/Server. If necessary, contactthe administrator.



SOZCM0029 The GETDATA response from server couldnot be parsed.The response from z/Server to a GETDATA request has an invalid format.


z/Server ISPF panel support (TSIPS) messages

TSIPS0001 Failed to parse help panel {0} .The help panel associated with an ISPF panel could not be located in the given input partitioned data set.This means the help panel could not be parsed and the help information could not be registered to thecorresponding attribute of the ISPF dialog tool.

UserResponse:

If help information should be added to the model, add the missing help panel to thedata set specified in the corresponding location attribute in the panel generation controlfile, and then repeat the model generation.

TSIPS0002 Given options map must not be null.An internal object was null where it was not expected to be null.



TSIPS0003 XML syntax error: A {0} element contains atleast one {1} element. No {2} attribute is set.There is an error in the XML structure of the panel model generator control file. A line command is definedfor a panel although there is no table defined for the panel.

UserResponse:

Correct the error in the panel model generator control file. If there are line commandsdefined for a panel, a table attribute must be specified in the XML panel tag. Removethe line commands or add the table attribute.

TSIPS0004 There is no {0} included in {1} element.In the panel model generator control file, an application is defined with no associated panels.

User Response: This is a warning message. Verify that the XML definition was intended to be this way.

TSIPS0005 A {0} element contains more than one {1}element with the {2} attribute: {3} .The same panel was declared more than once for the same application in the panel model generatorcontrol file.

User Response: This is a warning message. Only one ISPF dialog tool will be generated if the samepanel is declared more than once for the same application.

TSIPS0006 XML syntax error: At least one {0} attributemust be specified for {1} attribute ComboBox.A selection field was defined, but no selection values were given for a panel field in the panel modelgenerator control file.

User Response: Correct the panel model generator control file by listing the selection values.

TSIPS0007 XML syntax error: No {0} is set.The location attribute for a panel entry in the panel model generator control file could not be found.

User Response: Correct the panel model generator control file by defining the location in the overallAttr,dialogAppl or panel XML tag.

TSIPS0008 Panel extension error: parameter string forpanel REXX in panel {0} call too long. Not all panelvariables are passed to the panel REXX!There is a technical restriction that the length of the field names passed to a ISPF Panel REXX must notexceed 255 characters in total. The conversion of the given panel caused a field name length greater than255. This means that during the execution of the ISPF dialog in an Eclipse environment, not all of thevariables' contents are passed to the client, which will cause unpredictable results.


User Response: Try to change the ISPF panel so that fewer panel fields must be passed to the Eclipsedialog.

TSIPS0009 An error has occurred. See error log formore details.The XML SAX parser detected an error.

User Response: There is a log file of the panel conversion in the FileCache sub folder of the internalproject folder. See this log file for more information about the XML error.

TSIPS0010 Command property is not defined inrelation ISA_ISPF_Panel_Command for {0} .The command property is missing in the ISA_ISPF_Panel_Command relation for the given tool in themodel.


Correct the error in the ISA_ISPF_Panel_Command relation of the given tool inthe XML model file. Select the command property.

TSIPS0011 Relation ISA_ISPF_Panel_Command ismissing for {0} .The relation ISA_ISPF_Panel_Command for the given tool is missing. This relation is needed if a tool isdefined as part of a line command action for a file descriptor.


Add an ISA_ISPF_Panel_Command relation to the given tool in the XMLmodel file.

TSIPS0012 Exception occurred during ISPF dialogprocessing.An exception occurred during the execution of an ISPF dialog tool.

Model Administrator Response: Check the z/Server logs for more information.

Server Administrator Response: Check the error log for more information.

TSIPS0015 Exception when connecting to system {0} .The connection to the given remote system could not be established.

User Response: Verify that there is a network connection problem to the remote system. Verify that theconnection attributes of the remote system (IP address and port) are set correctly.

TSIPS0016 IO exception when trying to read hostmessage.An I/O exception on the network socket occurred during the execution of an ISPF dialog application.


User Response: Disconnect and re-connect to the remote system. Contact theadministrator.




Verify that there is no network problem between client and server. Checkthe z/Server logs for more information.

TSIPS0017 IO exception when sending a message tothe user server.An I/O exception on the network socket occurred during the execution of an ISPF dialog application.

User Response: Disconnect and re-connect to the remote system. Contact theadministrator.





TSIPS0018 Your dialog has timed out. Please restartthe dialog.The given dialog was open for a time interval longer than the configured timeout period without any userinteraction.

User Response: This is an informational message. Restart the ISPF dialog application.

TSIPS0019 z/Server exception during connection toport: {0} .An exception occurred during the communication of an ISPF dialog application and its associated userserver.





TSIPS0020 No ISPF help available for {0} .There is no help panel defined for the given ISPF dialog tool.


TSIPS0021 User socket is null.The network socket for the communication with the remote system has become undefined.

Model Administrator Response: Check the error log for more information. Contact SupportLine.


z/Server meta model (SOMDL) messages

SOMDL0001 Invalid License Checker extension. Thereferenced class is incompatible with ILicenseChecker:{0}This exception can be caused by an invalid Eclipse extension from a third party plug-in.


• Contact the plug-in contributor to resolve the problem.• If the exception was not caused by a third party plug-in, please contact

SupportLine.


TroubleshootingThe first step in troubleshooting is to determine in which Application Workflow Manager component theproblem occurred.

There is a general difference between the two components:

• z/Explorer• Modeled Application Workflow Manager application

The type of an Application Workflow Manager component, and where the error occurred, determine theanalysis methods required.

Some error situations are caused by a temporary failure; for example, the IP communication socketbetween the client and the z/Server might not be ready for communication.

In such cases, you will typically receive an org.xml.sax.SAXParseException message, sometimes with thereason “Content not allowed in prolog.”. Communication between the client and z/Server scheduleraddress space is in XML format. When the client does not receive an expected XML response (for instancebecause the scheduler address space is temporarily unavailable), a SAX exception occurs. In this case,first try to repeat the action, and it might work.

For more information, General problem determination describes general troubleshooting methods whichapply to all components, z/Explorer problem determination describes special methods for z/Explorer, andApplication Workflow Manager problem determination describes methods for modeled ApplicationWorkflow Manager applications.

General Problem DeterminationIn order to determine the cause of a problem, as much information as possible needs to be gathered.

Try to answer as many of the following questions as possible:

• Which version of the Application Workflow Manager software is installed on your system?

• What error message, if any, is displayed? What additional information is displayed when you clickDetails>>.

• Are there any entries in the error log relating to this error situation?

• What did you do, how did you expect the system to react, and how did the system really react?

• Is the problem reproducible?

• Does the problem only occur under certain conditions (e.g. only with certain input data or on certaintypes of element)? If so, what are they?

• Does the problem only occur in your environment or is it a general problem for all users?

• Does the problem persist after restarting your Eclipse workbench?

If the problem is to be reported to Micro Focus SupportLine, you need to collect a number of things:

• Detailed problem description

• Screenshots of error messages

• Screenshots of unexpected behavior

• Error logs

Troubleshooting | 119

Determine the original exceptionIn some cases, the error message dialog will display more than one error message. The reason for that isthat special exceptions are wrapped by less specific exceptions before they are issued.

In order to find the basic cause of the error situation, the original exception has to be determined.

Typically, this is the last exception of the list of exceptions in the details window.

Clear the persistent cache in the workspaceThe information displayed in the Application Workflow Manager view is persistently stored in the Eclipseworkspace in several XML files when the Eclipse workbench is shut down or an application is unloaded.See Further development and maintenance in the Workflow Manager Configuration Guide for moreinformation about those cache files.

In some error situations, it might be necessary to clear the cache, for example if the cache has becomeinconsistent with the model or if there are error messages indicating an inconsistent cache. We stronglyrecommend you use for this purpose the Clear Cache action on the context menu of an application in theTree View:

In this way you can ensure that the cache is cleared in a consistent way.

In some special situations, it might be necessary to delete the files directly in the file system. This shouldonly be done in accordance with or by order of SupportLine. In this case, it is important that Eclipse is shutdown before the files are deleted.

Deal with code page problemsIf problems occur which indicate a code page problem although the code page is set correctly in thezServer properties of the MVS Explorer in the Remote System View, always verify if there is a special filemapping for the regarding file. If this is the case, verify the code page setting in this file mapping.

120 | Troubleshooting

Workspace out of syncThe Eclipse workspace where the Application Workflow Manager files are located can get out ofsynchronization with the underlying file system. This can be corrected by applying the refresh action in theNavigator view to the part of the Application Workflow Manager project which has got out ofsynchronization.

z/Explorer Problem DeterminationWhen an error occurs in z/Explorer, typically an error message is displayed. If the error contains amessage ID in the format described in Introduction, refer to z/Server Messages and Diagnostics for moreinformation about the cause and possible responses.

If the error displayed is a software exception message, refer to the error log view for more information.

If none of the above helps in solving the problem, send the error log to Micro Focus; see General problemsolving suggestions.











Application Workflow Manager Problem DeterminationThe functionality of an application in the Team Developer Tree View is based on an XML model file. In mostcases, a problem in a modeled application can be traced back to an error or inconsistency in theapplication model. As a general rule, the Application Workflow Manager model administrator should

validate a model file before it is set as productive. Validate a model file by clicking , which is displayedon the Eclipse toolbar when editing a model file. Errors reported by the validation should always becorrected before the model file is set as productive.

If problems in a modeled application are reported to Micro Focus SupportLine, it is important to include theapplication model file. To do this, open Navigator View from the Eclipse workbench. In Navigator View,expand the InternalTDProject entry to the level of the application that is currently active in the TeamDeveloper Tree View. The corresponding model file TAURCONF.xml for the active application is displayed.


Include a copy of this file in the information to be sent to Micro Focus SupportLine.

The next five topics require some knowledge of Application Workflow Manager application modeling. Theyare meant as help for the Application Workflow Manager model administrator to correct some typical errorsituations caused by an inconsistent application model.

Modeled Action does not work• Check the reference to the action descriptor (e.g. “Element has Action”):

• Is there a reference to an action descriptor in the respective element type?• Is the correct action descriptor referenced?

• Check the action descriptor:

• Are the references to the tool descriptors correct (including sequence numbers)?• Check the tool executor(s):

• Are the parameters correctly modeled?

• Does the Type attribute match the Target ID used? In most cases, parameters that reference afile descriptor (TargetID File) must be modeled with the attribute Type = File while parameterspointing at a property (TargetID Parm) must have the attribute Type = String.

• Is the Parameter From attribute of all input parameters correct?

Context – The value will be taken from context (properties of the selected Element).

Previous Tool – The value will be taken from the previous tool of the corresponding actiondescriptor.


User Input – No value is used (only for Input Dialogs).Remember that you can also use a Defaultor Static value.

• If Tool Type = ISPFCOMMAND

• Is the “ISA ISPFTool” attribute modeled?• Is the program ID spelled correctly?• Is the correct invocation form specified?• Are parameter separators modeled correctly?

Element List is not created• If a detailed error dialog is displayed (containing the parsed line for element list creation):

• Use the “Validate” action of the Application Workflow Modeler. If errors were detected, try to correctthem.

• In the error dialog:

• Were the values of the parsed line parsed properly?• Is the match name (element type name) on the parsed line?• Is the match name’s position correct (depending on the position of the element type property)?• Does the parsed line contain every property of the element types ID definition?

• If no detailed error dialog is displayed:

• If the element list should be shown in Table View (no Get Children action):

• Is an element list structure modeled for the corresponding action descriptor (attribute HasElementlist)?

Tree View is not expandable• If the Tree View element is the application itself:

• Was an action descriptor defined in the Get Root Containers attribute of the application options?• If the Tree View element is an element of a modeled element type:

• Was an action descriptor defined in the Get Children attribute of the corresponding element type?• “Refresh” the Tree View element that is not expanding:

• Explanation: The Application Workflow Manager caches Tree View information. If the expand failsbecause of an incorrect model, an empty list is cached.

Tree View Elements do not have a correct label• Check the Tree View label attributes of the corresponding element type. The attribute can be found in

the “Element Type has Property” relationship.

Edit Action (Simple Remote Edit or Browse) does notwork properly• If the editor does not open, check the tool descriptor that should open it:

• The attribute Integrated Tool must be set to RemoteEdit.• An input parameter must be configured:

• Type = File• TargetID File = Unstructured tool descriptor. Check that the Name Physical attribute references

the correct property IDs.


• If the editor opens, but the editor title/label is “null”:

• Check that exactly one property of the corresponding element type has the element name attributeset to Ttrue. The attribute is in the “Element Type has Property” relationship.

• The editor opens with the wrong suffix (.txt):

• Does the corresponding element type have a relationship to a suffix property?• Does the suffix property have the attribute Special Property = Element_Suffix?

• The wrong editor opens up:

• In Eclipse, click Window > Preferences > General > Editors > File Associations and configurewhich editor should open up for the file extension (suffix).

General Problem Solving SuggestionsThis topic lists some general methods and techniques which can be helpful for troubleshooting.











Gathering information for Micro Focus SupportLineWhen a user problem cannot be resolved by the Application Workflow Manager model administrator/system administrator, report the problem to Micro Focus SupportLine.

Include debug information from the error logs to help further analysis of a problem. To include thisinformation, create a .options file and save it on the installation path of the Enterprise Developerproduct.

The .options file must contain the following:

de.soforte.taurus/debug=true de.soforte.taurus/debug/flag=true de.soforte.taurus.mvssystem/debug=true


de.soforte.taurus.mvssystem/debug/flag=true de.soforte.zserver.communicator/tracing=true

You can edit this file with Notepad or any similar text editor.

To quickly find the installation path when saving the .options file, click Open File Location from theEnterprise Developer shortcut.

After the .options file has been created and saved to the installation path, restart the Eclipse workbenchwith the –debug option (append ‘-debug’ to the Target field shown above).

Reproduce the error and export the error log to a local file (click Error Log View from the Eclipseworkbench).


Add the exported file to all other information (problem description, screenshots, etc.) for SupportLine, andzip it up ready to attach to an incident raised with Micro Focus SupportLine.

Remove the –debug option from the Target field.

You can also add debug information to a remote z/Server user server address space by activating theREXX debug as described in the Workflow Manager Configuration Guide.


Sample error situations

z/Server is not activeIf z/Server is not active on the remote system, an error message similar to the one below is displayed whenconnecting to z/Server:

Connection to z/Server is interruptedIf the network connection between client and remote system is interrupted, an error message similar to theone below is displayed when connecting to z/Server:

Sample error situations | 129

When z/Server is not active, the same message is received. The same error message can have differentreasons.

Connection problem when connection is activeWhen network connection problems occur while already connected to a remote system (z/Server), an errormessage similar to the one below is displayed:

The connection problem occurred while closing a file in the editor. The action "delete the local copy of thefile" could not be executed. The reason is a timeout because of connection problems.

No RACF OMVS segmentIf there is no RACF OMVS segment defined to the TSO user ID used to execute an ISPF tool using anApplication Workflow Manager modeled application, the following error message is displayed:

This message was issued by z/Server (the remote software), the scheduler address space in particular.The scheduler address space had started the user server address space needed to establish the master

130 | Sample error situations

configuration data set that contains the ISPF application. That address space did come up, but was unableto signal itself READY to the scheduler address space. Message SLR0131E is issued to the client after apredefined wait period to tell the client that it could not talk to the user server address space.

The administrator for z/Server needs to check for errors. For this particular problem, the z/OS hardcopy logshows:

ICH408I USER(user ) GROUP(group ) NAME(####################) CL(PROCESS ) OMVS SEGMENT NOT DEFINED

Job output in user server maintask has this error message again detailing the missing OMVS RACFsegment:

TAU0143S 07:35:19.091 This indicates an z/OS UNIX process initialisation failure. This is usually an indication that a proper OMVS RACF segment is not defined for the user ID associated with the application The RACF OMVS segment may not be defined or may contain error such as an improper HOME() directory specification. TAU0139E 07:35:24.094 SVC with function code 00000800 failed with RC 00000008

In this case, the TSO user ID must be defined with an OMVS segment (usually done by the RACFadministrator) as detailed in the z/Server Installation and Reference.

Model error: wrong Program IDIf the Application Workflow Manager model administrator defined a wrong Program ID in the ISA ISPF Toolrelation of a tool descriptor, the following error message is displayed:

Model error: wrong Panel NameIf the Application Workflow Manager model administrator defined a wrong Panel Name in the ISA ISPFPanel relation of a tool descriptor for an ISPF dialog tool, the following error message is displayed:


Error situations in an attached toolIf one of the pre-configured Application Workflow Manager models (PDS Explorer, SCLM Application,ChangeMan Application) or custom application models based on the REXX tool adapter TAUTOSAM areused, the attached tools will report error situations in a defined way.

For a deeper understanding of the methods and techniques of Application Workflow Manager toolattachment, please see the Workflow Manager Configuration Guide.

Application Workflow Manager displays an error message when the return code of the attached tool ishigher than the value specified by the Application Workflow Manager model administrator under theproperty Max RC of Application Options in the Application Workflow Manager model. The recommendedvalue for Max RC is 4. Then the following error message is displayed:

Within the message, the return code and message returned by the attached tool are shown.

The following table shows special return codes generally used in pre-configured Application WorkflowManager models, specifically in models based on the REXX tool adapter TAUTOSAM.

Return code Meaning

0 Attached tool successfully executed; no message windowis displayed.

11 The return code of the facility called (such as TSO orISPF) is higher than the maximum return code specifiedin the facility call. The message contains the commandcalled and the return code produced by the facility. Lookup the meaning of the return code in the correspondingIBM book under the command reported by the message.


Return code Meaning

99 Undefined variable referenced or syntax error in theattached tool.

In addition to these special return codes, attached tools can return custom created return codes andmessages. If the REXX TAUTOSAM is used as a template for custom tool adapters, these custommessages are reported with the same formatting.

The following examples shows the error messages displayed when certain error situations occur within anattached tool.

• Undefined variable used in the attached tool:

• Syntax error in the attached tool:

• Call to ISPF command VGET returns a return code higher than the maximum return code allowed ( 4):


Looking in REXX TAUPDGJK, the error was produced by a call to ISPF command VGET:

Call ISPF '0 VGET (ZUSERA) SHARED'

IBM ISPF Services Guide for the command VGET shows the following under return code 8:

Variable not found. If the SYMDEF parameter was specified: system symbol not found.

• Custom return code:

The custom tool TOOL_Getdatasets returned with a return code of 12, which is higher than Max RC of4 specified under Application Options in the Application Workflow Manager model. The messagereturned by the tool is "This is a customer specific error situation…".


Known issuesIn this topic, known issues and possible workarounds are provided.

The port of a z/Server connection is not remembered

Description: When a new z/Server connection is created and the Eclipse workbench is exitedwithout connecting to this new connection, the port is set back to the default value1111 when the Eclipse workbench is re-entered.

Auxiliarysolution:

You should always connect to a newly created z/Server connection before exiting theEclipse workbench.

Change password when connected

Description: If the Change Password… action is used on a z/Server connection that is activelyconnected to a remote host, this can lead to subsequent problems.

Auxiliary solution: Use the Change Password… action only on a z/Server connection that is notconnected.

Change code page settings when connected

Description: If the code page settings of the MVS Explorer are changed on a z/Server connectionthat is actively connected to a remote host, certain actions won’t work correctlyafterwards.

Auxiliarysolution:

Change the code page settings only on a z/Server connection that is not connected.

Multi-selection in ISPF table dialogs with non-keyed tables

Description: In modeled ISPF table dialogs with non-keyed tables, multi-selection of table entriesdoesn't work correctly.

Auxiliary help: ISPF table dialogs of non-keyed ISPF tables with multi-selection line commands cannotyet be modeled.

Known issues | 135

Troubleshooting Workflow Manager Messages and

Documents

Transcript of Troubleshooting Workflow Manager Messages and