Increase the region on the job(s) doing the retrieval. CSI returns the data in 
a buffer in *YOUR*  private storage, not his.
Depending on the amount of data returned by the request you might/might not 
receive a correct answer.

The results can range from success to "not found" (your case) or S878 abends.

HTH,

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Bruce Lightsey
Sent: Thursday, July 9, 2020 3:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: potential catalog search error - shown by IGGCSI00

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

While I’m waiting on my sysprog and IBM to finish scratching their heads I 
thought I’d ask if anyone had run into and corrected a similar situation.  And 
many thanks to Kirk Wolf for patiently helping isolate where the issue seems to 
be.

Situation :

On one particular LPAR I cannot retrieve a dataset via SFTP and also cannot 
find the specific dataset with sys1.samplib(iggcsirx).
I used Co:Z SFTP to “put” the dataset to the LPAR; I can use regular FTP to 
“get” the dataset; I can edit the dataset in ISPF; from my Windows workstation 
using SFTP I can see the dataset when I issue the “ls” command but when I “get” 
the dataset I get a “dataset not found” error. Same result when using Filezilla 
– when connecting to FTP I can “put” and “get” with no difficulty but when 
using SFTP I can “put”, see the dataset in the listing on the mainframe, but I 
can’t “get” the dataset.   Frustrating !
On TSO with the sys1.samplib(iggcsirx) REXX using the specific name as the 
filter key - CCTSD02.TRIM.TXT - yields nothing but wild-carding the filter key 
- CCTSD02.TRIM.TXT.** - returns the catalog information as expected.
I have verified that this is the same behavior for any dataset on the LPAR – 
you must wild-card the name in order to get the catalog info returned. There is 
also a user-started SAP process integration task using plain FTP and IGGCSI00 
that fails unless the dataset name is wild-carded

On a second LPAR on the same CEC that shares the user catalogs, the REXX 
returns the catalog information in both scenarios ( with and without the 
wild-card ). This makes me think that there is something uniquely set/broken on 
my problem LPAR but I am at a loss as to where to look now.

On a second box with multiple z/OS 2.2 and 2.3 LPARS, the REXX also works as 
expected with and without the wild-card.

Any ideas ?

Thanks,
Bruce



Bruce Lightsey
Database Manager
MS Department of Information Technology Services
601-432-8144 | 
https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.its.ms.gov%2F&amp;data=02%7C01%7Callan.staller%40HCL.COM%7Cfcb9a060c223460e884608d824494fa3%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637299244596160894&amp;sdata=hol%2Bhz9iqcXZKQ5pC6mPBIpDehrI5sDz6mrvYzUMyUA%3D&amp;reserved=0

DISCLAIMER: This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error please notify the system 
manager. This message contains confidential information and is intended only 
for the individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. If you are not the intended recipient you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.
________________________________

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to