<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: length statement in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744312#M233182</link>
    <description>&lt;P&gt;Also the main message windows on this forum reformat text seriously.&lt;/P&gt;
&lt;P&gt;Consider that this code typed into my editor and pasted into a text box opened on this forum with &amp;lt;/&amp;gt; icon above the message window.&lt;/P&gt;
&lt;PRE&gt;data cha;
input name $6.;
datalines;
CAPONE
 CAPONE
  CAPONE
   CAPONE
    CAPONE
;
run;&lt;/PRE&gt;
&lt;P&gt;will run with CAPONE losing characters after the first value because the input statement when used as Input Name $6. tells SAS to read exactly 6 characters from the current position of the input pointer. Which will be the first column at each iteration of the input statement.&lt;/P&gt;
&lt;P&gt;This is what happens when the exact same code is pasted into the main message window:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;data cha;&lt;BR /&gt;input name $6.;&lt;BR /&gt;datalines;&lt;BR /&gt;CAPONE&lt;BR /&gt;CAPONE&lt;BR /&gt;CAPONE&lt;BR /&gt;CAPONE&lt;BR /&gt;CAPONE&lt;BR /&gt;;&lt;BR /&gt;run;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Notice that all of the lines with spaces have been moved left. So what you showed for the first data step may not be what you ran at all.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can modify the Input statement to tell SAS to skip the default space delimiters until the first non-space is encountered buy using the modifier : before the informat.&lt;/P&gt;
&lt;PRE&gt;data cha;
input name :$6.;
datalines;
CAPONE
 CAPONE
  CAPONE
   CAPONE
    CAPONE
;
run;&lt;/PRE&gt;
&lt;P&gt;which generates 5 values of CAPONE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 27 May 2021 21:58:29 GMT</pubDate>
    <dc:creator>ballardw</dc:creator>
    <dc:date>2021-05-27T21:58:29Z</dc:date>
    <item>
      <title>length statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744285#M233166</link>
      <description>&lt;P&gt;Query 1:&lt;/P&gt;
&lt;P&gt;For the below data set the value is coming as &lt;STRONG&gt;CAPON&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;data cha;&lt;BR /&gt;input name $6.;&lt;BR /&gt;datelines;&lt;BR /&gt;CAPONE&lt;BR /&gt;;&lt;BR /&gt;run;&lt;/P&gt;
&lt;P&gt;but when I change the format to&amp;nbsp;&lt;STRONG&gt;name $7. &lt;/STRONG&gt;I am getting value as&lt;STRONG&gt;CAPONE&lt;/STRONG&gt;&lt;BR /&gt;what is the reason here for this trunctaion. Please explain.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Query 2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;data chg;&lt;BR /&gt;set cha;&lt;BR /&gt;y=length(CAPONE);&lt;BR /&gt;do i =1 to length(CAPONE);&lt;BR /&gt;z=substr("CAPONE",i,1);&lt;BR /&gt;output;&lt;BR /&gt;end;&lt;BR /&gt;run;&lt;/PRE&gt;
&lt;P&gt;here the value of y = 12 . Why its coming like 12 .Please explain.&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 27 May 2021 19:46:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744285#M233166</guid>
      <dc:creator>Aexor</dc:creator>
      <dc:date>2021-05-27T19:46:21Z</dc:date>
    </item>
    <item>
      <title>Re: length statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744287#M233168</link>
      <description>Addition to this :&lt;BR /&gt;&lt;BR /&gt;data chg;&lt;BR /&gt;set cha;&lt;BR /&gt;y=length(name);&lt;BR /&gt;do i =1 to length(name);&lt;BR /&gt;z=substr(name,i,1);&lt;BR /&gt;output;&lt;BR /&gt;end;&lt;BR /&gt;run;&lt;BR /&gt;&lt;BR /&gt;Now the length is coming as 6 and looping is also till 6 . So its correct .&lt;BR /&gt;&lt;BR /&gt;Can anyone please explain the  all the three conditions ?</description>
      <pubDate>Thu, 27 May 2021 19:50:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744287#M233168</guid>
      <dc:creator>Aexor</dc:creator>
      <dc:date>2021-05-27T19:50:09Z</dc:date>
    </item>
    <item>
      <title>Re: length statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744288#M233169</link>
      <description>&lt;P&gt;Your CHA data set has a single variable - NAME.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It has one value, CAPONE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Your code is referencing CAPONE as both a variable and as a string. I think you shoudl be using the NAME there (very bad variable name and easily leads to confusion).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data chg;
set cha;
y=length(name);
do i =1 to length(name);
z=substr(name, i, 1);
output;
end;
run;&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 27 May 2021 19:52:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744288#M233169</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2021-05-27T19:52:12Z</dc:date>
    </item>
    <item>
      <title>Re: length statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744291#M233171</link>
      <description>yes I used Name only in my third query and output came perfect.&lt;BR /&gt;&lt;BR /&gt;My doubt is in above 2 query why the length value is coming different :&lt;BR /&gt;Query 1:&lt;BR /&gt;&lt;BR /&gt;For the below data set the value is coming as CAPON&lt;BR /&gt;&lt;BR /&gt;data cha;&lt;BR /&gt;input name $6.;&lt;BR /&gt;datelines;&lt;BR /&gt;CAPONE&lt;BR /&gt;;&lt;BR /&gt;run;&lt;BR /&gt;&lt;BR /&gt;but when I change the format to name $7. I am getting value as CAPONE&lt;BR /&gt;what is the reason here for this truncation. Please explain.&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Query 2.&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;data chg;&lt;BR /&gt;set cha;&lt;BR /&gt;y=length(CAPONE);&lt;BR /&gt;do i =1 to length(CAPONE);&lt;BR /&gt;z=substr("CAPONE",i,1);&lt;BR /&gt;output;&lt;BR /&gt;end;&lt;BR /&gt;run;</description>
      <pubDate>Thu, 27 May 2021 20:07:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744291#M233171</guid>
      <dc:creator>Aexor</dc:creator>
      <dc:date>2021-05-27T20:07:24Z</dc:date>
    </item>
    <item>
      <title>Re: length statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744295#M233174</link>
      <description>&lt;P&gt;So your first data step is reading the first 6 bytes from the line into NAME.&amp;nbsp; If you are getting 'CAPON' and not 'CAPONE' then the letter C is in the second column of the line and not the first.&amp;nbsp; The $ informat removes leading spaces.&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data cha;
  input name $6.;
datelines;
 CAPONE
;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;PRE&gt;635   data cha;
636     input name $6.;
637   datelines;
      ---------
      14

WARNING 14-169: Assuming the symbol DATALINES was misspelled as datelines.

NOTE: The data set WORK.CHA has 1 observations and 1 variables.
NOTE: DATA statement used (Total process time):
      real time           0.07 seconds
      cpu time            0.04 seconds


639   ;
640
641   proc print;
642   run;

NOTE: There were 1 observations read from the data set WORK.CHA.
NOTE: PROCEDURE PRINT used (Total process time):
      real time           0.10 seconds
      cpu time            0.03 seconds
&lt;/PRE&gt;
&lt;P&gt;Note that your first data step is not using any &lt;STRONG&gt;FORMAT&lt;/STRONG&gt;s.&amp;nbsp; It is using the &lt;STRONG&gt;INFORMAT&lt;/STRONG&gt; of $6.&amp;nbsp; If you change that to use the $7. informat instead then the first 7 characters of the line will be read.&amp;nbsp; Also since you did not tell SAS explicitly what type or length to use to define NAME is it guessing you want it have a type and length that matches in the informat you used in the INPUT statement where you first referenced NAME.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Your second data step is referencing a variable CAPONE that does not exist.&amp;nbsp; SAS will default CAPONE to NUMERIC.&amp;nbsp; You then use it as input to a function that expects a string so SAS will convert it to a string using the BEST12. format.&amp;nbsp; So the LENGTH() of that string will be 12 since SAS right aligns the strings generated by numeric formats by default.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The DO loop is then pulling out the letters from the string constant 'CAPONE'.&amp;nbsp; You will get errors when I is larger than 6 since that string only takes 6 bytes.&lt;/P&gt;
&lt;PRE&gt;643
644   data chg;
645     set cha;
646     y=length(CAPONE);
647     do i =1 to length(CAPONE);
648       z=substr("CAPONE",i,1);
649     output;
650     end;
651   run;

NOTE: Numeric values have been converted to character values at the places given by: (Line):(Column).
      646:12   647:21
NOTE: Variable CAPONE is uninitialized.
NOTE: Invalid second argument to function SUBSTR at line 648 column 7.
NOTE: Invalid second argument to function SUBSTR at line 648 column 7.
NOTE: Invalid second argument to function SUBSTR at line 648 column 7.
NOTE: Invalid second argument to function SUBSTR at line 648 column 7.
NOTE: Invalid second argument to function SUBSTR at line 648 column 7.
NOTE: Invalid second argument to function SUBSTR at line 648 column 7.
name=CAPON y=12 CAPONE=. i=13 z=  _ERROR_=1 _N_=1
NOTE: There were 1 observations read from the data set WORK.CHA.
NOTE: The data set WORK.CHG has 12 observations and 5 variables.
NOTE: DATA statement used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds


652
653   proc print;
654   run;

NOTE: There were 12 observations read from the data set WORK.CHG.
NOTE: PROCEDURE PRINT used (Total process time):
      real time           0.02 seconds
      cpu time            0.01 seconds
&lt;/PRE&gt;
&lt;PRE&gt;Obs    name

 1     CAPON
&amp;#12;
Obs    name      y    CAPONE     i    z

  1    CAPON    12       .       1    C
  2    CAPON    12       .       2    A
  3    CAPON    12       .       3    P
  4    CAPON    12       .       4    O
  5    CAPON    12       .       5    N
  6    CAPON    12       .       6    E
  7    CAPON    12       .       7
  8    CAPON    12       .       8
  9    CAPON    12       .       9
 10    CAPON    12       .      10
 11    CAPON    12       .      11
 12    CAPON    12       .      12&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 May 2021 20:27:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744295#M233174</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2021-05-27T20:27:26Z</dc:date>
    </item>
    <item>
      <title>Re: length statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744297#M233175</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/327170"&gt;@Aexor&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;Query 1:&lt;/P&gt;
&lt;P&gt;For the below data set the value is coming as &lt;STRONG&gt;CAPON&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;data cha;&lt;BR /&gt;input name $6.;&lt;BR /&gt;datelines;&lt;BR /&gt;CAPONE&lt;BR /&gt;;&lt;BR /&gt;run;&lt;/P&gt;
&lt;P&gt;but when I change the format to&amp;nbsp;&lt;STRONG&gt;name $7. &lt;/STRONG&gt;I am getting value as&lt;STRONG&gt;CAPONE&lt;/STRONG&gt;&lt;BR /&gt;what is the reason here for this trunctaion. Please explain.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Query 2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;data chg;&lt;BR /&gt;set cha;&lt;BR /&gt;y=length(CAPONE);&lt;BR /&gt;do i =1 to length(CAPONE);&lt;BR /&gt;z=substr("CAPONE",i,1);&lt;BR /&gt;output;&lt;BR /&gt;end;&lt;BR /&gt;run;&lt;/PRE&gt;
&lt;P&gt;here the value of y = 12 . Why its coming like 12 .Please explain.&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Just exactly how are you looking at the data to determine the value is CAPON and not CAPONE?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It is not uncommon in a table viewer that the column width does not match the length of a variable and it can appear truncated when in fact it just a viewer issue.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Since your data set does not have a variable named CAPONE you created one with the statement (unless it is a different CHA data set) and without something defining it as character it is a NUMERIC variable. The length function&lt;/P&gt;
&lt;PRE&gt;y=length(CAPONE);&lt;/PRE&gt;
&lt;P&gt;From the documentation for the Length function&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;DIV class="xis-refDictEntry"&gt;
&lt;DIV class="xis-details"&gt;
&lt;DIV id="n06981dbdj93hln1ci73ze8r9kui" class="xis-topicContent"&gt;
&lt;DIV id="n1y1j5jo789qxcn1fnf6fis8gfyr" class="xis-paragraph"&gt;. If &lt;SPAN class="xis-userSuppliedValue"&gt;string&lt;/SPAN&gt; is a numeric constant, variable, or expression (either initialized or uninitialized), SAS automatically converts the numeric value to a right-justified character string by using the BEST12. format. In this case, LENGTH returns a value of 12 and writes a note in the SAS log stating that the numeric values have been converted to character values.&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;If your log shows a note about numeric conversion to character on the line with the Y= statement that is exactly what happened. When I run your code to create Cha and then Chg this is the result from the LOG;&lt;/P&gt;
&lt;PRE&gt;301  data cha;
302  input name $6.;
303  datalines;

NOTE: The data set WORK.CHA has 1 observations and 1 variables.
NOTE: DATA statement used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds


305  ;
306  data chg;
307     set cha;
&lt;STRONG&gt;&lt;FONT size="5" color="#800080"&gt;308&lt;/FONT&gt;&lt;/STRONG&gt;     y=length(CAPONE);
309     do i =1 to length(CAPONE);
310        z=substr("CAPONE",i,1);
311        output;
312     end;
313  run;

NOTE: Numeric values have been converted to character values at the places given by:
      (Line):(Column).
      &lt;FONT size="5" color="#800080"&gt;&lt;STRONG&gt;308&lt;/STRONG&gt;&lt;/FONT&gt;:13   309:22
NOTE: Variable CAPONE is uninitialized.
NOTE: Invalid second argument to function SUBSTR at line 310 column 9.
NOTE: Invalid second argument to function SUBSTR at line 310 column 9.
NOTE: Invalid second argument to function SUBSTR at line 310 column 9.
NOTE: Invalid second argument to function SUBSTR at line 310 column 9.
NOTE: Invalid second argument to function SUBSTR at line 310 column 9.
NOTE: Invalid second argument to function SUBSTR at line 310 column 9.
name=CAPONE y=12 CAPONE=. i=13 z=  _ERROR_=1 _N_=1
NOTE: There were 1 observations read from the data set WORK.CHA.
NOTE: The data set WORK.CHG has 12 observations and 5 variables.
NOTE: DATA statement used (Total process time):
      real time           0.01 seconds
      cpu time            0.01 seconds

&lt;/PRE&gt;
&lt;P&gt;I have highlighted the line numbers so you can see where the "conversion" took place, also that Capone is uninitialized (that means a value is never encountered) and all the invalid data comments when looping over the (empty) variable Capone.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Did you read the LOG? That is quite often the quickest way to determine why something is or is not happening.&lt;/P&gt;
&lt;P&gt;Such as you have DATALINES misspelled in the first data step and it won't execute at all.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 May 2021 20:27:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744297#M233175</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2021-05-27T20:27:37Z</dc:date>
    </item>
    <item>
      <title>Re: length statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744299#M233176</link>
      <description>&lt;P&gt;You can check for yourself whether the data actually contains a leading blank as in the example below:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data cha;
input name $char6.;
do i=1 to 6;
   letter = substr(name, i, 1);
   put i= letter=;
end;
datelines;
 CAPONE
;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;The $CHAR informat will preserve any leading blanks that appear in the incoming data.&amp;nbsp; That's likely the scenario, and you can run this type of program to easily confirm whether this is the problem.&amp;nbsp; As&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/159"&gt;@Tom&lt;/a&gt;&amp;nbsp;mentioned, the $6. informat reads six characters only, but left-hand justifies whatever it finds within those six characters.&lt;/P&gt;</description>
      <pubDate>Thu, 27 May 2021 20:43:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744299#M233176</guid>
      <dc:creator>Astounding</dc:creator>
      <dc:date>2021-05-27T20:43:25Z</dc:date>
    </item>
    <item>
      <title>Re: length statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744312#M233182</link>
      <description>&lt;P&gt;Also the main message windows on this forum reformat text seriously.&lt;/P&gt;
&lt;P&gt;Consider that this code typed into my editor and pasted into a text box opened on this forum with &amp;lt;/&amp;gt; icon above the message window.&lt;/P&gt;
&lt;PRE&gt;data cha;
input name $6.;
datalines;
CAPONE
 CAPONE
  CAPONE
   CAPONE
    CAPONE
;
run;&lt;/PRE&gt;
&lt;P&gt;will run with CAPONE losing characters after the first value because the input statement when used as Input Name $6. tells SAS to read exactly 6 characters from the current position of the input pointer. Which will be the first column at each iteration of the input statement.&lt;/P&gt;
&lt;P&gt;This is what happens when the exact same code is pasted into the main message window:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;data cha;&lt;BR /&gt;input name $6.;&lt;BR /&gt;datalines;&lt;BR /&gt;CAPONE&lt;BR /&gt;CAPONE&lt;BR /&gt;CAPONE&lt;BR /&gt;CAPONE&lt;BR /&gt;CAPONE&lt;BR /&gt;;&lt;BR /&gt;run;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Notice that all of the lines with spaces have been moved left. So what you showed for the first data step may not be what you ran at all.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can modify the Input statement to tell SAS to skip the default space delimiters until the first non-space is encountered buy using the modifier : before the informat.&lt;/P&gt;
&lt;PRE&gt;data cha;
input name :$6.;
datalines;
CAPONE
 CAPONE
  CAPONE
   CAPONE
    CAPONE
;
run;&lt;/PRE&gt;
&lt;P&gt;which generates 5 values of CAPONE.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 May 2021 21:58:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744312#M233182</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2021-05-27T21:58:29Z</dc:date>
    </item>
    <item>
      <title>Re: length statement</title>
      <link>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744453#M233230</link>
      <description>&lt;P&gt;Thanks much for valuable inputs&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 May 2021 15:53:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/length-statement/m-p/744453#M233230</guid>
      <dc:creator>Aexor</dc:creator>
      <dc:date>2021-05-28T15:53:25Z</dc:date>
    </item>
  </channel>
</rss>

